Ethereum
Vault
LOCK
- User requesting bridging executes - EthVault.depositor- EthVault.depositTokenFunction with Bridging Fee.
- Depositevent occurs in Eth Vault and Token Lock completed
- Bridge Operator catches the event and relays bridging data to Orbit Hub 
- Bridge Validator consensus on relayed bridging data 
- After the agreement is completed, - toChainMinter's MINT Process
RELEASE
- Completes the BURN process of - fromChainMinter
- Bridge Operator Catch Bridging Data agreed by Bridge Validators 
- After the Bridge Operator collects the signature for the agreed Bridging Data, - EthVault.withdrawis executed
- Withdrawevent occurs in Eth Vault and Token Release (Transfer) is completed
Minter
MINT
- Completes the LOCK process of - fromChainVault
- Bridge Operator Catch Bridging Data agreed by Bridge Validators 
- After the Bridge Operator collects the signature for the agreed Bridging Data, - EthMinter.swapis executed
- Swapevent occurs in Eth Minter and Token Minted
Token Initial Name & Symbol minted by Minter
- Name : Orbit Bridge Ethereum Token 
- Symbol : OBT 
To change the Token Name and Symbol, anyone can make the first change as Public, and from the second change, it can be changed with the authority of the Token Contract Owner (= Minter Contract Owner).
BURN
- User requesting bridging executes - EthMinter.requestSwapFunction with Bridging Fee.
- Swapevent occurs in Eth Minter and Token Burn is completed
- Bridge Operator catches the event and relays bridging data to Orbit Hub 
- Bridge Validator consensus on relayed bridging data 
- After the agreement is completed, - toChainVault's Release Process
Last updated
Was this helpful?
