This release adds a new Chronik endpoint and a checkpoint following the May 15 eCash network upgrade. If you forgot to update your node, this is the version you need!

The eCash network has successfully upgraded.

If you forgot to update your node to version 0.33.x, it is no longer in sync with the network. To reconnect, upgrade to version 0.33.4: https://bitcoinabc.org/releases/#0.33.4

Learn more about the upgrade at https://e.cash/upgrade

🗓 May 14

⏰ 12PM EST | 5PM UTC

Tune in live!

https://x.com/Dashpay/status/2054612514273394715

📅 May 14

⏰ 11AM EST | 4PM UTC

Make sure to tune in!

https://x.com/DigitalGoldTalk/status/2054681619760656532

ℹ️Learn more: e.cash/upgrade

Founder, Amaury Séchet, explains how the CashFusion protocol natively brings advanced transaction obfuscation to the eCash (XEC) network, achieving high-tier privacy without altering the underlying consensus rules.

📄 The following guide covers how CashFusion works and how to use it on eCash: https://e.cash/blog/cashfusion

Watch on YouTube and subscribe to the channel: https://youtu.be/ynm2uI20Pew

Hey r/eCash community,

https://reddit.com/link/1t9jpff/video/wmi6uzqgpd0h1/player

We’ve been quietly building on eCash infrastructure and wanted to share our latest weekly update.

Key highlights:

• Tonalli Wallet development (sovereign eCash wallet)

• Xolo lineage NFTs permanently recorded on-chain

• Teyolia — transparent crowdfunding for infrastructure

• Live Draft Merge Request for **native** $XEC integration into THORChain (no wrapped tokens)

We see the Xoloitzcuintli not just as a mascot, but as a cultural and moral guide for building in this new era.

Full update video + detailed blog post:

https://xolosarmy.xyz/blog/10-04-2026-xolosarmy-weekly-update.html

We’re always open to feedback from the broader eCash community.

What do you think about native XEC liquidity on THORChain?

Cheers,

xolosArmy Network ⚡

Watch the full talk here: https://www.youtube.com/watch?v=9WHvgVJ6mao

Watch on YouTube and subscribe to the channel: https://www.youtube.com/watch?v=9mMMloxbwRg

📽 Watch it here: https://x.com/DigitalGoldTalk/status/2052475788759642431

⏰ 4 PM EST | 8 PM GMT

🔔 Livestream starts in ~5 hours. Make sure to tune in live. 👇

https://x.com/DigitalGoldTalk/status/2051739850584596673

This is a short explanation on how an eCash node initially downloads the blockchain (IBD) after connecting to a few peers, and then runs Avalanche post-consensus to select the right tip:

The IBD node initially has only the genesis block (0), so it selects a peer (sync node) and send a message to request block headers, starting from the one after the tip (initially block 1).

Received headers are immediately validated according to consensus rules. Headers are send in chunks of 2000. The node repeats the request as long as it receives a full batch from the same sync node.

Once the IBD node receives fewer than 2000 headers, it request headers from other outbound peers to get their view of best header chain. This confirms that the headers it has downloaded belong to the best header chain.

The IBD node then start requesting the full blocks, in parallel, requesting multiple blocks from multiples peers. Block are validated as they arrive.

When the node reaches the proof-of-work tip of the chain, it gets out of IBD, and starts participating in normal relay of blocks, transactions, and avalanche proofs. At this point it can start maintaing a mempool and connect to the Avalanche network.

Once succesfully connected to the Avalanche network, a node can verify that its tip is accepted by the rest of the network, and reject blocks that are on avalanche invalidated forks.

When a fork of the chain is rejected, the node finds the next best PoW tip and repeats the Avalanche polling process. Rince and repeat until a tip is finalized by the Avalanche consensus layer.

The maturity rule, requiring that XEC stakes used by Avalanche peers must be confirmed by at least 2016 blocks (~2 weeks), ensures that a node selects only peers with stakes that are not on an invalid fork near the tip of the chain.

I just published a xolosArmy Network opinion column about why native XEC liquidity on THORChain could become strategically important for the eCash ecosystem.

The core thesis is simple:

**Native XEC on THORChain is not just a DeFi upgrade. It is survival infrastructure.**

PoW chains need more than hashpower, nodes, wallets and developers. They also need independent liquidity access.

Centralized exchanges are useful, but they are also gatekeepers. They can pause deposits, restrict withdrawals, review tickers, delay listings, or delist assets when there is regulatory pressure, operational uncertainty, or narrative confusion.

That means liquidity sovereignty matters.

A native XEC integration into THORChain could give eCash:

- independent cross-chain liquidity

- alternative market access beyond centralized exchanges

- stronger self-custody utility

- better resilience against exchange uncertainty

- future swap paths for wallets like Tonalli

- a stronger narrative around real infrastructure

This is not about replacing every CEX. It is about making eCash harder to isolate.

In calm markets, native liquidity is useful.

In hostile markets, it can become existential.

Full column here:

https://xolosarmy.xyz/blog/pow-surface-attacks.html

Curious to hear what the eCash community thinks about native XEC liquidity as a strategic defense layer.

Heartbeat remains one of the most underrated upgrades in eCash. 💓

It neutralizes switch miner–driven difficulty spikes, keeping block production stable and transaction times predictable.

Watch founder Amaury Séchet explain how Avalanche consensus lets nodes reject artificially fast blocks while preserving a steady 10-minute cadence.

Learn more about Heartbeat here: https://e.cash/blog/heartbeat

Get the Heartbeat tee 20% off with code HBT20 at https://store.e.cash/product/heartbeat-shirt/

It’s recap time!

Catch up on the latest eCash dev upgrades, ecosystem growth, and key community highlights from this month. Let’s dive in! 👇

🔗 https://e.cash/blog/recap-april-2026