> We're still on something like HTTP 1.0 and HTML 2.0 when it comes to crypto. I agree, and even though avalanche (one of a16z investments in ava-labs works on

> We're still on something like HTTP 1.0 and HTML 2.0 when it comes to crypto. I agree, and even though avalanche (one of a16z investments in ava-labs works on this) seems to have solved the consensus problem, I have yet to see an l1 tackle the state growth issues similarly. I think it will require some novel ways of information compression, mapping and/or storage/revival, and I suspect at least one l1 way will be related to the the DAG approach with avalanche however with the relationship between prior blocks (if you consider a block a matrix related to it block size limit at max) a series of transformations such that block x_n = sum of block transformations from 0 to n (this will be heavily reliant upon group theory) so instead of storing blocks themselves, you store the transformation matrices mapped to the hashes (sacrificing some compute for less storage). [0] https://thecontrol.co/state-growth-a-look-at-the-problem-and-its-solutions-6de9d7634b0b https://thecontrol.co/state-growth-a-look-at-the-problem-and...