[2601 Grant] SwaptoX Aggregator – Milestone 1（V2.1 Proposal
We voted For: Milestones were completed and no issues. Releasing the next milestone as prior agreed upon.
[Grant 2603] Recognized Delegate Compensation - February 2026
We voted For: Voting yes for the decision on the delegates as proposed.
[2603] Beexo BTCFi Grant – Criptovendimia 2026
We voted Against: Too much of a rush at this point to sponsor and the requested amount not matching the forums is concerning.
We voted Against: While we supported milestones 1 through 3 of this program on the basis of operational completion of deliverables, the latest update reflects on-chain activity that materially undershoots the underlying premise of the grant. The original scope targeted projects generating $500K+ TVL with meaningful ecosystem usage, and the most recent monthly report on the program’s anchor deployment shows roughly $1,000 in volume across 8 unique wallets and 31 transactions. The milestone payment structure was designed to be performance-based and tied to project deployment and ecosystem contribution, and the realized contribution at this stage is not at the level that justifies releasing further funds against the originally scoped success criteria. We would support a future milestone that documents either meaningful activation of the existing deployments or a credible reset on KPI targets, but releasing M4 as currently presented is not consistent with the performance-based intent of the program.
We voted For: Consistent with our prior support of this team’s resubmitted Milestone 2, where the IOV Foundation responded to our questions and demonstrated that the smart contract deployment and CID storage work was actually complete. The Milestone 3 scope advances the sandbox from architecture-complete to alpha launch on Rootstock, which is the natural next step for the SSI integration and a meaningful contribution to the ecosystem’s identity infrastructure. The team has been responsive to delegate feedback and has shown a willingness to course-correct when concerns are raised, which is the engagement pattern we want to reward at the milestone stage. The proposal failing to reach quorum on this attempt is unfortunate; we would support a resubmission on the same terms.
[Grant 0806] Recognized Delegate Compensation - May 2026
We voted For: In favor of this first distribution under the new collaborative, threshold-based compensation model that Anode and StableLab have moved the program toward, with seven delegates receiving graduated amounts totaling 3,750 USDRIF for May. The shift away from a fixed tier structure where delegates effectively competed for a small number of paid spots, toward a model that rewards contribution to the ecosystem rather than relative ranking, is the healthier direction for delegate dynamics over the long run. We would be interested to see how the threshold model holds up as participation patterns evolve over the next several cycles, since the first month is necessarily a baseline rather than a steady state.
We voted For: As the prior vote didn’t hit quorum, we are voting in favor again, consistent with our support last round after the IOV Foundation demonstrated the milestone work was complete. Same terms as before and no new concerns from our end.
[Grant 0907] Recognized Delegate Compensation - June 2026
We voted For: In favor of the June distribution under the collaborative, threshold-based model, with 3,750 USDRIF split across eight delegates this cycle.
Update OpenOcean Builder Reward Receiver Address
We voted For: A routine administrative update of the address that receives OpenOcean’s builder rewards, requested by the team on the forum. It changes no reward amounts or program terms, and we have no concerns with the housekeeping update.
[2508 Grant Milestone 3] Winks.fun: On-chain actions on Rootstock within Twitter
We voted For: Milestone 2 was completed and validated, and our one reservation on Milestone 3 was its ecosystem impact, since the second reference Wink was originally left open to a generic staking, faucet, or NFT interaction. That is resolved by the team committing to build the DOC minting Wink with MoneyOnChain as the concrete second reference implementation within this milestone, with completion evidenced by the Wink live on X and mainnet DOC mint transactions traceable to the embed. Naming a real integrator and tying completion to on-chain, verifiable evidence directly addresses the verification gaps that affected earlier Winks, where broken or unhosted links made deliverables hard to confirm. The remaining deliverables, published SDK packages with CI/CD, comprehensive documentation, and a Playwright testing suite, round out the tooling for Rootstock developers, so we are comfortable releasing M3 on these terms.
[2606 Builder Activation] Stelios & Mick (Geyser Team)
We voted For: The All-or-Nothing and Prism fundraising primitives are foundational Rootstock infrastructure that the team has taken past proof-of-concept through the production Geyser deployment, which is the kind of real-world tooling Builder Activation should back. After we asked on the forum for a clearer split of Rootstock-specific activity, the team clarified that the headline $1.9M reflects three-plus years of overall Geyser volume while the Rootstock Prism and All-or-Nothing flows were only integrated in 2026, and shared the contribution volumes attributable to the RSK smart contracts. That breakdown answers our main question about Rootstock-attributable usage, so we support the activation, while encouraging the team to publish those figures as verifiable on-chain data rather than screenshots going forward.
Blockscout Global Wallet - M3 Final Milestone
We voted For: This closes out the Blockscout Global Wallet pilot on its final milestone, and the delivered scope is real, with a full Rootstock explorer integration, a fiat onramp, gas-sponsorship infrastructure, and 2,349 authenticated users at a retention rate above 18% that beat the program’s own target. The team is candid that attracting dapps to build on the wallet proved harder than hoped, but the infrastructure shipped is a genuine addition to Rootstock’s onboarding stack, and releasing the final milestone on a completed, honestly-reported pilot is consistent with how we treat grant conclusions.
[Grant 0708] Recognized Delegate Compensation - July 2026
We voted For: In favor of the July distribution under the collaborative, threshold-based model, with 3,750 USDRIF split across the eight delegates who cleared the eligibility bar this cycle.
DZap - One-Click RIF Staking on Rootstock
We voted Against: Batching swap and stake into a single transaction is a genuine UX improvement, and we are supportive of lowering the friction to stake RIF. Our concern is whether this grant produces net-new staking or mainly reroutes existing stakers through an external intent layer, since the projected early volumes are modest and a grant of this size would subsidize a large share of that throughput on a third-party platform rather than Rootstock-native infrastructure. For a convenience layer like this, we would want milestone release tied to verifiable net-new staking, first-time stRIF wallets and RIF that would not otherwise have been staked, rather than to shipping the integration and a dashboard. On the economics and the substitution question as presented, we did not think the treasury spend was justified at this milestone, though we would reconsider a version that demonstrates net-new, on-chain staking attributable to the flow.
[2601 Grant] SwaptoX Aggregator - Milestone 3
We voted For: SwaptoX delivered and validated Milestone 2, with the split-routing algorithm proven against a public SwaptoX-versus-OpenOcean comparison page and the API infrastructure migrated to Redis caching and Cloudflare, and the M3 discussion surfaced no unresolved objections to the delivered scope. Milestone 3’s 4,000 USDRIF, 45-day scope is product and developer work, a React/Next.js frontend, a Widget and Mini-SDK for third-party integration, developer documentation, and a mobile swap interface, none of which touches the contracts still under audit, so there is no reason to hold it. We support releasing M3 on the conditions the thread converged on: that the SwaptoXTimelock and multisig deployment and the 2028 zero-protocol-fee lock are validated against the final audited version before the deployment stage, and that the team publishes a clear reconciliation of what M2 committed, what was delivered, and what moved into M3. Our standing caveat is the solo-developer bus factor and that from the next milestone the measure should shift from shipped features to real, verifiable usage and adoption on Rootstock.
[2609 Builder Activation] JXLabs
We voted For: We said on the forum that we expected to support this once the text-based metrics table, the direct Blockscout contract links, and the video introduction were in place, and JXLabs has now posted all three, with DAOstar confirming the application meets the May 2026 Collective Rewards guidelines and stating it will vote in favor. The BΔLT suite is four non-custodial products already live on Rootstock Mainnet covering asset continuity, organizational treasury protection, programmable payments, and Bitcoin gifting, which is real deployed utility rather than a pre-launch promise, and the 50% Backer Reward split reads as balanced rather than extractive. Our remaining caveat is the one raised in the thread and answered candidly: the independent Coinspect audit covers the original BΔLT contracts only, while BΔLT Pro, Payments, and Gift were derived from that audited base with limited changes and have had internal review rather than separate independent audits, even though all four are live and handling user funds. Since Builder Activation is explicitly meant to fund security, monitoring, and maintenance, we are comfortable supporting it here, and we would want the next reporting cycle to show independent audit coverage extended to the three derived products together with disclosure of admin, pause, and upgrade permissions across all four.