An alternative to blockchain architecture is block lattice architecture. It’s supposed to be an improvement by allowing for faster transaction times than are currently being achieved with blockchain models.

One feature that enables faster transaction times is that each user’s blockchain tracks their account balance. This feature allows for less storage requirements. Additionally, each blockchain used by someone will also give information related to the individual’s balance history. Thankfully it can only be updated by the owner.

The blocks in a block-lattice system also do not contain thousands of bundled transactions like in a typical blockchain system. Rather, every transaction on a lattice system puts a send block on the sender’s account chain and a corresponding receive block on the receiver’s account chain. 

This separation of transactions into two parts allows the sender to make transactions anytime. 

To make a transaction, the sender creates a send block. This send block will hold the address of the receiving account, the number of coins to be sent and a reference to the last block on the sender’s account chain. 

The sender then adds the block to his/her chain and broadcasts it to the network. The sender must then wait for the network to agree on the transaction’s validity. When the network agrees, the coins are deducted from the sender’s balance and the transaction is settled on the chain. This entire process should take no more than 3 seconds on this block lattice architecture.

The receiver, to receive the funds, creates a corresponding receive block. The sender then attaches it to his/her own account chain. Once the receiver broadcasts the block to the network, the funds are added to his/her balance. This also should take about 3 seconds

In addition to all this, the block lattice system is governed, not by Proof-of-Work like in a traditional blockchain system, but instead by Delegated Proof-of-stake (dPoS).

To make dPoS function, each account owner must choose a representative that will verify new blocks on his/her behalf. 

If one of the network participants tries to double-spend his/her coins the representatives vote on which block to keep and which one to discard, thereby eliminating double spending. Each rep. also has different voting weight which is based on the number of coins that accounts have delegated to them. 

So a block cannot be settled into the block lattice until it’s been verified by representatives with a combined voting weight of more than 50%. This way, only one of the conflicting blocks is kept and double-spending is prevented.

Additionally, thanks to the fact that each account holder has their own chain independent from another, the rest of the accounts can continue to make transactions during the voting process.

The dPoS-architecture allows for feeless and near-instantaneous transactions thanks to all transactions being settled on separate chains that are verified by their representatives. This also helps achieve a much higher transaction throughput, since no machine-heavy block mining needs to be done to secure the network.