Cardano Dijkstra Targets Simpler Staking and More Flexible DeFi

Cardano’s Dijkstra upgrade could remove everyday obstacles for ADA holders while giving developers more flexible ways to build applications.

Speaking on Cardano Over Coffee, Input Output product manager Carlos Lopez de Lara outlined a package that includes reward withdrawals without voting delegation, nested transactions and changes intended to help smaller stake pools.

Leios remains the headline scaling feature. But these accompanying changes could shape how users experience Cardano long before they notice additional network capacity.

Reward Withdrawals Could Become Simpler

CIP-181 would remove the requirement for an active voting delegation before withdrawing staking rewards.

Today, users must delegate their voting power to a DRep or select Abstain or No Confidence before withdrawing. The proposed change would remove that prerequisite while leaving governance participation available.

For smaller stake pools, CIP-23 addresses the distribution of rewards. Carlos explained that a fixed minimum pool cost can consume much of the rewards earned by a pool that produces blocks infrequently, leaving little for delegators.

A minimum margin would provide another mechanism for compensating operators. Combined with subsequent parameter decisions, it could help smaller pools offer a more attractive proposition to delegators.

Carlos said SPO requests helped bring implementation forward. Published planning material still makes activation of the fee rule conditional on implementation and governance readiness. An immediate improvement in rewards should therefore not be assumed.

Babel Fees Could Remove an Onboarding Obstacle

Nested transactions would allow independently authorized actions to be assembled inside a larger transaction.

Carlos illustrated the opportunity through Babel fees. Someone holding a Cardano native token could express an intended swap, while another participant supplies the ADA required for the network fee.

For a new user, the practical difference could be significant: using a token without first acquiring a separate ADA balance.

The fee still gets paid. Applications would arrange who supplies it and under what terms.

That capability would give wallet and DeFi developers more freedom to organize transactions around the action a user wants to complete. Delivering a simple experience would still require application support.

Carlos also discussed account enhancements as groundwork for future small transfers. Those preparations do not establish that Dijkstra immediately makes micropayments cheaper.

[NEWSBREAK]

Wallets and Tools Must Be Ready

Dijkstra changes transaction and block structures, requiring coordinated updates across wallets, indexers and development libraries.

Carlos described a planned sequence in which node 11.2 would support testing other Dijkstra features, followed by Leios integration in 11.3. He presented those versions as development milestones, with testing determining readiness.

Governance work must proceed alongside engineering. New adjustable parameters need constitutional guardrails before the community can govern them.

The published rollout plan also distinguishes software completion targets from mainnet activation. Testnet deployment, operator testing and governance ratification require additional time.

For users, the most tangible gains could be fewer steps before withdrawing rewards or using a token. For builders, Dijkstra offers greater flexibility in how those interactions are constructed. The next task is turning that flexibility into reliable products.