Scaling Bitcoin with SAFE

That’s not true. But to be helpful, you need to be helpful.

The problem is if you don’t know how bitcoin (or SAFE) works, then you can’t be helpful.
I tried 3 times to talk some sense into you and the other guy, @polporene tried too, and you still don’t get it.

And no, there is no misunderstanding when it comes to de-duplication.

The whole point of bitcoin is that full nodes most decisively must not rely on 3rd party to tell them what transpired on the blockchain. And secondly, from release notes for the current version (released months ago):

This release supports running a fully validating node without maintaining a copy of the raw block and undo data on disk. … The user specifies how much space to allot for block & undo files. The minimum allowed is 550MB.

So, in case you didn’t know, there’s something called disk pruning, which allows full bitcoin nodes to optionally automatically delete unneeded blocks (based on their own definition of “unneeded”) and in the most extreme case one needs only 550 MB of disk space to run a full node.

550 MB is nothing by today’s standards (even 50 GB (entire blockchain) isn’t a big deal - a microSD card can host the entire OS, full node software and the entire bitcoin blockchain).

Therefore the “solution” proposed in this topic is undesired, unworkable, and unnecessary.