What is your opinion about subchains?Has there been any discussion about using interleaved blocks?
Of course, some details about fungibility between the different interleaves and closing some attack vectors, but if the 1MB limit is really so important (it isnt technically), you can make a hardfork where N different interleaves are mined. So there would be N different parallel chains, each offset by 10 minutes/N. This way, each interleave gets the full 10 minutes for mining and propagation, removing all "objections" to larger blocks/faster blocks, etc.
I think each would need to be mined independently and just have a convention so (txid mod N) determines which interleave a tx gets mined on.
Using interleaves, the number N can be changed as tx levels require it. But really, I dont see what the big technical issue is with 1MB. Just change to 2MB and 5 minute blocks to get an immediate 4x capacity increase. then a 10x interleave for a total 40x increase. That would buy enough time for truly solving the scalability. Another 2x could be gained by using the canonical numbering that iguana uses, so now it approaches 100x capacity increase. And with the bundle approach, the time to do everything will gradually get faster and faster over the years as CPU's get more cores faster than blockchain size increases.
A Visual Explanation of Subchains
Subchains are a practical application of "weak blocks," which add security to zero-confirmation transactions and permit massive scaling of Bitcoin.
Fig. 1. Each time a block that satisfies the weak target is found, the subchain is extended. When a block satisfying the strong target is found, the subchain is closed, becoming a strong block, and a new subchain begins.
Fig. 2. Miners cooperate to build subchains in order to process more transactions and claim more fees without incurring additional orphaning risk. This illustration visualizes "idealized" ¼-difficulty subchains (also referred to as 4x subchains). In practice, each strong block may contain more or less than four weak blocks, due to randomness.
Fig. 3. Miners build subchains layer by layer (a – c), where each layer corresponds to the solution of a weak block. To propagate blocks (weak or strong), miners need only send their Δ-block and a reference to the subchain’s tip (f), reducing the quantity of transmitted bytes. When a nonce that satisfies the strong target is found, the subchain is closed thereby becoming a strong block (d), and miners begin working on a new subchain (e).
For further reading, please refer to "Reduce Orphaning Risk and Improve Zero-Confirmation Security With Subchains."