Author

Topic: Concept: OP_RETURN with torrent file to an HTML file = hostless website (Read 1014 times)

legendary
Activity: 3598
Merit: 2386
Viva Ut Vivas
An interesting idear, how would you handle website updates? You would need to make a new version of the page and create another 3 transactions using OP_RETURN to point to the updated version i guess...

Also, the concept will probably only work as long as enough people keep on seeding the page. Offcourse, it's really small so i guess most people won't mind doing this (if the page itself is usefull)

Like I said, you take the latest OP_RETURN from the address. So every time you update your page you just send the transactions again.

Hillary has stated that she wants to take down certain websites that are critical of her when elected. This may become something necessary sooner rather than later.
legendary
Activity: 3514
Merit: 5123
https://merel.mobi => buy facemasks with BTC/LTC
An interesting idear, how would you handle website updates? You would need to make a new version of the page and create another 3 transactions using OP_RETURN to point to the updated version i guess...

Also, the concept will probably only work as long as enough people keep on seeding the page. Offcourse, it's really small so i guess most people won't mind doing this (if the page itself is usefull)
legendary
Activity: 3598
Merit: 2386
Viva Ut Vivas
I have been mulling something over and would like to get some input.

I would like to make a serverless webpage using the blockchain + bittorrent.

Let's assume I have a web site with an HTML, some css and a few images compressed into a .zip file of 1Mb.

I then create a .torrent of that zip file, which includes a hash of the file's parts, and start seeding the file. Assume the .torrent file is 200 bytes in size.

I then create a Bitcoin transaction from address 1WEBaj42k2j23lk23nk23jlk2n1kj to any address.

I pay the transaction fee and include an OP_RETURN with 80 bytes from the .torrent with a preceding number like 1/3.
Then I send another transaction from the same address with another 80 bytes with a preceeding number 2/3, etc.

So now there is a series of OP_RETURNs from address 1WEBaj42k2j23lk23nk23jlk2n1kj that can be referenced from any Bitcoin node that tracks OP_RETURNs.

Now I create a browser extension that accepts btctp:/1WEBaj42k2j23lk23nk23jlk2n1kj as an input which then goes to that address and gets its last series of OP_RETURNs.

It puts together the .torrent file and connects as a bittorrent client to download the .zip file. The extension then extracts the contents of the .zip file and displays the web page.

This would prevent DDoS attacks. It would prevent hacks of your server. It would allow people behind censoring firewalls like China to get information and allow anyone to post simple content without the need for a hosting service.

And you are paying the miners in transaction fees. You pay the miners for larger .torrents so they are compensated and you pay for any updates you make, all via transaction fees.

Thoughts?

Could u not store the 200 bytes as part of the message field using a smart currency like Bitshares or NXT? and then rather then using a bitcoin address you use a bitshares or nxt address for the browser extension?

Prefix the message with something since u can't include a special op code

I may as well use Onecoin.

Bitcoin is the most secure ledger in the world. Having the highest security in the world for a site would be a good thing to have.
sr. member
Activity: 270
Merit: 250
I have been mulling something over and would like to get some input.

I would like to make a serverless webpage using the blockchain + bittorrent.

Let's assume I have a web site with an HTML, some css and a few images compressed into a .zip file of 1Mb.

I then create a .torrent of that zip file, which includes a hash of the file's parts, and start seeding the file. Assume the .torrent file is 200 bytes in size.

I then create a Bitcoin transaction from address 1WEBaj42k2j23lk23nk23jlk2n1kj to any address.

I pay the transaction fee and include an OP_RETURN with 80 bytes from the .torrent with a preceding number like 1/3.
Then I send another transaction from the same address with another 80 bytes with a preceeding number 2/3, etc.

So now there is a series of OP_RETURNs from address 1WEBaj42k2j23lk23nk23jlk2n1kj that can be referenced from any Bitcoin node that tracks OP_RETURNs.

Now I create a browser extension that accepts btctp:/1WEBaj42k2j23lk23nk23jlk2n1kj as an input which then goes to that address and gets its last series of OP_RETURNs.

It puts together the .torrent file and connects as a bittorrent client to download the .zip file. The extension then extracts the contents of the .zip file and displays the web page.

This would prevent DDoS attacks. It would prevent hacks of your server. It would allow people behind censoring firewalls like China to get information and allow anyone to post simple content without the need for a hosting service.

And you are paying the miners in transaction fees. You pay the miners for larger .torrents so they are compensated and you pay for any updates you make, all via transaction fees.

Thoughts?

Could u not store the 200 bytes as part of the message field using a smart currency like Bitshares or NXT? and then rather then using a bitcoin address you use a bitshares or nxt address for the browser extension?

Prefix the message with something since u can't include a special op code
member
Activity: 111
Merit: 15
Eat, sleep, code, repeat.
Use magnet links, not torrent files.
> Smaller
legendary
Activity: 3066
Merit: 1047
Your country may be your worst enemy
I don't think you could make a normal website this way. By "normal website", I mean something which downloads and shows up fast in the browser, something which is easy to update for the webmaster, and something optimized for search engines.
Maybe it could eventually become an alternative to a Tor hidden service?
staff
Activity: 4270
Merit: 1209
I support freedom of choice
legendary
Activity: 3598
Merit: 2386
Viva Ut Vivas
Maybe this can help: https://webtorrent.io
So the user will be able to download the website without installing anything.

Interesting. A javascript bittorrent client. I'd still need the extension to go to the blockchain and get the OP_RETURN.
staff
Activity: 4270
Merit: 1209
I support freedom of choice
Maybe this can help: https://webtorrent.io
So the user will be able to download the website without installing anything.
legendary
Activity: 3598
Merit: 2386
Viva Ut Vivas
I have been mulling something over and would like to get some input.

I would like to make a serverless webpage using the blockchain + bittorrent.

Let's assume I have a web site with an HTML, some css and a few images compressed into a .zip file of 1Mb.

I then create a .torrent of that zip file, which includes a hash of the file's parts, and start seeding the file. Assume the .torrent file is 200 bytes in size.

I then create a Bitcoin transaction from address 1WEBaj42k2j23lk23nk23jlk2n1kj to any address.

I pay the transaction fee and include an OP_RETURN with 80 bytes from the .torrent with a preceding number like 1/3.
Then I send another transaction from the same address with another 80 bytes with a preceeding number 2/3, etc.

So now there is a series of OP_RETURNs from address 1WEBaj42k2j23lk23nk23jlk2n1kj that can be referenced from any Bitcoin node that tracks OP_RETURNs.

Now I create a browser extension that accepts btctp:/1WEBaj42k2j23lk23nk23jlk2n1kj as an input which then goes to that address and gets its last series of OP_RETURNs.

It puts together the .torrent file and connects as a bittorrent client to download the .zip file. The extension then extracts the contents of the .zip file and displays the web page.

This would prevent DDoS attacks. It would prevent hacks of your server. It would allow people behind censoring firewalls like China to get information and allow anyone to post simple content without the need for a hosting service.

And you are paying the miners in transaction fees. You pay the miners for larger .torrents so they are compensated and you pay for any updates you make, all via transaction fees.

Thoughts?
Jump to: