Developer Experience (JAPANESE)
Improving the end-to-end Cardano developer experience to drive adoption and active users.
The team behind the initiative
The opportunity
Cardano’s security model and native asset support has always attracted serious builders. However, its powerful yet challenging UTXO model and fragmented tooling ecosystem has never made Cardano the easiest of lifts for new developers. As Cardano's governance model continues to mature and new integrations become available, more developers are taking notice. And what turns that interest into shipped products - and the potential for growth these bring - is the experience between 'I want to build here' and 'my DApp is live.'
Consolidating tooling, strengthening documentation, and shortening the path from first contact to a working application will compound across the ecosystem. Each developer who ships successfully becomes a signal to the next one.
The Initiative
Developer Experience (JAPANESE)
This proposal funds a focused program to streamline Cardano's developer tooling, documentation, and onboarding experience.
The work connects directly to CBOR standardization and contract specification languages. CBOR makes data smaller, faster, and more reliable for computers to process. This helps developers build and run applications on Cardano more efficiently and at lower cost, improving the experience developers have across the entire build lifecycle.
The scope covers six to nine months of work. Deliverables include improved SDK tooling, consolidated documentation, better error handling and diagnostics, and smoother pathways from prototype to production.
Who is building
This initiative is led by Robertino Martinez at Input Output Group, coordinated through Intersect.
Full stewardship of developer relations will transition to Pragma and the Cardano Foundation by the end of 2026. Their combined community reach and global presence, and developer expertise make them the natural long-term home for this work. IO is funding and delivering this year's program while ensuring a strong handoff of relationships, processes, and institutional knowledge.
Expected outcomes
- Reduced time-to-first-DApp for new developers joining the ecosystem.
- Measurable improvements in developer satisfaction scores and documentation coverage.
- Higher conversion rates from developer onboarding to active project deployment.
Ecosystem Impact
When developers succeed, the entire ecosystem benefits. More shipped products means more users, more transaction volume, and more economic activity flowing through the network. This initiative directly supports the 2030 Ecosystem KPIs for MAU and Revenue/Adoption, while enabling improvements in Monthly Transactions and TVL through better tooling.
Governance links
Formal treasury proposal
The on-chain submission, read the full proposal text and rationale.
View the formal proposalDiscussion forum
Ask questions, share views, and follow the community debate.
Go to the discussion forum