Thanks to all who showed up for the Q1 Community Call on 04/16. A full recording is available here and embedded below.
It ran about 90 minutes and covered four major topics:
RSR Delegate Program: six community delegates now active across four Yield DTFs, with @Raphael_Anode walking through how the program came together and what to expect going forward
Q1 engineering updates: protocol releases, Optimistic Governance progress, the upcoming Zapper overhaul, the Register repaint, and how AI tooling has reshaped the engineering team’s velocity
First quarterly financial report: full revenue “waterfall,” the NARR (net annually recurring revenue) methodology we’ll be using going forward, RSR burn YoY, and Confusion Capital treasury operations
RSR unlocking proposal: a milestone-based model to replace the Bitcoin emissions curve, with the first milestone tied to $2.5M in annualized net revenue
Plus a live demo of Scout, the internal AI tool we’re using to ideate, backtest, and evaluate DTF strategies in our search for product-market fit.
If you have thoughts on anything covered in the call, drop them below. @nevin.freeman will make a separate post specific to the RSR unlocking proposal.
Hey @starl3xx, thanks for putting this together and posting it on the forum.
Would it be possible to post Reserve’s Q1 Financial Report as a standalone post? It’s a significant report which protocol decisions and possible future RSR unlocks depend on it seems a shame to leave it nested within the community call recap.
It could then also follow the SOPs adopted by the Yield DTF reports.
Superb update structure, format, and post-share. Thank you.
OPEN DTF community is excited to put some cycles into using Scout for test and explorations with the OPEN DTF. Let us know its ready. Fwiw Codex maxi here.
On 5.0.0 adoption: the smart contract world is nervous by default. A Reserve blog post explaining the what, when, how, and benefits of 5.0.0, with audit links, would help a lot. I’d also suggest an explicit Reserve docs update.
Hopeful the RSR unlocking proposal will utilize “cant be evil” web3 onchain immutability. Clear immutable rules make it easier for investors and builders far and wide to understand, adopt and compound on rules of the system.
Would suggest submitting RSR to Aragon’s Ownership Token Framework (OTF), Blockworks Token Transparency Network (TTF) and DefiLlama’s Token Rights Framework (TRF). Submissions can likely be completed in half a day, are free, and create useful transparency for the industry. More here: https://x.com/0xJMG/status/2051342977528942893
re: Permanent burning. There really is no such thing as permanent (not to be confused with a protocol’s version immutability). Technically, any protocol can fork to a new token with new parameters anytime. Only blockers would be social consensus or legal objections.
Example: Already seeing momentum within ~5 years to see Bitcoin fork to quantum security upgrade. While that upgrade won’t address Bitcoin’s 21 million supply, it technically could with same social consensus or legal objections.
Many protocols will be confronted with this conundrum in the next decade. And while it may be an unpopular topic under 2026 circumstances, they will have to “cross that bridge when they get there” and will do what’s best for the network at that time.
Recommend do whats best for RSR ecosystem adoption in 2026-28, as there will be many new bridges to cross over the decades ahead.
Food for thought.
Appreciate the public updates and thank you team for the hard work.
