Phantom Wallet Experiences Downtime Following Grass Airdrop

Highlights: 

• The Grass Airdrop caused major disruption for Phantom Wallet, affecting numerous users.
• The Grass Airdrop gave 10% of the GRASS token supply to 2 million users, marking a record-breaking event.
• Despite the wallet’s difficulties, the Solana network remained stable, demonstrating its resiliency during peak demand occasions.

Phantom Wallet, the most popular wallet for the Solana blockchain, experienced downtime today. People flocked into the network to grab the highly anticipated airdrop. The wallet’s back-end systems were unavailable for several hours, leaving many unable to check balances or perform transactions.

Advertisement

🚨 BREAKING: @phantom wallet is experiencing downtime due to a major backend incident. pic.twitter.com/dsAm2lM2td

— SolanaFloor (@SolanaFloor) October 28, 2024

Massive Grass Airdrop Overwhelms Wallet

The Grass airdrop is among the greatest token giveaways in blockchain history. It plans to give 10% of the total GRASS token supply to more than 2 million active users. Grass is a Solana-based platform that allows users to monetize their surplus network bandwidth. This bandwidth helps train artificial intelligence models and analyze large amounts of data. This is a huge milestone for Grass and the Solana community.

When the airdrop went live, hundreds hurried to get their GRASS tokens. As a result, the Phantom Wallet backend could not handle the rapid rise of traffic. The company’s status page confirmed the major incident. The backend had been down for about an hour.

Phantom Wallet assures consumers in an official notification that their cash is safe. They added that they are striving to rectify the situation as soon as possible. The outage impacted both desktop and mobile users. Many others voiced frustration since they were eager to participate in the airdrop.

We're currently experiencing an uptime incident and some services may be temporarily disrupted.

If you are in urgent need of making a transaction, please ignore simulation errors and try using a dapp.

Thanks for your patience as we work to resolve the issue 🙏

— Phantom (@phantom) October 28, 2024

The Scale of the GRASS Airdrop

The GRASS Airdrop One was no small accomplishment; it was one of blockchain’s largest token deployments. Grass, a decentralized platform for AI data infrastructure on Solana, marked a new milestone with the event, intended to reward users who provided bandwidth to its network.

Grass allows users to monetize idle bandwidth, which is then used to train decentralized AI models. The airdrop distributed 10% of GRASS’s total token supply, or an astonishing 100 million tokens, to build a devoted user base ahead of its formal listing on markets.

During the platform’s beta phase, early players acquired “Grass Points” that could be turned into GRASS tokens during the airdrop. The magnitude of this event demonstrates blockchain’s potential for token distribution and user involvement. However, it has highlighted significant infrastructure issues.

Resilience in the Solana Network During Wallet Downtime

Meanwhile, Solana’s core network remained steady despite the large transaction volume tied to the airdrop, while Phantom suffered operational difficulties. Solana’s infrastructure was able to handle an increase in load as their blockchain could not even be brought down. For Phantom users, however, the experience was less seamless. This incident as sparked serious concerns among the cryptocurrency community with regard to the strength of the wallets by the infrastructure of the platforms that anchor blockchain ecosystems.

This year, Phantom has faced downtime on several occasions already. Earlier this year, Phantom had similar troubles, most recently on October 3. Users experienced delays when balance updates and the wallet provider fixed these issues immediately. 

In regard to the latest outage, the Phantom team is working to restore full service and keep users updated on the resolution status. Phantom has not yet revealed explicit data about the main problem. However, they revealed backend overloads played a part in the issue.

Advertisement