So Cherry Trees have the flaws of Merkle DAGs (growing file for list of chunks) with the narrow abilities of Classic Merkle trees (support restricted to single files).
That seems like a big waste of time… regressing us backward. I don’t think we should try to beat Merkle’s scheme.
It has the flaws of Merkle DAGs but it does not use merkle trees, its basically just a recreation of torrent V1 files on top of nostr and blossom servers
I'm not trying to fix anything with this, just building an app to stress test blossom servers. and I was curious if it could be done in a really simple way
Why not just use bittorrent then?
its slightly more simple, and it works in web browsers. although I'm not trying to replace bittorrent, I'm just trying to stress test blossom servers and introduce the concept of pay-per-upload
Chunking and pay-per-upload have nothing to do with each other. You can stress test blossom servers & payments with large unchunked files.
Blossom is great for unchunked files, but chunked files should be a Merkle-based scheme.
Creating a poor chunking standard is just foolish and can raise the risk of delay attacks for large files. Merkle would be disappointed.
