Governance digest / Rootstock Collective

Rootstock Collective digest,
2026-09-19.

1delta Intents drew three FOR delegate votes on T1; 2609 Yield Vault debate turned to valuation methodology; three builder deactivations voted.

Window: 2026-09-18 09:00 to 2026-09-19 09:00 UTCPublished 2026-09-19 UTC

Independent daily summary of public forum activity, compiled by Anode Research. Not an official communication of Reserve or Rootstock Collective. Anode participates in both as a delegate.

Proposals and RFCs

[2609 Grant] Rootstock Yield Vault: immutable ERC-4626 rBTC vault across LayerBank and Sovryn - Grants & Incentives - https://gov.rootstockcollective.xyz/t/970

New proposal under active discussion (no onchain link yet). Requests $25,000 in USDRIF for an immutable ERC-4626 rBTC yield vault routing deposits between LayerBank and Sovryn on Rootstock: permissionless rebalancing, no admin/upgrade controls. $15,000 earmarked for a Coinspect audit, remainder split across four milestones.

New topics

None.

Discussion by topic

[2609 Grant] Rootstock Yield Vault (Grants & Incentives, topic 970)

  • iamChekwube (proposer): summary of the $25k ask + milestone funding split.
  • Mattsanto (probing/supportive): the filter shouldn't be "does today's APY justify $25k"; LayerBank mostly uses rBTC as collateral and Sovryn has weak support. Argues dual-venue + 60% cap + redeemInKind matter as an exit when a protocol's withdrawal path breaks, more than spot yield.

[2608] 1delta Intents: permissionless solving on Rootstock (Grants & Incentives, topic 929)

  • Josedrybit (concern): security: how safe is the protocol against a malicious solver or settlement-contract vulnerability, given AI-accelerated exploit discovery?
  • Mattsanto (supportive): USDRIF exit problem is real and measurable; signed outcomes, competing solvers, partial fills fit a shallow market better than "hope the AMM rebalances."
  • Achthar (author): to Josedrybit, comprehensive unit tests added to the settlement contract (github.com/1delta-DAO/1delta-X) covering malicious orders, reentrancy, fake modules, and known historical solver incidents. To Mattsanto, all four points covered in the post-21 changes: M2 with $10k or more settled by independent solvers, M3 with $50k or more, M4 with $150k or more (plus 12-month impact review); notes 43% of grant is releasable before any independent volume is shown.

Delegate votes

  • Tané Delegate Thread (t/463): Achthar agrees 1delta should submit onchain as Milestone 1, but flags the guideline probably should not carry an onchain milestone tag; suggests a guideline fix.
  • Curia Delegate Thread (t/438): Curia voted FOR 1delta Milestone 1 (T1). Revised tranche structure addressed prior concerns; M1/M2 as useful checkpoints.
  • DAOstar Delegate Thread (rev) (t/711): DAOstar_gov voted FOR three Builder Deactivation Proposals: Tally, Tropykus, Boltz, all ceased operations, so deactivation keeps the roster accurate.
  • SEEDGov Delegate Thread (t/774): SEEDGov voted FOR 1delta Milestone 1 (T1). T1 covers the smart-contract audit, essential since contracts are immutable/ungoverned once deployed.

Sentiment

  • 1delta Intents: Supportive. Three aligned FORs (Curia, SEEDGov) and author engagement; the only concern (Josedrybit's security Q) was credibly answered. Strong momentum on the T1 tranche.
  • Rootstock Yield Vault: Mixed/probing. A valuation-methodology debate (spot APY vs. exit-path resilience) shaping criteria; no delegate votes yet.

What to watch

  • Guideline change flagged (Achthar, t/463): whether Milestone-1 submissions should carry an onchain milestone tag, a potential governance-docs fix.
  • 1delta T1 vote settling: three FOR votes already in; the 43%-release-before-independent-volume structure is part of the record before it closes.
  • Three builder deactivations (Tally, Tropykus, Boltz) voted FOR in one sitting, a routine deroster.