Peapods Pulls Most Layer-2 Liquidity After Abnormal PEAS Minting
Peapods Finance says a possibly compromised deployer key was used to set minting permissions and create PEAS tokens on a layer-2 network that were bridged to Ethereum and sold, and the team has removed 98 to 99 percent of its layer-2 liquidity while users exit positions.
Edited and fact-checked by Stephen Sprague
One master key could mint what the market had to price as real supply, and the completed review has to count tokens that should not exist.
Peapods Finance told users on November 19 that PEAS tokens had been minted abnormally on a layer-2 network. The team's preliminary assessment blames a deployer private key that may have been compromised, because that key had been used to set minting permissions on the layer-2 contracts. The minted tokens crossed a bridge to Ethereum mainnet and were sold into market liquidity.
A deployer key is the master credential a protocol keeps from launch day, and it carries powers ordinary users never see, because whoever holds it can grant minting rights. In this incident the key's authority was used to create tokens the protocol never issued through its own process, while Peapods says PEAS can't be minted directly on mainnet. The mainnet exposure runs only through liquidity that was already bridged there.
The team's containment step removed most of the pool users trade against, because Peapods says it pulled about 98 to 99 percent of its layer-2 liquidity to limit further extraction by the attacker. The team says selling pressure on PEAS has been contained, and a liquidity pull of that size protects what remains in the pool, while it also strands the market. Holders who want to exit a thin pool move the price against themselves with every sale.
The instruction to users was broader than the pool, because Peapods advised users to temporarily remove all on-chain liquidity provider and leveraged yield farming positions while the investigation and recovery work continues. Those positions sit outside the main pool in leveraged strategies built on Peapods contracts, and the team's warning treats them as exposed until the team says otherwise.
For businesses
Amazon Business is Amazon’s purchasing store for companies, with business accounts and quantity ordering.Register with Amazon BusinessThe missing number in this incident is the loss total, and its absence is part of the record, because no confirmed figure for the value minted or taken has been published. Incident trackers list the amount stolen as not yet known, and the team's own language stays preliminary throughout, since a key that may have been compromised is an assessment rather than a finding. The post-incident review is still running, and the incident sits in the DeFiLlama hacks database with the deployer-key cause recorded and the stolen amount left blank. That listing shape tells holders the event is verified while its size isn't.
Peapods says it's attempting to recover funds taken in the incident while the review proceeds, and recovery in a minting case runs through the bridge and exchange trail the sales left behind. Its success turns on whether the proceeds reached a service that can freeze them, while the team has published no recovery amount, no address list and no contract migration plan. Holders are working from the team's short statements alone.
The practical divide for a PEAS holder is between the two networks, because the layer-2 pool is nearly empty by the team's own choice and its positions sit under an exit advisory. On mainnet, no new PEAS can be created, and the risk is the bridged supply already sold or still moving, so the next document that matters is the completed review. It has to convert a preliminary key story into an accounting of how many tokens exist that shouldn't.
Sources
The conversation.
Loading comments…
A little more perspective.
Reading is free. Verified members can comment and reply for $2 a month.