Maintaining Data Integrity When Blockchains Fork
summary
Conseil stores chain data in Postgres and Lorre crawls nodes (currently Tezos) to populate it; the algorithm never deletes blocks but marks them in an invalidated blocks table and maintains the invariant that at most one block per level has is_invalidated flag = false. Lorre does a linear backward crawl, detects missing or conflicting predecessors, flips invalidation flags to follow the chosen branch, and preserves internal consistency during multi-branch forks without relying on chain consensus details.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:15What is Scriptnomic
- 2:25Blockchain Ecosystem
- 3:40CryptAnomic
- 4:20Architecture
- 5:55Lore
- 8:20Blockchains
- 11:40Nightmare Scenario
- 13:10Invalidation Table
- 15:40Twopronged approach
- 24:00Consensus mechanism
- 30:10The algorithm makes sense
- 33:20Chains are beautiful
- 33:45Privacy
- 36:30Questions
- 41:00Go for it
related talks
24mCrypto Secure Data Management with In-Database Blockchain
20mShared Security in the BLOCKCHAIN
25mModular Structure of Blockchains
23mBlockchain node DB designs: from Geth to Erigon
21mCOLE: A Column-based Learned Storage for Blockchain Systems
22mActually Functional Blockchain Design
25mManaging changes to your data with dat
55mHow Not to Destroy Data