I'm still a bit skeptical about "Optimistic confirmations", by that mechanism, a low reputation chain (Chain A) can compromise a big one (Chain B), e.g. by cross swapping tokens between chain A and B. Then if the Chain A sequencer misbehaves, it enforces to potentially rollback 1 hour of transactions on Chain A, which IMO is insane
Can you please create a video or point us to a document that provides details on trusted state created by sequencers, virtual state and the different kinds of states (virtual batches, verified batches, forced batches)
35:00. Why not use both decentralized and shared sequencers? Decentralized sequencer for work when you do NOT need interoperability, and use shared sequencer for work when you do need interoperability?
Great video as usual, you're now my favourite web3 educator!
Briliant breakdown! 🎯💯🔥🤙🏿😉
Thank you, this was really good.
Pls do a video on Polkadot JAM and maybe comparing it to restaking, decentralized sequencers and agglaxer :O
Cant wait to eat snacks and watch this one!
I see what you did there 😅
Great content!
can we find the node which is centralised sequencer? so that we can propagate tx faster ?
I'm still a bit skeptical about "Optimistic confirmations", by that mechanism, a low reputation chain (Chain A) can compromise a big one (Chain B), e.g. by cross swapping tokens between chain A and B. Then if the Chain A sequencer misbehaves, it enforces to potentially rollback 1 hour of transactions on Chain A, which IMO is insane
Can you please create a video or point us to a document that provides details on trusted state created by sequencers, virtual state and the different kinds of states (virtual batches, verified batches, forced batches)
35:00. Why not use both decentralized and shared sequencers? Decentralized sequencer for work when you do NOT need interoperability, and use shared sequencer for work when you do need interoperability?
Please keep the slides on the left of yourself, so that you do not block/hide parts of your slides.
🙂