{"id":120483,"date":"2023-07-10T19:53:20","date_gmt":"2023-07-10T19:53:20","guid":{"rendered":"https:\/\/dripp.zone\/news\/connext-founder-proposes-sovereign-bridged-token-standard-after-multichain-incident-crypto-news\/"},"modified":"2023-07-10T19:53:24","modified_gmt":"2023-07-10T19:53:24","slug":"connext-founder-proposes-sovereign-bridged-token-standard-after-multichain-incident-crypto-news","status":"publish","type":"post","link":"https:\/\/dripp.zone\/news\/connext-founder-proposes-sovereign-bridged-token-standard-after-multichain-incident-crypto-news\/","title":{"rendered":"Connext founder proposes ‘Sovereign Bridged Token’ standard after Multichain incident\n – Crypto News"},"content":{"rendered":"
\n

An Ethereum Improvement Proposal (EIP) made on July 7 seeks to standardize how tokens are bridged between networks. The \u201cSovereign Bridged Token\u201d standard, or EIP-7281, allows token issuers to created<\/a> Canonical bridges across multiple networks. <\/p>\n

The proposal was co-authored by Arjun Bhuptani, founder of the Connext bridging protocol. In a July 7 social media post, Bhuptani claimed<\/a> the protocol would help prevent issues like the July 6 Multichain incident, which some experts have been described as a \u201chack.<\/a>,<\/p>\n

\n

Today’s @MultichainOrg<\/a> The hack is a sad reminder of the systemic risks tokens face from bridges.<\/p>\n

We believe these risks stem from a single underlying problem:<\/p>\n

\u2728Token Sovereignty\u2728<\/p>\n

We’re proposing ERC-7281 (aka xERC20) – an open standard to fix this.https:\/\/t.co\/k9Vyd55Eb5<\/a><\/p>\n

1\/x<\/p>\n

\u2013 Arjun | ERC-7281 arc (@arjunbhuptani) July 7, 2023<\/a><\/p><\/blockquote>\n

According to the proposal’s discussion page, it allows token issuers to designate a list of canonical bridges. Only bridges added to this list could mint an official version of the issuer’s token. Issuers can also limit the number of tokens a bridge is allowed to mint. These parameters can be changed at virtually any time by the issuer.<\/p>\n

In Bhuptani’s view, this proposal will ensure that \u201cownership of tokens is shifted away from bridges (canonical or 3rd party) into the hands of token issuers themselves\u201d and will limit losses if a bridge’s security comes into question:<\/p>\n

\u201cIn the event of a hack or vulnerability for a given bridge (eg today’s Multichain hack), issuer risk is capped to the rate limit of that bridge and issuers can seamlessly delist a bridge without needing to go through a painful and time-intensive migration process with users.<\/p><\/blockquote>\n

Related: <\/strong>$30B stolen from crypto ecosystem since 2012: Report<\/strong><\/a><\/em><\/p>\n

Bhuptani said the proposal would also help prevent user experience problems in decentralized finance, as all bridges would issue the same official token. Over time, this will eliminate the need for multiple versions of the same token, he claimed.<\/p>\n

Stablecoin issuer Circle has already created the Cross-Chain Transfer Protocol (CCTP) to list official bridges<\/a> for its token, the US Dollar Coin (usdc<\/a>, EIP-7281 intends to implement the basic concept behind CCTP but also tries to make<\/a> This solution applies “more broadly to all tokens,” according to the proposal’s notes.<\/p>\n

Both Circle and Tether have blacklisted some of the addresses<\/a> used in the Multichain incident, preventing $65 million worth of USDC and Tether (usdt<\/a>) from being moved out of these addresses.<\/p>\n