cerc-io/laconic-nitro-docs
10
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

describe validator side flow

Browse Source
This commit is contained in:
Roy Crihfield 2025-08-04 22:58:17 +08:00
parent 97c9b8a303
commit ebbf24f15f
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
nitro-bridge-summary.md
View File

@ -28,6 +28,22 @@ A decentralized bridge network connecting the Cosmos ecosystem and Ethereum. It
4. **Withdrawal (The User's Escape Hatch):** To withdraw, the user submits their **latest held proof** directly to the Shared Nitro Vault on Ethereum. The contract verifies the Schnorr signature and releases the USDC. This action is completely independent of the current state of any Cosmos chain.
### How It Works (Validator Side)
From the validator perspective, the bridge operates as a sophisticated distributed cryptographic system where each validator participates as a member of a threshold signature scheme:
1. **Distributed Key Setup:** Validators collectively participate in a Distributed Key Generation (DKG) protocol to establish a shared public key for their chain. This creates a threshold signature scheme where no single validator can forge signatures, but any threshold number of validators (e.g., 2/3) can collectively produce valid signatures for L1 proofs.
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.
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.
5. **State Verification and Synchronization:** Before processing new ledger-involved transactions, validators verify that their view of L1 state is current and consistent. This includes checking that no unexpected withdrawals have occurred and that the total supply of `Bridged-USDC` on their chain matches their expected liability based on L1 events and IBC transfers.
The critical security property is that validators cannot create fraudulent proofs (due to the threshold signature scheme), cannot prevent legitimate user withdrawals (due to the L1 escape hatch), and cannot ignore L1 finalization events (due to continuous monitoring and state verification requirements).
### Inherent Trade-offs
* **Primary Benefit:** Achieves user sovereignty and unified liquidity without a third-party bridge.