Deploying ERC20 with interop functionality / considerations around if we created a ZK L2 later on

[jameswgc]

Team or Project

Wild Goat Coin

ZK chain

Era, Abstract, Cronos zkEVM

Environment

Mainnet

L2 block number

No response

Provide a brief description of the functionality you're trying to implement and the issue you are running into.

Hello guys,

I've asked a few questions in the discord and been asked to post in here...
We have a fairly early stage, experimental project - WGC Wild Goat Coin. We've just migrated/upgraded to a LayerZero OFT setup, deployed on 28 chains, trying to reposition from memecoin to 'alternative currency protocol' with a focus on being chain agnostic and fully interoperable.

We're looking to deploy our LayerZero OFT token on ZK chains. I'm trying to understand, do we need to consider anything specifically so that the tokens will be compatible with Elastic Chain interop once live.

For example, we've deployed on OP Superchain networks, contract includes ERC-7802 and we've needed to deploy the contract on all chains where we want native interop to be functional.

I have a few questions, would appreciate any advice please...

• Do we need to include something in the token contract for it to be compatible with interop? i.e. like ERC-7802
• Do we need to deploy individually on all chains where we'd like the token to be interoperable (via native interop), similar to how it works on OP Superchain?
• Do we need the same CA across all chains for native interop?
• If we deploy on say ZK Sync Era and Abstract now, could we add more chains later and still have those tokens compatible for interop across entire elastic chain?

We're far away from this right now but have discussed that we might someday look to create our own L2, and if we did, we'd probably look to do it on ZK Sync...

• In the event of that, if we want to use WGC as native token, and we want it to be interoperable across elastic chains... are there special considerations we'd need to make now, to ensure we don't have a problem later?
  (... in other words, if we deploy on ZK now, will it be possible to link the contracts on other ZK chains to our native token later? or is that going to be problematic)

Thanks

Repo Link (Optional)

No response

Additional Details

No response

[dimazhornyk]

Hello! Our interop is designed differently from what OP Superchain has, the main difference being how we identify tokens across different chains. In OP it is required for them to be at the same address. In our framework, we define them by assetIDs, and there are three main components involved in bridging: AssetRouter, AssetHandler, and Token.

The Token in this setup is something like this - it serves as the wrapper for the underlying asset that is deployed automatically on all the chains when the interop transaction happens. So on the chain where the token is native (e.g. Era), you would use the one you deployed (it can be just a normal ERC-20), and when it is bridged to other chains, it will be done automatically.

On your questions:

Do we need to include something in the token contract for it to be compatible with interop? i.e. like ERC-7802

No, it can be vanilla ERC-20

Do we need to deploy individually on all chains

No, you only need to deploy to one chain, where this token will be "native". When full interop goes live - it will be deployed automatically during the first bridging operation.

Do we need the same CA across all chains for native interop?

No

If we deploy on say ZK Sync Era and Abstract now, could we add more chains later and still have those tokens compatible for interop across entire elastic chain?

Yes, any token will be interop-compatible as long as it is ERC-20 compatible. The right way to get it deployed on both chains now is to deploy it to an L1, and later bridge it to Era and Abstract via canonical bridges. Or if it is already deployed on one of them, you can withdraw it to L1 and deploy to another L2 (this is going to do the same thing as interop does)

On the question of a separate chain, it is the same as using it across Abstract and Era - it will have a unique AssetID that will identify it across all chains.