Hey @bumerang , thanks for your question, first we need to clarify that 50m - Moonbeam, 30m - Moonriver, 10m - Bifrost, 10m - New parachain is only the initial distribution of ZLK (Zenlink network tokens), which does not mean that the ZLK on each parachain is always fixed.
We are working on getting ZLK to circulate on all parachains. For now, Moonriver<>Moonbeam and Bifrost<>Moonriver cross-chain transfers for ZLK are available, and they are implemented via Multichain and SubBridge respectively. So when Zenlink is integrated into Astar, we can certainly make ZLK on other parachains available to the Astar network through some similar solution.
Some other solutions foreseen.
Push CEXs such as gate.io to open up ZLK deposits and withdrawals on the Astar network. ZLK is currently listed primarily on gate.io, which we have pushed to support ZLK withdrawals and deposits on multiple networks including Bifrost, Moonriver, and Moonbeam.
Hey @Ayu , thanks to the Astar team for the support, we are equally excited about the integration and let’s build! Looking forward to hearing more thoughts and suggestions from the Astar team
@Lu1 welcome to Astar. I’m a long time fan of your project.
Please explain will you support both Native(Polkadot.js) and EVM wallets for Astar? I see you use SS58 signer for Bifrost and H160 for MB
It depends on where we run the dex logic.
Bifrost integrated with Zenlink DEX Module(Pallet) into their chain codebase, so that we would let people use SS58 signer to interact with the pallet.
For Astar, we deploy Zenlink DEX EVM contracts to its evm pallet, as same as MB/MR. So we only need to let people use EVM wallet in Zenlink.