Cardano Rosetta Java v2.1.0 is live with full Conway-era governance support, SPO Voting, DRep Delegation, and CIP-129 across all endpoints.
The Cardano Foundation shipped something developers have been waiting on. Cardano Rosetta Java v2.1.0 is live, and it brings full Conway-era governance support to both construction and data endpoints. As Cardano_CF announced on X, the update covers SPO Voting, DRep Vote Delegation, CIP-129, and more.
That’s not a small thing. Governance operations are now visible inside the API. Developers no longer need workarounds.
Must Read: From Legacy Rails to Blockchain: Why Big Banks Are Betting on Tokenization
What Changed Inside the API
According to the official v2.1.0 release notes on GitHub, the update was authored by matiwinnetou two weeks ago. SPO Voting and DRep Vote Delegation now appear in both construction and data endpoints. Operations sort by index in ascending order. That last part is small, but it was causing headaches.
CIP-129 support is now baked in. DRep IDs with a 29-byte prefixed header no longer need an explicit type field. The API infers the type automatically from the header byte. Raw 28-byte IDs still need type declared manually.
The /block, /block/transaction, and /search/transactions endpoints now return VOTE_DREP_DELEGATION and POOL_GOVERNANCE_VOTE operations for Conway-era transactions.
You Might Also Like: Ripple’s $550M XRPL Expansion Could Ignite XRP Demand
The Breaking Change Developers Must Know
There’s one breaking change. HTTP status codes are now aligned with actual error classifications. All non-retriable errors return 400 Bad Request now. Previously, validation and not-found errors returned 500 Internal Server Error. Clients built around catching 500s need to update their error handling before upgrading.
The Cardano Foundation was direct about it in the release notes. No soft framing.
Upgrade Path and What Gets Reset
For users coming from v2.0.0, this release is fully compatible. No resync needed. That’s a clean path for most current deployments.
Coming from v1.x.x is a different story. A full genesis resync of the yaci-indexer is required. Cardano Node data can stay; only the indexer data needs to go. The release notes include a data volume removal procedure.
Node version moves from 10.5.3 to 10.5.4. Yaci also bumps from 0.10.5 to 0.10.6. And there is now an experimental admin UI for the indexer sitting at http://yaci-indexer:9095/admin-ui/.
The Cardano Foundation confirmed this is not a mandatory release. Teams can plan the upgrade on their own timelines.
Also Trending: WildMeta Integrates Aster DEX to Expand Web3 Crypto Trading Discovery
What the Conway Era Actually Means Here
The Conway era is Cardano’s Voltaire phase. Decentralized governance. On-chain voting. DReps. SPO participation in governance decisions. It’s the part of the roadmap that turns ADA holders into actual decision-makers on protocol changes.
Rosetta is the API layer that exchanges and builders interact with. Without governance operations in it, those institutions had a blind spot. v2.1.0 closes that.
As @Cardano_CF put it on X, full Conway-era governance support is now available. That phrasing matters. Not partial. Not experimental. Full.
The contributors behind the pull requests include @matiwinnetou, @linconvidal, and @Sotatek-DucPhung. Several PRs went in to get this across the line, including governance data endpoint tests with golden examples and an Allure3 migration for the test suite.
Related: ETH Funding Flips Positive as $262M Inflows Break 35-Day Slide
Cardano’s infrastructure layer just got more complete. Builders working with governance-heavy applications now have what they need inside the standard API.
