Governance digests / Rootstock Collective

Rootstock Collective
digest.

Independent daily summary of public activity on the gov.rootstockcollective.xyz forum: proposals, new topics, discussion and sentiment, compiled by Anode Research.

Daily digest of public forum activityLatest edition: 2026-10-29

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.

Latest edition: 2026-10-29

Proposals and RFCs

No new grant proposals were posted in this window. Two existing proposals drew continued detail-level discussion: Predge 2610 (https://gov.rootstockcollective.xyz/t/1009) and RPCDrift (https://gov.rootstockcollective.xyz/t/1011).

New topics

None.

Discussion by topic

Topic 1009, [2610 Grant] Predge, disputable USDRIF payments without an escrow agent, Milestone 1 (Grants and Incentives):
IBUKI offered to review the draft and give feedback from running a demolition business in Japan, noting payment delays are a real problem in construction and seeing practical value; IBUKI is also developing a digital platform for the Japanese demolition industry.
predge posted the staged-payment template (v0.1) for open comment and asked for blunt feedback on anything that would not work on a real job site. The client pays and the contractor does the work; predge holds no money and takes no side, with funds sitting in a USDRIF contract on Rootstock.
Seviramar accepted the proposed disbursement conditions, that the security incident was clarified, and the commitment to publish audit quotes, findings and revised metrics before the vote. Seviramar still sought clarity on independent demand validation, including a written non-binding scope sent to 1delta for a free two-week integration assessment.
Mattsanto liked the technical approach (USDRIF via Permit2, RIF Relay, RNS) and budget alignment with Guidelines V3.3, but did not agree with the milestone structure on real adoption, raising two concrete questions starting with the removal of the "Reference Integration" fallback in M1 and M3.
Topic 1011, RPCDrift: Rootstock RPC Compatibility and Regression Testing (Grants and Incentives):
Seviramar pressed that Milestone 1 must be a decision point, not just a technical deliverable, given there are no confirmed pilot integrations yet, and asked whether continuation to Milestone 2 should be conditional on validation.
Carl agreed Milestone 1 should be a decision point based on evidence, proposing M1 validate the gap and demand before M2, starting with a source-level audit of Rootstock's existing integration tests and RPC tooling.
Mattsanto called the 12-month maintenance commitment positive but flagged concerns on both the cost estimate and the lack of validated demand on Rootstock before funding, noting 225 hours for 8500 USD works out to roughly 37.70 USD per hour and questioning the rate given AI-assisted workflows.

Sentiment

Supportive but demanding on the Predge thread. Commenters backed the technical approach and budget, yet support on the milestone structure is conditional on proving real adoption, and Seviramar is seeking independent demand validation. No outright opposition. The RPCDrift thread is mixed but constructive, with Seviramar and Mattsanto questioning cost and demand and Carl cooperating by restructuring Milestone 1 into an evidence-based decision point.

What to watch

No votes opening or closing in this window.
predge has committed to publishing audit quotes, findings and revised metrics before the vote on topic 1009.
Delegates are pressing to make RPCDrift Milestone 1 a decision point gating Milestone 2 (topic 1011).

Permalink to this edition ↗

Rootstock Collectivedigest.