Definitely could be articulated better on the site. A lot of technical details that are beyond most of us.
However what I grasped from it is that it wishes to overcome some limitations, speeding up query & download times on Nostr, which we see can be an issue with some clients.
Not only that it offers a credible alternative to IPFS and avoids the unnecessary full & duplicate download of files for numerous clients and relays.
——
“This will unlock a new tier of speed for a variety of decentralized apps that require file directories.”
“Without cryptographically verifiable chunking, users would need to download the entire file to verify it — rather than verifying each chunk immediately after the download. Downloading a very large file before verifying it wastes a lot of time and bandwidth if the file turns out to be incorrect.”
Count me as a huge SN fan who is using nostr every day. I do think some type of integration would make sense. I am also an old but rarely contributing Minds member,, and I know Bill Ottman set up a nostr relay for that network. I don't know the technicalities, but that could be one path.
For one, all it takes is a node operator's channel partners to report balance and then in effect, their balances are out there in the open too.
For two, it's quite obvious a large payment flowing through the network. If there's just a few nodes in a route where the data is not being publicized, there's still enough assumptions about the route that could take place. Plenty of academic research into correlating payments across the network.
It eventually gets into the aspect of anonymity sets and length of hops, which is getting worse and worse as the network becomes bigger (there's papers on that too). In the end, chain analytics and triple letter agencies sees who is paying who. What Amboss is doing right now is how we get to that point.
Definitely could be articulated better on the site. A lot of technical details that are beyond most of us.
However what I grasped from it is that it wishes to overcome some limitations, speeding up query & download times on Nostr, which we see can be an issue with some clients.
Not only that it offers a credible alternative to IPFS and avoids the unnecessary full & duplicate download of files for numerous clients and relays.
——
“This will unlock a new tier of speed for a variety of decentralized apps that require file directories.”
“Without cryptographically verifiable chunking, users would need to download the entire file to verify it — rather than verifying each chunk immediately after the download. Downloading a very large file before verifying it wastes a lot of time and bandwidth if the file turns out to be incorrect.”
Count me as a huge SN fan who is using nostr every day. I do think some type of integration would make sense. I am also an old but rarely contributing Minds member,, and I know Bill Ottman set up a nostr relay for that network. I don't know the technicalities, but that could be one path.
For one, all it takes is a node operator's channel partners to report balance and then in effect, their balances are out there in the open too.
For two, it's quite obvious a large payment flowing through the network. If there's just a few nodes in a route where the data is not being publicized, there's still enough assumptions about the route that could take place. Plenty of academic research into correlating payments across the network.
It eventually gets into the aspect of anonymity sets and length of hops, which is getting worse and worse as the network becomes bigger (there's papers on that too). In the end, chain analytics and triple letter agencies sees who is paying who. What Amboss is doing right now is how we get to that point.