Secret Network proposes SCRT migration from Cosmos to Arbitrum, Sept 1 snapshot

SCRT Labs — the core team behind the privacy-oriented Secret Network — published a July 7, 2026 governance post proposing to migrate the native SCRT token off its Cosmos SDK L1 and reissue it as an ERC-20 on Arbitrum. A one-time balance snapshot is planned for September 1, 2026; eligible holders would claim their new tokens through a Merkle-proof Redeemer contract. The proposal — reported by crypto.news, Cointelegraph and The Crypto Times — is not yet ratified. SCRT Labs has said it will end official support for the Cosmos-based L1 on September 1 regardless of the vote outcome; validators can keep the chain producing blocks if they choose.

What SCRT Labs is proposing

The plan on the forum has four moving parts:

1. Snapshot at Sept 1, 2026, 00:00 UTC of every eligible SCRT balance across the Secret L1.
2. New ERC-20 SCRT deployed on Arbitrum together with staking and governance contracts.
3. Merkle-proof claim through a Redeemer contract. Holders submit a proof tied to the snapshot; the Redeemer mints their share of the new token.
4. Monetary policy reset. Post-migration inflation drops from the current 9% to 5%; SCRT continues to be the governance token on the new chain.

Eligibility rules

• Included: native SCRT held in self-custodied Cosmos-format wallets, SCRT actively staked with Secret validators, and SCRT in the unbonding queue at snapshot time.
• Excluded: sSCRT (Secret-wrapped SCRT), any bridged SCRT on other chains, tokens held in smart contracts on Secret, and any SCRT held via IBC on a foreign Cosmos chain.

Holders in the excluded categories are expected to unwrap or repatriate their balances back to a native self-custodied wallet before the snapshot cutoff to remain eligible.

Why now — SCRT Labs' three stated reasons

Per the team's post and analysis relayed by Value the Markets, three drivers are cited:

• Bridge losses on legacy Cosmos integrations. The June 10 Axelar-Secret IBC bridge drain, roughly $4.67M, sat undetected for nine days and was traced to a modified ICS-20 contract on the Secret side that didn't validate source-channel and denomination-path. The team argues that older, project-specific integration code around Cosmos SDK is where the risk sits.
• AI-lowered cost of vulnerability discovery. The post argues that automated static analysis and LLM-assisted contract reading make "old code" progressively cheaper to audit offensively: "Attacks that used to take deep manual effort are getting cheaper as models get better at reading contracts, tracing assumptions, and turning a forgotten edge case into a working exploit."
• Ecosystem gravity. Liquidity, developer count, custody support and CEX rails have concentrated on Ethereum-compatible chains. SCRT Labs frames Arbitrum as offering deeper on-chain liquidity, more mature DeFi primitives, broader wallet and exchange support and a larger developer surface than what Cosmos IBC currently provides.

Numbers

- Snapshot date              : Sept 1, 2026, 00:00 UTC (proposed)
- Post-migration inflation   : 5%  (down from 9%)
- Eligibility bucket         : native + staked + unbonding SCRT
- Excluded                   : sSCRT, bridged SCRT, contract-held, IBC SCRT
- Claim mechanism            : Merkle proof → Redeemer contract on Arbitrum
- Cosmos L1 official support : ends Sept 1, 2026, regardless of vote outcome
- Chain continuation         : validators may keep producing blocks
- Vote status                : not yet passed (community vote pending)
- Governance requirement     : community approval required to execute migration
- Prior bridge loss cited    : ~$4.67M Axelar-Secret IBC drain, June 10, 2026

Figures are per SCRT Labs' forum post as relayed by crypto.news, Cointelegraph, The Crypto Times, Cryip and Value the Markets.

Impact — what this means for holders and the Cosmos region

• Self-custodied stakers need to do nothing pre-snapshot beyond staying custodied; their balance is captured directly by the snapshot.
• sSCRT and bridged-SCRT holders must unwrap/return to native SCRT before the cutoff or forfeit inclusion in the migration.
• DeFi protocols with SCRT integrations on Secret face an execution window: any SCRT sitting in a contract is excluded. Vaults and LPs must publish an unwind path if they want their users included.
• Validators face a hard fork of their business. SCRT Labs' end-of-support pulls the tooling floor out from the Cosmos L1; a validator continuation would need its own maintenance funding.
• Cosmos IBC region as a whole loses a flagship privacy chain if the vote passes — one of the earliest CosmWasm networks, and the one that best differentiated on privacy-by-default execution rather than throughput or fees. The signaling matters beyond SCRT alone.

What to watch

1. The on-chain vote and quorum. The proposal will land as an on-chain governance action on Secret. Turnout and voting-power distribution will indicate whether the migration is truly community-driven or a de facto executive decision.
2. The Redeemer contract address on Arbitrum and its audit. A Merkle-drop claim contract handling a full network's supply is exactly the class of surface area that gets probed — publication and third-party review before Sept 1 is the mechanical prerequisite.
3. Handling for excluded balances. Watch SCRT Labs' guidance for sSCRT and IBC SCRT holders — whether there's a supported unwrap path, a deadline, or a make-good mechanism.
4. Validator statements. Whether existing Secret validators publicly commit to running the Cosmos L1 after Sept 1 determines whether the chain is genuinely dual-life or effectively deprecated.

Context — Cosmos chains reconsidering their home

Secret is not the first Cosmos-era project to weigh a move off the IBC region: dYdX left StarkEx for a Cosmos SDK app-chain in 2023; more recently, several Cosmos-adjacent teams have re-evaluated whether to consolidate onto EVM-compatible L2s where user tooling, custody and CEX rails are denser. The Secret proposal is unusual in that it stacks a security argument (post-mortem-driven, tied to a specific June exploit) with an AI-attack argument (structural, forward-looking) with an ecosystem-gravity argument (backward-looking). Each on its own has been made before; SCRT Labs is asking the community to weigh all three at once.

The narrower point: the Axelar-Secret drain was a modified-ICS-20 bug, not a Cosmos SDK core bug. Whether that specific failure justifies a full L1 migration — rather than a re-audit of Secret's own bridge contracts — is exactly the argument this vote will settle.