What about https://github.com/hzrd149/cherry-tree ?
We need some standard for chunking of videos and other large files.
That enables
1) verifying what you're getting before you've downloaded the entire large file,
2) downloading simultaneously from multiple servers or peers and
3) saved and scrollable livestreams — just publish the updated merkle root to your stream file every few seconds.
While we're at it, why not use blossom-compatible (sha-256) Bittorrent v2 merkle-trees https://blog.libtorrent.org/2020/09/bittorrent-v2/ — or maybe nostr:npub1h0rnetjp2qka44ayzyjcdh90gs3gzrtq4f94033heng6w34s0pzq2yfv0g soon?
Discussion
There's not much info on it. Maybe it's using https://github.com/hzrd149/blossom/blob/chunked-blobs/buds/10.md ? BUD-10 looks workable, but there's no merkle tree definition yet.
nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpzfmhxue69uhkummnw3e82efwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9emkjmn99urf278z nostr:nprofile1qqsxlvnxqykrqzps8e22u4g5pdrf2l5e0qycgqwa5d85mys6yadl3wcpzpmhxue69uhkummnw3ezuamfdejsz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpp4mhxue69uhkummn9ekx7mq65w8x5
Could you explain what you mean? we have a prototype that was made a while ago an you can even pay for the chunks using cashu
Is there any info on the chunking standard?
right now now the bud only specifies to use either 1MB or 4MB chunks.
We split the file in equal parts and make a merkle tree out of that. we tried to keep it real simple
there is nothing that would avoid you using bigger chunks thought. We should probably specify the chunk size in the tags.
