Although the proposal was not passed in this round, the final tally is 5:5, representing 73% of the voting power. First of all, I would like to sincerely thank the 5 supporters; your support has given me sufficient confidence and motivation to continue advancing this proposal. At the same time, I also appreciate the feedback provided by the dissenters. I have responded to 4 of them individually (one dissenter has not yet provided a rationale), and I look forward to everyone’s feedback. I plan to continue the discussion for one week and re-submit the proposal on-chain after that. I look forward to receiving more diverse opinions during the discussion; questions are welcome.
Below, I will summarize and clarify several representative issues:
1. Regarding the claim that 5 months on Base without gaining traction proves SwaptoX lacks “pulling power”: The Base ecosystem is different from Rootstock; Base has too many choices and its ecosystem is even “oversupplied,” while Rootstock has fewer choices and is somewhat “undersupplied.” Furthermore, we did not execute any promotion plans on Base. The lackluster performance of SwaptoX on Base cannot be equated to its potential performance on Rootstock. Running for 5 months should be seen as a strength, proving the developer’s ability for continuous maintenance and cost expenditure. We view this project as infrastructure—long-term construction and stable development. We do not expect immediate attention. The fact that the developer has spent significant time and effort, self-funding operations for a year with the current priority still being development and improvement, is sufficient proof of this.
2. Excessive requirements for solo developers or unclear risk judgment: Everyone knows the risks of solo developers, yet Rootstock still provides KYC processes and solutions. If a solo developer, who has self-developed (with no existing open-source solutions to reference or copy) for over half a year and self-funded operations for 5 months, is still labeled as “High Risk,” are the requirements for solo developers too high? If you are concerned about unknown risks such as single-point-of-failure or personal accidents, I completely understand, but I suggest defining the minimum standards for solo developers; otherwise, such unknown risks without evidence will be difficult to define.
(The above two points are responses to the questioning of SwaptoX and myself)
3. This project is a huge challenge for a solo developer: It is precisely because I face huge challenges that I am applying for a grant. Fortunately, the core part has been completed, and I have solved the technical problems alone. We do not need to hire a development team in the short term, which greatly reduces costs. This grant will help us assemble a marketing team, which will be more cost-effective and efficient.
4. Regarding the grant, I must quote the excellent response from @ChronoTrigger**:**
5. Unable to provide verifiable Rootstock deployment contracts: This is a procedural issue; Milestone 1 is the migration and deployment. An aggregator is not a static contract; it requires cooperation with liquidity contracts. This is a complex task involving the deployment of quotation contracts, trading contracts, liquidity collection, liquidity info polling bots, and the integration of frontend and backend. Only after completing Milestone 1 can I provide verifiable Rootstock deployment contracts.
Finally, I am providing a more detailed explanation of Milestone 1 after further investigation:
-
Deploy SwaptoX core contracts on Rootstock mainnet.
-
Integrate Rootstock native tokens and liquidity pools, including liquidity from WoodSwap, Sushi, and UniSwap. (Since UniSwap does not list a Rootstock network entry, I discovered its liquidity via on-chain data).
-
Ensure accurate routing, quotation, and execution.
-
Provide a publicly accessible Swap UI connected to Rootstock.
-
At least 30+ supported tokens in the initial deployment. (Liquidity is increased but not the number of tokens. Specific tokens can be viewed via the block explorer; 28 tokens have logos and price info: ).
-
Deploy liquidity sorting and quotation bots.
Some of the 30+ tokens may lack liquidity, but they already include all tokens on the Rootstock network for which liquidity has been created (even if liquidity is low or zero). The liquidity quotation bot primarily obtains price data for tokens and displays prices on the frontend, including 24-hour price trends. The liquidity sorting bot is used for the swap algorithm; we will obtain liquidity data in real-time for sorting. During quotation, if the routing passes through too much liquidity, we will filter based on liquidity ranking to ensure performance and stability.