Hardly inconspicuous.
But I like the idea.
31–40 of 50 posts
Hardly inconspicuous.
But I like the idea.
So something I've been wondering about with all the talk around The Pirate Bay recently is why aren't people using the blockchain to store data needed to bootstrap your joining of a decentralised network. It could be as simple as storing the magnet links themselves.
is this a published paper? O_o
[1] http://news.ucsc.edu/2013/06/entrepreneurship-showcase.html
So something I've been wondering about with all the talk around The Pirate Bay recently is why aren't people using the blockchain to store data needed to bootstrap your joining of a decentralised network. It could be as simple as storing the magnet links themselves.
On the Bitcoin blockchain, you can't fit a magnet link in the very small amount of data you're allowed to include in a transaction. You could split them across multiple transactions, but that leads into the second problem: It's not entirely clear how you'd make a directory so people could actually find these torrents. As more general-purpose blockchains come out (Ethereum, for one example), this will get easier.
Since you can easily fit the Magnet hash in an OP_RETURN value, all required is to move the torrent's description (title, description, categories, magnet URL) into a torrent of its own. Indexers find the first hash via the blockchain, use it to fetch the full torrent description via DHT, which in turn allows it to find the torrent via the magnet URL (or alternatively, includes the .torrent file directly, but this trades network efficiency for hosting overhead)
To speed up bootstrapping new indexers, occasionally "rollup" descriptions could be published, which are just torrents that aggregate a large number of descriptions (bucketed say, by date, DHT swarm size, or similar). Add an identifier and public key to these roll-up releases, and you effectively have a trusted "channel" - one guy or group with editorial control over the index they publish, and magically you have something very close to ThePirateBay again.
So something I've been wondering about with all the talk around The Pirate Bay recently is why aren't people using the blockchain to store data needed to bootstrap your joining of a decentralised network. It could be as simple as storing the magnet links themselves.
The main problem I see with this is that you would have to have each client in the botnet sync with the Bitcoin network. This is a lengthy task and results in gigs of data. Hardly inconspicuous. But I like the idea.
And new blocks are "only" ~400KB in size - at 1/10min, that's less than 700B/s. (Of course, it'll be more in practice. But still, not much.)
Haha, I had the same idea. The since (valid) transactions are passed freely to all nodes in the Bitcoin network, one can just use the network as a signed messaging platform. You don't need to query blockchain.info, all you need is a Bitcoin client that listens for incoming transactions. I've been writing an implementation on and off for a while now. The general idea is as follows: The botnet client connects to "n" Bi…
> You don't even have to use transactions ("tx" messages), you can use the block messages if you are willing to tolerate an (on average) 10 minute delay Does this mean you can send messages without transfering bitcoin from one account to another?
is this a published paper? O_o