Proposals we are NOT putting forward
Transparency about what we chose not to pursue, and why.
A responsible treasury proposal is defined as much by what it excludes as by what it includes. Treasury resources are finite, and every initiative selected means another was deprioritized. We believe the community deserves full transparency about those decisions.
During the proposal development process, we evaluated 25+ initiatives. The nine proposals presented in this portfolio represent the initiatives we believe offer the highest impact relative to cost, align most closely with the 2030 Ecosystem KPIs, and can be delivered within a 12-month window.
Below are some of the notable initiatives we chose not to include, along with our reasoning.
Due to the security-sensitive nature of this work, we believe Intersect is better positioned to coordinate its execution. Additional alignment between IO Research and the Architecture Review Committee (ARC) is also needed, and expected delivery exceeds 12 months.
Deprioritized due to bandwidth constraints and a delivery timeline exceeding 12 months. The ARC is progressing prototyping work within the scope of the 2026 proposal cycle independently.
This initiative, which encompassed Nested Transactions, DeFi Intents, and Atomic Transactions, was deprioritized due to product alignment considerations and a delivery timeline that exceeded the proposal window.
Deprioritized as a downstream dependency of Intent-Based Agentic Exchange. Without the underlying exchange framework, this initiative cannot proceed.
This work continues as part of the DB team's ongoing effort and is covered within the Maintenance and Support proposal. It does not require a separate funding line.
Deprioritized because node diversity is not a strategic product priority in this cycle. The effort to make Haskell polyglot, while valuable long-term, does not rank among the highest-impact initiatives available.
The solution is not mature enough for CBU to execute as an initiative. Progression on this front is better suited to the ARC, as reflected in their proposal.
Deprioritized does not mean abandoned. Many of these initiatives remain on the longer-term roadmap and may be proposed in future cycles as the ecosystem evolves, research matures, or dependencies are resolved.
We welcome community feedback on these prioritization decisions. Governance is a conversation, and we are committed to explaining our reasoning openly.