To Bridge or Not to Bridge: What's at Stake?
summary
Frames proof of stake as two decisions: fork choice / finality (ECC’s trailing finality layer is the concrete hybrid proposal) and the staking/rewards design that actually allocates ZEC and shapes validator/delegator politics. Gives concrete examples: Ethereum requires 32 ETH per validator and enables liquid staking like Lido, Cosmos/Tendermint runs ~150 validators with protocol-enforced reward distribution, Penumbra offers native per-validator LSTs, Namada uses cubic slashing and Rust tooling. Compares interoperability paths IBC versus a bespoke bridge and notes a shielded airdrop proposal.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:14Background of proof-of stake
- 6:34Background of interoperability
- 8:00Why consider PoS & interoperability together?
- 9:50What will PoS change from Zcash today?
- 12:32What will interoperability change from Zcash today?
- 14:14Fork choice / finality
- 15:30Staking & rewards
- 17:31Examples from other ecosystems
- 21:25Staking and rewards ex: Ethereum
- 25:01Staking and rewards ex: Cosmos SDK
- 26:51Staking and rewards ex: Penumbra
- 27:48Staking and rewards ex: Namada
- 28:31Takeaways
- 30:33PoS considerations
- 31:43Interoperability options
- 32:00Interoperability: bespoke bridge
- 33:04Interoperability trade-offs
- 34:18What's next and role of Anoma/Namada/Heliax
related talks
12mBreaking Down Bridge Security Models
11mCommon Vulnerabilities in Bridges
19mSecuring a Cross-Chain Bridge
38mUnifying Blockchains: Innovations for Seamless Interoperability
21mBattle of the blockchains
18mNot Quite Water Under the Bridge
14mExploring a New Nexus: Cosmos & Ethereum
13mMulti-chain governance: How can DAOs live across chains