According to Cointelegraph: The Canto blockchain has been experiencing a 33-hour outage caused by a consensus issue, with the team planning an upgrade on August 12 to resolve the problem. This Cosmos-based layer-1 blockchain, launched in August 2022, is designed for decentralized finance (DeFi) applications and is compatible with the Ethereum Virtual Machine (EVM).
According to the CantoScan block explorer, the last transaction on the Canto blockchain was recorded at block 10847516 at 2:29 a.m. on August 11. The blockchain has since been inactive, with no new transactions logged on Etherscan in the last 33 hours and only two transactions in the last 46 hours.
![](https://public.bnbstatic.com/static/content/live-admin-api/images/tBCNcThpEfawSZSte8KaEB.jpeg)
In an August 12 update posted on Canto’s official social media account on X (formerly Twitter), the team confirmed that a "consensus issue" is behind the outage but provided few additional details. The team has scheduled an upgrade to address the issue at 12:00 p.m. UTC on August 12.
A consensus mechanism is crucial for validating transactions on a blockchain, marking them as authentic, and adding them to the blockchain ledger. The team assured users that all funds are safe and that normal functions will resume once the upgrade is complete.
Despite the ongoing outage, Canto has reassured users that they should not be alarmed, stating, "All funds are safe. Once the chain resumes, users will be able to access all activities as usual."
The Canto blockchain had previously announced plans to migrate to the Ethereum Network in September 2023 and become a layer-2 network, but this decision was reversed in March 2024, and it has remained a layer-1 blockchain.
Activity on the Canto blockchain surged in February 2023, but it has since declined, currently ranking as the 80th largest blockchain by total value locked, according to DefiLlama data.
The Callisto upgrade, which was scheduled for August 9, has not been addressed by Canto in relation to the current outage, leaving questions about whether it was successfully implemented or if it may have contributed to the issue.