How Bridging Tokens Works
With the deployment of Union’s protocol on Arbitrum, we plan the maintain UNION based token emissions for stakers on both Ethereum & Arbitrum. As UNION is a non-transferrable token and will be required for governance on Layer-1, we’re required to build some additional features which can allow that process to happen in a clear and simple way.
The Stages of UNION between Ethereum & Arbitrum
- 1.UNION originates on Ethereum
- 2.UNION is migrated to Arbitrum via Governance / Multi-sig (?)
- 3.Users staking DAI on Arbitrum can claimed their accumulated arbUNION
- 4.Holders of arbUNION have the ability to migrate arbUNION to Ethereum via Arbitrum’s native crosschain bridge (We should be promoting the migration of arbUNION to L1)
- 5.Migrated arbUNION remains in this state until the point where a user unwraps their arbUNION converting it into the final form of UNION
How a user can manage their UNION tokens through L2 → L1
- While a users wallet is connected to the Union app on Arbitrum with arbUNION in their wallet, they should have an option to bridge their arbUNION to Layer 1 for Governance purposes with Arbitrum’s native bridge either via a link out or directly within the Union UI (Note potentially high bridging fees)
- If a user has migrated arbUNION to Ethereum using the bridge, they should be notified of the ability to unwrap their arbUNION and convert it into regular UNION. This UNION can then be used for voting in Union Improvement Proposals.
function wrap(uint256 _amount) public returns (bool)
function unwrap(uint256 _amount) external returns (bool)
The bridge UI