Interesting, we&#x27;re doing something similar with Open Publish, Bitstore, and a couple of DHT backed delivery systems, namely IPFS and BitTorrent.<p>Content is published by registering a SHA-1, BitTorrent InfoHash, an IPFS key and a URI pointing to the content on the Bitcoin blockchain.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;blockai&#x2F;openpublish#register-media-with-an-open-publish-transaction-posted-to-the-bitcoin-network" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;blockai&#x2F;openpublish#register-media-with-a...</a><p>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.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;blockai&#x2F;openpublish#tipping-and-micropayments" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;blockai&#x2F;openpublish#tipping-and-micropaym...</a><p>We&#x27;ve experimented with some Reddit-style ranking algorithms where we consider payments or tips as upvotes.<p>One big difference between what we&#x27;re building and what this presentation is describing is where and how the content itself is stored.<p>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.<p>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.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;blockai&#x2F;bitstore-client" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;blockai&#x2F;bitstore-client</a><p>So instead of having to run your own IPFS or BitTorrent node that&#x27;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.<p>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.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;blockai&#x2F;abstract-common-wallet" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;blockai&#x2F;abstract-common-wallet</a><p>This opens up a number of really interesting interactions, such as something like &quot;tip to comment&quot;, 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.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;blockai&#x2F;my-two-bits" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;blockai&#x2F;my-two-bits</a> <a href="https:&#x2F;&#x2F;github.com&#x2F;blockai&#x2F;my-two-bits-client" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;blockai&#x2F;my-two-bits-client</a>