Deployed zkApps lost proof authorization after the chain restart until keys are updated.
CryptoSlate reported that Mina’s Mesa upgrade paused transactions for eight hours and made existing zkApp verification keys incompatible. The chain restarted afterward. Deployed apps cannot resume proof-authorized activity until developers compile and post Mesa-compatible keys. The article states that zero-knowledge apps went dark after the chain upgrade broke their underlying verification keys. It adds that the Mina Mesa upgrade completed after the eight-hour pause yet deployed zkApps still need new verification keys to resume proof-authorized activity. No other details appear in the supplied evidence.
1.2K
1 post, first seen 3d ago
Deployed zkApps lost proof authorization after the chain restart until keys are updated.
CryptoSlate reported that Mina’s Mesa upgrade paused transactions for eight hours and made existing zkApp verification keys incompatible. The chain restarted afterward. Deployed apps cannot resume proof-authorized activity until developers compile and post Mesa-compatible keys. The article states that zero-knowledge apps went dark after the chain upgrade broke their underlying verification keys. It adds that the Mina Mesa upgrade completed after the eight-hour pause yet deployed zkApps still need new verification keys to resume proof-authorized activity. No other details appear in the supplied evidence.
CryptoSlate@CryptoSlateMina’s Mesa upgrade paused transactions for eight hours and made existing zkApp verification keys incompatible. The chain has restarted, but deployed apps cannot resume proof-authorized activity until developers compile and post Mesa-compatible keys.
CryptoSlate@CryptoSlateMina’s Mesa upgrade paused transactions for eight hours and made existing zkApp verification keys incompatible. The chain has restarted, but deployed apps cannot resume proof-authorized activity until developers compile and post Mesa-compatible keys.
