Interleaving is a very old way of getting more throughput, without requiring any changes to the underlying basis.
So, using 1MB blocks every 10 minutes, interleaving can get 10x increase in capacity by having 10 interleaves in parallel.
Each interleave is a mostly independent blockchain, but we need to enforce a fixed ordering based on the interleave, regardless of when the block is solved for that interleave. This does create the situation where there is a solved block that cant be confirmed due to a prior interleave not there yet.
This provides the possibility of a rapid delivery feature, where the user can generate 10 different variants of the same tx, so each interleave gets that tx. This would confirm in each interleave, but of course only be valid in the first one that gets confirmed. So a provision needs to exist for charging extra for these redundant tx and to invalidate the ones that are in the unconfirmed later interleaves.
Miners would be able to optimize their revenues by intelligently managing their hashpower based on the state of the 10 interleaves. Also, by having different service levels that comes for free, this would create a larger txfee revenue base via the premium fees and of course from just having 10x the transaction capacity.
10x interleaving works just as well with 1MB blocks, 8MB blocks, subchains, etc.
So far nobody has pointed out any attack, please post if you see any potential attack vector.
So, using 1MB blocks every 10 minutes, interleaving can get 10x increase in capacity by having 10 interleaves in parallel.
Each interleave is a mostly independent blockchain, but we need to enforce a fixed ordering based on the interleave, regardless of when the block is solved for that interleave. This does create the situation where there is a solved block that cant be confirmed due to a prior interleave not there yet.
This provides the possibility of a rapid delivery feature, where the user can generate 10 different variants of the same tx, so each interleave gets that tx. This would confirm in each interleave, but of course only be valid in the first one that gets confirmed. So a provision needs to exist for charging extra for these redundant tx and to invalidate the ones that are in the unconfirmed later interleaves.
Miners would be able to optimize their revenues by intelligently managing their hashpower based on the state of the 10 interleaves. Also, by having different service levels that comes for free, this would create a larger txfee revenue base via the premium fees and of course from just having 10x the transaction capacity.
10x interleaving works just as well with 1MB blocks, 8MB blocks, subchains, etc.
So far nobody has pointed out any attack, please post if you see any potential attack vector.