We need to wait those bridges to be finalized (soon will be available). But however, is not mandatory to wait for those bridges.
If you have a time constraint and you need to immediately make the token available on those chains as well, do it like this:
- Lock a portion of your ESDT supply
- Mint the same portion (exact number of tokens) on the other chain(s)
- share this publicly with your community (locked wallet, correct contract on the other chains, etc)
- set up a trusted (centralized) bridge where you process transfer requests from one part to the other (i.e. I give you 100 tokens and an address on Ethereum, you send 100 ERC20 tokens to that address on Ethereum)
We need to wait those bridges to be finalized (soon will be available). But however, is not mandatory to wait for those bridges. If you have a time constraint and you need to immediately make the token available on those chains as well, do it like this: - Lock a portion of your ESDT supply - Mint the same portion (exact number of tokens) on the other chain(s) - share this publicly with your community (locked wallet, correct contract on the other chains, etc) - set up a trusted (centralized) bridge where you process transfer requests from one part to the other (i.e. I give you 100 tokens and an address on Ethereum, you send 100 ERC20 tokens to that address on Ethereum)
There is no such thing as an extra sc for the token. They are natively implemented on the chain and stored directly in the account trie :)