Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bottle: A Bitcoin SV Browser

bottle.bitdb.network

Post reply on HN
Print view View original

41–50 of 149 posts

Re: Bottle: A Bitcoin SV Browser

#41

Post by Roujo »

looeee wrote: post #32
onion-soup wrote: post #25

Earlier quoted context omitted.

Yes. It lives as a transaction output under op code 'OP_RETURN'. See example of weather data stored on chain https://whatsonchain.com/tx/6dac238576e9778458bb62a2f7d936fd... >are there fees to host this data (as we need to pay miners to include data in a block)? Yes, current fees are about 1 sat/byte. This is really a write once, read many type of system.

> 1 sat/byte What's a sat?

Presumably a Satoshi, the nickname given to the current smallest fraction of a bitcoin that is recorded on the block chain - 0.00000001 BTC.

https://en.bitcoin.it/wiki/Satoshi_(unit)

Re: Bottle: A Bitcoin SV Browser

#42

Post by brianorwhatever »

jacobroyquebec wrote: post #24
onion-soup wrote: post #16

Earlier quoted context omitted.

You can upload it using, say https://add.bico.media/ . Then you just share the transaction ID or sha256 hash of the pdf file to recepient. Recepient can access that file as long as blockchain exists (basically forever). And all this is achieved by OP_RETURN, a special op_code in bitcoin script that allows you to return data to blockchain.

Except that the link you suggest is for BSV, a bastard fork of bitcoin that tries to lure newcomers.

adjective: bastard

    1. (of a thing) no longer in its pure or original form; debased.
The idea behind this fork is that it is bitcoin IN it's original form

Re: Bottle: A Bitcoin SV Browser

#43

Post by marsface »

thekyle wrote: post #34

It's a neat idea. Although, I'm skeptical of its practicality for hosting any serious amount of data. If everything is hosted on the Bitcoin blockchain then every node in the Bitcoin network will need to keep a copy of every file uploaded. I would prefer the DHT model used by IPFS and DAT where each node only hosts part of the network.

opcode return data can be deleted by nodes at will, they will be as redundant as they are profitable to the storage provider.

Re: Bottle: A Bitcoin SV Browser

#45

Post by ismatopius »

thekyle wrote: post #34

It's a neat idea. Although, I'm skeptical of its practicality for hosting any serious amount of data. If everything is hosted on the Bitcoin blockchain then every node in the Bitcoin network will need to keep a copy of every file uploaded. I would prefer the DHT model used by IPFS and DAT where each node only hosts part of the network.

Nodes would be big server farms and preserve immutability by competing for block rewards. If you're running a Bitcoin application you don't need to store the entire chain, only the subset you need.

Re: Bottle: A Bitcoin SV Browser

#46

Post by PowerfulWizard »

onion-soup wrote: post #25
Solvitieg wrote: post #20

If we are posting data to the Bitcoin blockchain, does this data live alongside transaction data? And if so, are there fees to host this data (as we need to pay miners to include data in a block)?

Yes. It lives as a transaction output under op code 'OP_RETURN'. See example of weather data stored on chain https://whatsonchain.com/tx/6dac238576e9778458bb62a2f7d936fd... >are there fees to host this data (as we need to pay miners to include data in a block)? Yes, current fees are about 1 sat/byte. This is really a write once, read many type of system.

So it will be roughly $115 USD per megabyte? (1% of a BTC). High, but at least you get a 10000x replication factor.

Re: Bottle: A Bitcoin SV Browser

#48

Post by voodoosurfer »

thekyle wrote: post #34

It's a neat idea. Although, I'm skeptical of its practicality for hosting any serious amount of data. If everything is hosted on the Bitcoin blockchain then every node in the Bitcoin network will need to keep a copy of every file uploaded. I would prefer the DHT model used by IPFS and DAT where each node only hosts part of the network.

OP_RETURN data can be pruned, actually. Miners/node owners can decide for themselves if they want to keep the data; eventually a market will emerge for such a service, but for now the blockchain is small enough that it's not a problem.

Re: Bottle: A Bitcoin SV Browser

#49

Post by phaser »

Please note this is hosted on the BitcoinSV (BSV) network, which is not the same as the Bitcoin network that we all know as BTC.

BitcoinSV has much bigger blocks than Bitcoin, which is probably why this idea is possible.

While the same idea could be applied for the original Bitcoin network, that is far more popular, it would be highly impractical as blocks are smaller and transaction costs are higher.

I don't want to start another big/small blocks debate but if this idea gets popular, I doubt there will be many nodes that want to host the insane amount of data that will be accumulated, and the incentives for hosting a full node cost-effectively is the main reason why Bitcoin blocks are small.

I also sense a malicious intention with the website not making any reference to the fact that this is not the BTC network that 99.9% of visitors associate with the word Bitcoin.

Re: Bottle: A Bitcoin SV Browser

#50

Post by djbits »

grahamperich wrote: post #12

VERY cool. It reminds me a bit of this project, which has some of the same concepts and uses the Ethereum blockchain: https://ethsites.io/ ethsites TLDR: host unstoppable censorship resistance websites that can be accessed anywhere in the world (as long as you can remember a small JS snippet or print it on a tshirt or something)

Idea taken from Bitcoin SV and it cant work at scale because ethereum doesn’t scale.
Post reply on HN