Proposal: [2508 Grant Milestone 3] Winks.fun: On-chain actions on Rootstock within Twitter
Vote: Against
Rationale:
Under the 2026 grant guidelines’ FES lens, M3 as scoped doesn’t demonstrate measurable, verifiable on-chain impact. The one component that could generate real activity (MOC DOC-minting) lacks a described attribution mechanism to trace transactions to Winks, and as of this vote, lacks confirmation from MOC itself.
Our vote was also informed by our inability to review the sample links provided, as X has flagged them as unsafe/spammy. This was raised by other delegates and explained, but it undercuts the product’s core value proposition regardless of SDK quality — and perhaps should have been resolved before M3 was brought to a vote.
Proposal: **[2606 Builder Activation] Stelios & Mick (Geyser Team)
Voted: FOR
Rationale:
The AON grant in this DAO is showing on-chain traction, growing month over month (0.013 → 1.164 RBTC, Dec–May). The Backer-Reward % mechanism is a reasonable amplifier on top of proven activity. We also like that Prism emerged directly as a byproduct of the AON grant work — a good sign that grant is compounding into more Rootstock infrastructure than originally scoped.
Two items we’d like to see followed up post-activation rather than treat as blockers: whether Prism has been audited, and clarity on admin/owner key permissions across both contracts, per @krngill questions. We’d also encourage @Stelios and team to reconcile the dashboard’s “Last 7d” figures, which currently mix weekly and monthly data — useful for delegates tracking impact going forward.
Supportive of activation, and looking forward to those clarifications.
Proposal: Blockscout Global Wallet - M3 Final Milestone
Voted: FOR
Rationale:
Voting FOR with a bittersweet outcome — the core adoption goals weren’t reached, most notably dapp integration — but Blockscout made a clear, honest effort to learn from it and adjust.
They shipped what they promised on infrastructure, exceeded the retention target, and closed out returning budget.
The team’s candor is welcomed: they name specifically what didn’t work (dapp outreach, gas sponsorship) and translate it into concrete suggested fixes.
It is also a good supporting case for elements of the new grant guidelines— demand validation before funding, a gated final milestone, fixed KPIs end to end.
Proposal: Recognized Delegate Compensation - July 2026
Voted: FOR
Rationale:
Voted in favor of the published results — the defined criteria was applied and diligently evaluated. This is the 3rd month under the new compensation guidelines, so it’s still early to confirm whether all intended objectives are being achieved.
Proposal: DZap — One-Click RIF Staking on Rootstock
Vote: Against
Rationale:
There are errors in title format, amount quantity and rBTC was used instead of USDRIF.
Proposal: [2601 Grant] SwaptoX Aggregator – Milestone3
Voted: FOR
Rationale:
Supporting M3. Grateful to Anode’s milestone analysis clarified and shared an itemized picture of where M2 actually stood — and it also gave SwaptoX the opportunity to respond and show progress addressing points delegates had raised.
Separate from the audit conversation currently being handled in parallel by the Collective, I’d ask SwaptoX to publish a simple reconciliation:
-total grant funds received to date
-what’s been delivered against each milestone’s original scope
-what remains outstanding (including anything deferred from M2 into M3 or beyond).
This is a request for a clean, single reference point so delegates and the builder are working from the same picture of where things actually stand, independent of how the audit question resolves.
Proposal: [2609 Builder Activation] JXLabs
Voted: For
Rational: We voted in favor of this Builder Application application, as JXLabs has more than demonstrated an aligned project that is robust, and provides a clarity in their mission, dedication and intention of a long-term aligned with Rootstock.