This SIP proposes the addition of a cross-chain transfer function to the snxUSD token.
\nLeveraging cross-chain messaging, Synthetix is able to implement highly efficient digital asset transfer via teleportation. In its simplest form, this entails burning snxUSD on a source chain, sending a cross-chain message containing the amount burned, and minting that quantity of tokens on the destination chain. A teleportation fee can be collected and distributed to backers of snxUSD. Teleporters will initially be deployed on the networks where Synthetix already exists (i.e. Ethereum & Optimism).
\nAs liquidity in DeFi continues to move across various L2s, it is increasingly important for protocols to create chain-agnostic abstractions. Given that Synthetix is currently deployed on two chains, the ability to transfer assets bi-directionally (without a challenge verification period imposed by roll-ups, e.g.) would already be a very valuable feature for the protocol.
\nTeleporters were originally proposed in SIP-204, but implementation was postponed due to the lack of decentralized cross-chain messaging solutions available. This proposal entails the use of the Cross-Chain Interoperability Protocol (CCIP). Because Synthetix is already dependent on Chainlink's infrastructure for price feed oracles, this proposal doesn't create any trust assumptions with additional third parties.
\nTeleporters are an improvement over AMM-based cross-chain bridging solutions because there is no slippage incurred from liquidity available on destination chains. Instead, the protocol can apply a fee structure at the discretion of governance, further incentivizing stakers to back the stablecoin.
\nTeleporters involve adding transferCrossChain and ccipReceive functions to the snxUSD token with appropriate validations and fee capture functionality.
We propose making the transfer function available on the snxUSD proxy, rather than the core system proxy. This is an extension of the ERC-20 interface (which already essentially includes a \"same-chain\" transfer function).
In addition to the new functions outlined in the technical specification below, this SIP also proposes that Chainlink's CCIP token pools be granted permission to mint and burn snxUSD in order to facilitate the cross-chain token transfers. This method allows for multiple benefits as described below:
\nComposability & Commercial Opportunity
\nToken transfers using the CCIP token pools provide Synthetix the opportunity in the future, if desired, to open up Chainlink's private snxUSD Token Pool which would allow third parties to transfer snxUSD (even in combination with other tokens and/or data). In this scenario, there is also potential to set up a rev-share model between CCIP and Synthetix (as snxUSD token issuer) for third-party CCIP snxUSD token transfers, creating a shared incentive for increased snxUSD token transfer volume over CCIP.
\nEnhanced security via the Active Risk Management (ARM) Network
\nWith token transfers, the ARM Network has access to additional transaction information (i.e. token, amount) that enable it to perform additional risk management policies which cannot be implemented for arbitrary messaging. The ARM rule set will evolve over time into more advanced logic to identify and mitigate additional risks.
\nEnhanced security via Rate Limits
\nIn contrast to arbitrary messaging, CCIP token transfers provide configurable rate limits per token pool per lane, which are set up in alignment with the token issuer. This feature is part of the heavily audited CCIP code base and only available for token transfers. CCIP token transfers also benefit from increased security via the global rate limits (across token pools), so not every token’s rate limit could be exploited at maximum in a worst case scenario.
\nThis proposal entails collecting fees in ETH, rather than snxUSD, for the following reasons:
\nCcipRouter handles the fee calculation for the execution of the specified message.msg.value that the user passes to transferCrossChain() and what the CcipRouter returns as getFee().Future SIPs could involve additional fee payment methods (such as snxUSD), alternative fee structures, and circuit-breaking functionality for added security.
\nImplementation entails adding two new functions to the snxUSD token module:
\ntransferCrossChain(uint64 destChainId, address to, uint256 amount) external payable returns (uint256 gasTokenUsed)
Approve the amount of snxUSD to be transferred to the CCIP Router.
\nccipSend.msg.value and CcipRouter.getFee()).ccipReceive(Any2EVMMessage calldata message)
srcChainId and sender data in the message correspond to a legitimate deployment of the snxUSD token.data.Note that this function must conform to the existing CCIP interface.
\nRelevant tests will be developed during implementation, including but not limited to:
\nTwo new unit tests are added to test the new contracts. These tests will mock the required external interfaces (i.e. CcipRouter and CcipTokenPool).
For USDTokenModule:
For CcipReceiverModule:
CcipRouter.One integration test to cover the initiation of a cross-chain transfer.
\nCcipRouter has enough allowance to transfer tokens.CcipRouter burns the correct amount of snxUSD on the source chain.msg.value and getFee()) to the caller.CcipRouter.ccipSend() with the expected encoded data.TransferCrossChainInitiated event with the expected values.CcipRouter (on destination) emits a MessageExecuted event.CcipRouters and CcipTokenPools for each chain, such that it can verify the sender of messages that request minting snxUSD.Copyright and related rights waived via CC0.
"}},"pageContext":{"id":"1109852f-fb4c-5b2d-86e7-787dd2e6e37b","frontmatter__sip":311,"__params":{"frontmatter__sip":"311"}}},"staticQueryHashes":[]}