Cardano Over Coffee: Leios, Timelines and Stake Pools

Leios and preparations for Dijkstra became a central topic in Friday’s Cardano Over Coffee. James, known as Blockjock, EPOCH, Ken Erik, Christina and Angry explored how the upgrade could reach users and what it might mean for the people maintaining Cardano.

Between stories about school days and first cars, the group worked through practical dilemmas: how much preparation is enough, what operators can afford, and how teams should explain additional funding needs.

Leios Readiness and the Pressure to Deliver

James questioned how the community would receive an initial release with limited functionality after years of expectations around Leios, Cardano’s proposed capacity upgrade. He worried about a gap between the scale of those expectations and what users might experience at first.

EPOCH challenged the reason for accelerating development. Against what he described as a difficult market backdrop, he wanted a clearer explanation of the benefit of an earlier release.

“So if risk is high and the value is low, then why rush?” he asked.

His concern extended to developers continuing to build through quieter market periods. Unnecessary urgency, he argued, could exhaust teams before a more demanding period of growth and activity.

He also pushed back on allowing potential negative coverage to influence engineering decisions. Criticism would exist regardless of the outcome; his preference was to work methodically and maintain the network’s own standards.

Ken Erik offered his personal estimate that Dijkstra activation could take until March or April 2027, recalling pushback from people expecting an earlier result.

He viewed the roadmap as ambitious and emphasized the additional work that can emerge when research becomes implementation.

He remained optimistic about the upgrade. Problems discovered during development were challenges the ecosystem had the expertise to address, provided teams had time to fix and test them.

James later explored the case for introducing capabilities in stages. Could the necessary foundation be activated first, with further functionality added afterward? Would those additions require another hard fork? His questions moved the conversation toward how a gradual rollout could work in practice.

Stake Pool Costs and Home-Based Operators

Christina brought the discussion to infrastructure requirements. She wanted clearer communication about what stake pool operators, or SPOs, would need to run Leios.

Connectivity was a particular concern for people operating equipment from home. A computer can be upgraded, but access to a suitable internet connection also depends on location and service providers.

Cloud hosting offered another route, although the group discussed its recurring costs. Smaller customers, Christina noted, cannot necessarily expect the discounts available to larger operations.

Ken Erik believed operators could continue using machines outside large data centers, with appropriate connectivity, storage and processing resources. Angry similarly expected many existing setups to meet the basic requirements, with demands changing as network parameters increased.

He added a joke about older equipment: the Pentium 4 would have to be retired.

James kept returning to the business calculation. Even manageable hardware requirements could create difficulties for a pool whose ADA income already struggled to cover its bills.

That distinction surfaced when Ken Erik described running his own relay node. For him, the monthly expense was a contribution to Cardano and a way to understand the network. James observed that this motivation had a different financial basis from a pool operating as a sustainable business.

The group also questioned how operator numbers should be understood. EPOCH compared Cardano with networks running far fewer validators, while Ken Erik challenged the assumption that every additional node provides the same improvement in resilience.

James raised a related governance question. Some SPOs also serve as DReps. If operators left the staking business, would they continue representing delegators in governance, or could their departure also affect voting participation?

Funding Development When Plans Change

Development schedules also have a financial side. James discussed salaries, team expenses and milestone payments, asking how those pressures might influence delivery decisions.

For teams supported through ADA grants, completing a phase of work can determine when further funding becomes available.

Ken Erik asked what would happen if finishing the upgrade required additional money. James anticipated resistance to another request, particularly after earlier discussions about efficiency and constrained budgets. He also considered the consequences of withholding funding needed to complete years of work.

Ken Erik illustrated the dilemma with a car repair. A customer agrees to a price, but the mechanic discovers another problem during the job. Does the owner accept the additional cost to get the vehicle working?

James focused on the explanation behind the new bill. An unexpected fault can justify further work; a poor initial estimate raises different questions. For development funding, he wanted to understand what had changed, what remained necessary, and why it had not appeared in the original plan.

Near the end of the show, Christina returned to a task already on her screen: reviewing a project’s milestone documentation. She was opening links and checking evidence against the promised deliverables, “because it’s got my name on it, dude.”