• 2 Posts
  • 11 Comments
Joined 3 years ago
cake
Cake day: December 3rd, 2023

help-circle




  • Is the main issue really tracking and consolidating microdonations, or is it transferring credit between these donation systems and traditional finance entities like banks and credit card networks?

    They are 2 main issues. As mentioned, you want to transfer the money to the right person, which means tracking (or collection, whatever term you want to assign to it). And you want to transfer in the first place. Since there are so many systems, and some that don’t allow one-time donations, and people are all over the world, it definitely is a problem. That’s why not doing it monthly but annually could help. But that does make me think that it should be possible for the user to filter donation methods. For example filtering out direct transfers to accounts outside of your region due to transfer costs. Thanks, I can add that.

    Which regulatory compliance things would apply to this in its current form? Or do you mean that connecting to a user’s bank account would incur the wrath of the authorities?



  • You typically want a slightly-more-elaborate approach than just handing the network a hash and then getting a file.

    […]

    Blake 3 supports verified streaming as it is built upon merkle trees as you described. So is IPFS. As I mentioned, IPFS hashes are that of the tree, not the file contents themselves, but that doesn’t help when you have a SHA256 sum of a file and want to download it. Maybe there are networks that map the SHA256 sum to a blake3 sum, an IPFS CID, or even an HTTP URI, but I don’t know of one, hence the question here.

    BitTorrent and Hyphanet have mechanisms that do this.

    Do you know of a way to exploit that? A library maybe?