Rationale: We’re supportive of Global Wallet by Blockscout proposal as the team have already revise the milestone based on the feedback from delegates by reducing the grant size, clarifying milestones and costs, and adding onramps that help improve Web2 to Web3 onboarding.
Rationale: We’re voting against the SwaptoX Aggregator proposal because the team did not complete the mandatory KYC step as required by the Rootstock Collective grant process.
Rationale: We do not support releasing funds for the second milestone due to failure to deliver Milestone 1 within the agreed timeline, which was originally planned to be completed within one month but experienced significant delays. In addition, a team member, Manuel Rico Molina, previously received funding under [2507 Grant] BTCFi for Institutions: Multisig Custody with DeFi Access on Rootstock – Milestone 1, for which we have not seen any public updates since approval. Taken together, these inconsistencies and lack of disclosure indicate insufficient reporting discipline and raise concerns about the team’s level of commitment.
Rationale: We’re in favor of the Milestone 3 focus on go-to-market and adoption of AON crowdfunding. Supporting campaigns that are close to reaching their goals makes sense, and the additional $2,000 seems reasonable as a small traction budget to help push near-complete campaigns over the line so they can receive their funds.
Rationale: While we appreciate the concept, we are not yet fully convinced. We do not currently see a clear benefit for Rootstock in subsidizing user interest as a mechanism for onboarding. As you mentioned:
However, we do not see any KPI, milestone, or deliverable in the proposal that would clearly attract new USD depositors. As designed, the pilot only subsidizes borrowing demand and does not include a USD supply-side growth strategy. Even if borrowing volume is cumulative over six months, we believe a clear and explicit plan for supply-side growth is essential for this initiative to deliver meaningful protocol value to Rootstock.
Rationale: We support the release of funding for delegate compensation for the month of January, as delegates are a crucial part of the Rootstock Collective and this program ensures they are fairly compensated for their contributions.
Rationale: We’re voting against the SwaptoX aggregator proposal at this time. While we see the benefit of building an aggregator on Rootstock, and your demonstrations show that SwaptoX can find better routes than other aggregators, Rootstock still has low DEX liquidity and only a small number of DEXs. As a result, an aggregator is likely to offer limited price improvement. That said, the project should also have clear deliverables that lead to user adoption, not just integration with Rootstock.
I previously considered your suggestion to define a growth-focused milestone. However, since there was no further engagement on that specific topic at the time, I focused on the technical delivery instead.
In my view, the current priority must be technical development. Our roadmap for Milestones 1 through 3 covers three months, with an additional two months dedicated to developing advanced features such as “Limit Orders” and “Exact Output” routing. Once these core functionalities are delivered, the priority will naturally shift toward Security Audits and Growth Strategies.
The reason we cannot define a reasonable “growth milestone” right now is that we lack the necessary baseline data on Rootstock: we don’t yet know the difficulty of user acquisition, the conversion rates, or the benchmarks for CPA (Cost Per Acquisition) and CPS (Cost Per Sale).
However, after operating for six months, we will have a clear understanding of the user experience, retention rates, and growth hurdles. At that stage, if we need additional milestones to scale, we will be able to provide professional data and define a much more efficient, evidence-based growth plan. Don’t you think this is a more responsible approach?
Regarding the low liquidity issue: I believe it is precisely when liquidity is scarce that users need an aggregator most to capture the limited depth available across the network. We are committed to optimizing user experience by providing multiple routing paths, which leads to a more transparent and positive trading experience. What do you think?
Rationale: We support Milestone 2 of the Self-Sovereign Identity (SSI) proposal, as the team reduced the audit budget and proactively addressed delegate concerns through detailed responses.
Rationale: We support Milestone 3 following the completion of Milestone 2 and the securing of four signed LOIs with committed projects. The focus now shifts from coordination to execution, live integrations and measurable onchain impact. This is the right next step for the proposal. We look forward to seeing concrete deployments delivered on Rootstock.
Rationale: As the project has rescope Milestone 2 to integrate with Lemon while still keeping the overall delivery reasonable for us, we view the additional $5K request as justified. The opportunity to integrate as a Mini App inside a platform with 5M+ users can strengthen the GTM strategy and accelerate user validation.
That said, we still have some doubt regarding the asset chosen for initial deployment. Cars are understandable as a practical test case, but they are depreciating assets and carry a different long-term value narrative compared to real estate. We expect this milestone to build foundational components that are reusable and scalable across more robust RWA categories in future expansions. Overall, we support Milestone 2 of Zerem Finance in its updated form.
Rationale: We support the revised SwaptoX proposal. The team clearly listened to previous community feedback, reduced the upfront funding and strengthened their commitments around deliverables. That shows willingness to work with Rootstock. We think it’s worth giving this a try and evaluating the results based on actual delivery and ecosystem impact.
Rationale: We are in favor of continuing support for the recognized delegate compensation program and approving the release of funds to those delegates who qualified for February.
Rationale: While the proposal authors, including Beexo and the Rootstock Ambassador, have credible backgrounds, we have decided to vote against this proposal. The requested budget of $12.5K appears relatively high for an event sponsorship, particularly given the uncertainty around measurable outcomes. Additionally, the timeline appears too tight to ensure smooth execution, which increases the risk that the event may not deliver meaningful ecosystem impact.