Clear DefinitionsBlock-Lattice
2 min read
Pronunciation
[blok-lat-is]
Analogy
Think of Block-Lattice as a city where each resident maintains their own personal checkbook (account-chain) rather than everyone recording their transactions in a single community ledger (traditional blockchain). When Alice pays Bob, she records a withdrawal in her checkbook while Bob simultaneously records a deposit in his. These independent records proceed at their own pace, requiring no city-wide agreement process. Only when disputes arise, such as Alice attempting to spend the same money twice, does a conflict-resolution mechanism engage. This architecture allows thousands of transactions to occur simultaneously without everyone needing to synchronize after each payment.
Definition
A distributed ledger architecture where each account maintains its own blockchain (account-chain), enabling asynchronous updates and eliminating the need for global consensus on all transactions. Block-Lattice achieves high throughput and minimal latency by requiring consensus only when resolving conflicts between interacting account-chains, rather than for every transaction in the network.
Key Points Intro
Block-Lattice architecture introduces four key innovations that differentiate it from traditional blockchain designs.
Key Points
Account-Centric Design: Each account controls its own blockchain, recording only transactions relevant to that account.
Asynchronous Processing: Transactions can be processed independently without global coordination, enabling near-instant finality under normal conditions.
Dual-Transaction Mechanism: Most transactions require two entries—a send block on the sender's chain and a receive block on the recipient's chain.
Local Consensus: Requires network-wide consensus only for resolving conflicting transactions, not for routine operations.
Example
A payment platform built on Block-Lattice architecture enables near-instant microtransactions. When a user pays for a coffee, their wallet creates a 'send' block on their account-chain, which is broadcast to the network and confirmed almost immediately without waiting for miners or validators to process it. The coffee shop's account can then create a 'receive' block on their own account-chain at their convenience, completing the transaction. This process takes a fraction of a second and incurs no fees because no global consensus is required. Even if hundreds of other transactions are occurring simultaneously, they proceed independently on their respective account-chains without creating congestion or delays.
Technical Deep Dive
Block-Lattice implements a directed acyclic graph (DAG) structure where each account controls its own blockchain that only this account can modify, using key-based ownership. Each account-chain tracks account balance history rather than individual transaction amounts (account model vs. UTXO model). Transactions typically require two separate blocks: a send block (deducting from sender's balance) and a corresponding receive block (adding to recipient's balance). This design allows recipients to pocket received funds at their convenience, asynchronously from the send operation. For conflict resolution (e.g., double-spending attempts), the network employs various consensus mechanisms ranging from delegated Proof-of-Stake (dPoS) to Open Representative Voting (ORV) depending on the specific implementation. Each block contains a reference to the previous block in that account-chain (creating a hash-based chain) and typically employs a small proof-of-work as an anti-spam measure rather than for consensus. Advanced implementations add features like state blocks (combining open/receive/send/change blocks into a single format), account sharding for scalability, and voting systems allowing representatives to vote on conflicting transactions.
Security Warning
While Block-Lattice architecture provides high performance, it introduces unique security considerations. In some implementations, funds remain in a 'pending' state until recipients actively create receive blocks. Monitor account activity regularly to ensure incoming transactions are properly pocketed, as some attacks target this two-stage process.
Caveat
Despite its performance advantages, Block-Lattice architecture faces several challenges. The account-centric model may create practical limitations for smart contract implementation compared to global state systems. The lightweight consensus models typically used with Block-Lattice may provide weaker security guarantees against sophisticated attacks compared to traditional blockchain consensus mechanisms. Additionally, the asynchronous nature of transactions can introduce UX complexity, as users need to understand that receiving funds requires active participation rather than being automatic.
Block-Lattice - Related Articles
No related articles for this term.