42 ms·
Interesting, we're doing something similar with Open Publish, Bitstore, and a couple of DHT backed delivery systems, namely IPFS and BitTorrent. Content is pub
by williamcotton 11y ago
Interesting, we're doing something similar with Open Publish, Bitstore, and a couple of DHT backed delivery systems, namely IPFS and BitTorrent.
Content is published by registering a SHA-1, BitTorrent InfoHash, an IPFS key and a URI pointing to the content on the Bitcoin blockchain.
https://github.com/blockai/openpublish#register-media-with-an-open-publish-transaction-posted-to-the-bitcoin-network https://github.com/blockai/openpublish#register-media-with-a...
Payments or tips towards that content are registered by creating a Bitcoin transaction that pays the person who registered the content by referencing the SHA-1.
https://github.com/blockai/openpublish#tipping-and-micropayments https://github.com/blockai/openpublish#tipping-and-micropaym...
We've experimented with some Reddit-style ranking algorithms where we consider payments or tips as upvotes.
One big difference between what we're building and what this presentation is describing is where and how the content itself is stored.
We expect the content to be available on BitTorrent (and WebTorrent) as well as IPFS, both content-addressable data stores that use DHTs, but we also have a fallback to a URL for the content.
We made our own service called Bitstore, a content-addressable file hosting and distribution service that uses Bitcoin public key infrastructure for authentication and payment.
https://github.com/blockai/bitstore-client https://github.com/blockai/bitstore-client
So instead of having to run your own IPFS or BitTorrent node that's always serving up your content, you can pay a small fee in Bitcoin to have your file hosted... something like a coin operated S3.
Both Bitstore and Open Publish use the same form of authentication and permission, the public key nature of Bitcoin wallets. Users are identified by their public wallet addresses. This login mechanism has been implemented in a number of wallets that support the spec Common Wallet interface.
https://github.com/blockai/abstract-common-wallet https://github.com/blockai/abstract-common-wallet
This opens up a number of really interesting interactions, such as something like "tip to comment", where a web service can check the Bitcoin blockchain to see if a self-identified wallet address did indeed tip the content it is attempting to comment on.
https://github.com/blockai/my-two-bits https://github.com/blockai/my-two-bits https://github.com/blockai/my-two-bits-client https://github.com/blockai/my-two-bits-client
- joosters 11y agoWhat are the problems with existing services that you are attempting to solve?
- williamcotton 11y agoIn short, the entire nature of how information is published and monetized. There are numerous problems with the current ad-sponsored publishing systems with web content, but some of the more interesting ideas we're looking at deal more with the professional publishing industries around photography, music and books. We were very excited to read this report from the Berklee School of Music that outlined a system very similar to what we've been building! In addition to the aforementioned benefits, a compre- hensive, accurate database of music rights ownership information would provide a platform for new technol- ogies to be applied in potentially game-changing ways. We encourage the investigation of the use of emerging crypto-currencies, such as Bitcoin, and their underlying technology, Blockchain, as new royalty-distribution mechanisms for the music industry. ... A database of accurate rights ownership information, like the one we have proposed, could form the founda- tion of a similar cryptocurrency log. In addition to rights ownership information, the royalty split for each work, as determined by a mixture of statute and contracts, could be added to the database. Each time a payment is generated for a given work, the money would be auto- matically split according to the set terms, and each par- ty’s account would instantly reflect the additional reve- nue. For example, suppose a song is purchased from a digital music store, such as iTunes. After the store takes its cut, for ease of demonstration, we will hypothetically assume the revenue generated by the purchase comes to US$1.00. This money would be split between the two different works contained in the song, with a 9.1 cent mechanical royalty going to the musical work, and the remaining 90.9 cents going to the sound recording. Next, if the contract between the publisher and songwriter specifies a 75/25 split of revenue from downloads, the publisher would receive 6.825 cents and the songwriter would receive 2.275 cents. With an identical split at the record label, The label would receive 68.175 cents, and the recording artist would get 22.725 cents. The block- chain network could also further divide this 22.725 cents between the members of a band, if applicable. This entire process would take place in less than one second, allowing all parties to access their money immediately after it is generated. Further, this payment system is fully trackable and would ensure that royalties are not held by third parties, such as labels and publish- ers, before being passed to the artist and songwriter. This would eliminate concerns about accidental or intentional underpayment of royalties. - Fair Music: Transparency and Money Flows in the Music Industry, p.27-28 https://www.berklee.edu/news/fair_music_report https://www.berklee.edu/news/fair_music_report