transfer steps are not "simultaneous"
This commit is contained in:
parent
ebbf24f15f
commit
5fa8fda37c
@ -36,7 +36,7 @@ From the validator perspective, the bridge operates as a sophisticated distribut
|
||||
|
||||
2. **Liability Tracking and Proof Generation:** When a user deposits `Bridged-USDC` or transfers it to their chain, validators collectively track the liability and generate Schnorr-signed proofs of ownership. For example, when Chain A receives a deposit, its validators coordinate to create a signature that proves "Chain A validator set acknowledges liability for X USDC belonging to user Y."
|
||||
|
||||
3. **Cross-Chain Handoffs:** During IBC transfers between chains (e.g., Chain A → Chain B), both validator sets participate in an atomic handoff protocol. Chain A validators sign a proof releasing their liability, while Chain B validators simultaneously sign a new proof accepting the liability. This ensures the user always holds exactly one valid, L1-verifiable proof.
|
||||
3. **Cross-Chain Handoffs:** During IBC transfers between chains (e.g., Chain A → Chain B), both validator sets participate in an atomic handoff protocol. Chain B validators first sign a new proof accepting the liability, then Chain A validators sign a proof releasing their liability once they receive confirmation. This ensures the user always holds exactly one valid, L1-verifiable proof.
|
||||
|
||||
4. **L1 State Monitoring:** All validators continuously monitor the Shared Nitro Vault on Ethereum for finalization events, particularly users who exit via the escape hatch. When a user withdraws directly from L1, validators detect this event and update their local chain state to reflect the reduction in total bridged assets, ensuring the system remains economically consistent.
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user