You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keep in mind we have to deduplicate chain events based on the hash
Convert all assets to be associated to the configured ethereum chain (using chain ID).
Hash with Chain ID, if seen, dedup, if not seen, hash without chain ID, if seen dedup, if not, track event hash with with chain ID.
Add RPC config to enable arbitrum ETHClient.
Support in governance
2. add chain ID to governance payload
3. validation of asset with bridge based on chain ID
5. add asset to asset pool and banking
6. on enactment, emit signature that tells the bridge it shall allow the use of asset (support multiple chain ID)
7. enable asset in collateral engine (support multiple chain ID)
Support deposit & withdraw
Support chain ID in chain event (resolved from asset ID to chain ID)
Validation using the correct ETHClient (ensure use of the arbitrum one)
Finish deposit
Withdrawal: emit signatures that are slightly modified: ethbridge = old signatures, arbitrum = new signatures. to be refined
Validation package (To refined, no ticket associated yet)
Add and remove validators: add_signer / remove_signer
Question: impact on rewards if bridge incorrectly setup ? Option: If one is not correctly setup -> no payment.
Support for the Arbitrum bridge in the core.
Green path
2. add chain ID to governance payload
3. validation of asset with bridge based on chain ID
5. add asset to asset pool and banking
6. on enactment, emit signature that tells the bridge it shall allow the use of asset (support multiple chain ID)
7. enable asset in collateral engine (support multiple chain ID)
add_signer
/remove_signer
Additional links
Tasks
The text was updated successfully, but these errors were encountered: