Hey there, I'm curios as to what you make of this statement by Dan Larimer of EOS.
"Redefining the Semantics of a Transfer:
What if we redefined the requirements for a valid block to require that each account may receive at most one deposit or one withdraw."
Taken from:
https://steemit.com/blockchain/@dantheman/how-to-process-100m-transfers-second-on-a-single-blockchain
This sounds a lot like the blocklattice that is being described in your article.
I always wondered how he was going to do an asynchronous, highly scalable blockchain. This seems like the likely approach.
Best,
Hi, sorry for the late reply, I've been extremely busy with work for the last couple of weeks. Yes, the structure he describes is exactly how the block lattice operates. Each transaction consists of two pieces, one withdraw transaction and one deposit transactions, and each of these occurs on their respective blockchains so as such there is only one transaction type (deposit or withdraw) per account.
This ties is very closely with tried and tested methods of duel entry accounting (always have a debit and credit in a transaction and neither of these can be in the same ledger). This is one of the most likely ways of achieving a true asynchronous, highly scalable blockchain.
There is a tremendous use potential for this in various fields, I'm currently exploring and working on some that are completely non-crypto related.