Pages:
Author

Topic: Storing large data in blockchain (Read 3952 times)

sr. member
Activity: 362
Merit: 262
April 21, 2015, 10:39:56 AM
#22
Source of the data: http://steve-parker.org/articles/others/stephenson/osshock.shtml

Quote
Young Americans who leave their great big homogeneous country and visit some other part of the world typically go through several stages of culture shock: first, dumb wide-eyed astonishment. Then a tentative engagement with the new country's manners, cuisine, public transit systems and toilets, leading to a brief period of fatuous confidence that they are instant experts on the new country. As the visit wears on, homesickness begins to set in, and the traveler begins to appreciate, for the first time, how much he or she took for granted at home. At the same time it begins to seem obvious that many of one's own cultures and traditions are essentially arbitrary, and could have been different; driving on the right side of the road, for example. When the traveler returns home and takes stock of the experience, he or she may have learned a good deal more about America than about the country they went to visit.

For the same reasons, Linux is worth trying...
legendary
Activity: 1106
Merit: 1026
April 17, 2015, 09:08:43 PM
#21
Does this mean that Bitcoin is pretty vulnerable against vandalism? What happens if someone is pushing giga bytes of text into the blockchain? Does text pushing to the blockchain cost more than a normal transaction?

Publishing 1 GB of data, assuming a standard fee of 0.0001 BTC/1000 byte transaction size, roughly costs 170 BTC, if the data is embedded via P2SH, as done here.
legendary
Activity: 2097
Merit: 1070
April 15, 2015, 03:14:04 PM
#20
* The guy who sent the transaction paid the fees for it. Actually, well above the minimum fee required.
He paid for it only to a miner who find block.
I am not sure that keeping ( 100 kilobyte ) x ( several thousands fullnodes ) x ( unknown time ) costs less than a couple of dollars.

I can assure you that it does
tyz
legendary
Activity: 3360
Merit: 1533
April 15, 2015, 02:54:37 PM
#19
Does this mean that Bitcoin is pretty vulnerable against vandalism? What happens if someone is pushing giga bytes of text into the blockchain? Does text pushing to the blockchain cost more than a normal transaction?

legendary
Activity: 1260
Merit: 1019
April 15, 2015, 10:23:24 AM
#18
I'm glad the majority does not agree with you.
Majority of whom does not agree with which proposal?
I am just asking questions and reading opinions.
sr. member
Activity: 467
Merit: 267
April 15, 2015, 10:17:58 AM
#17
Quote
* Why should his data be rejected and not color coins, stealth addresses, or any other non bitcoin data?
Because the majority can do anything.

Quote
Do we start judging what should be and shouldn't be allowed?
Have we stopped doing it?

I'm glad the majority does not agree with you.
legendary
Activity: 1260
Merit: 1019
April 15, 2015, 09:51:07 AM
#16
* The guy who sent the transaction paid the fees for it. Actually, well above the minimum fee required.
He paid for it only to a miner who find block.
I am not sure that keeping ( 100 kilobyte ) x ( several thousands fullnodes ) x ( unknown time ) costs less than a couple of dollars.

Quote
* Why should his data be rejected and not color coins, stealth addresses, or any other non bitcoin data?
Because the majority can do anything.

Quote
Do we start judging what should be and shouldn't be allowed?
Have we stopped doing it?

Quote
* The data can be pruned since it's part of the sigscript.
sr. member
Activity: 467
Merit: 267
April 15, 2015, 09:42:06 AM
#15
* The guy who sent the transaction paid the fees for it. Actually, well above the minimum fee required.
* Why should his data be rejected and not color coins, stealth addresses, or any other non bitcoin data? Do we start judging what should be and shouldn't be allowed?
* The data can be pruned since it's part of the sigscript.
legendary
Activity: 1260
Merit: 1019
April 15, 2015, 09:29:52 AM
#14
Look at BIP 66 voting that is going on now.  Nobody seems to care very much.
There is only one thing everyone cares. Profit of investments calculated in fiat currency.
So, you are right: nobody cares of the size of blockchain and the number of utxo and malleability and so on while bitcoin gains profits.
sr. member
Activity: 333
Merit: 252
April 15, 2015, 09:15:45 AM
#13
why are you saying it cannot be disallowed?
Because this is consensus code. It is too hard to change it, isn't it?

I suppose it depends on how significant  the change. is Whether any
used or potentially useful cases are affected.

If the change is mostly techincal then nobody will care.
Look at BIP 66 voting that is going on now.  Nobody seems to care very much.
legendary
Activity: 1260
Merit: 1019
April 15, 2015, 08:48:57 AM
#12
why are you saying it cannot be disallowed?
Because this is consensus code. It is too hard to change it, isn't it?
sr. member
Activity: 333
Merit: 252
April 15, 2015, 08:46:05 AM
#11
But the possibility of  pushing large chuncks of plain text in a single transaction
looks like a bug to me.
It is a feature, not a bug Smiley
If we disallow this feature (we can not, but hypothetically), somebody would create a tool which posts large data chunks as several small (chained or parallel) transactions.
Like I said, if it requires a specialized tool to get it out, then it can be ignored.

I mean, the blockchain probably contains your username already: there's an A at some place, M at some other, etc.
I can publish a tool that finds  it in the blockchain, but the tool would be longer than the piece of data in question (your username).


large chunks of plaintext, on the other hand, is a different matter.

why are you saying it cannot be disallowed?
legendary
Activity: 1260
Merit: 1019
April 15, 2015, 07:44:46 AM
#10
But the possibility of  pushing large chuncks of plain text in a single transaction
looks like a bug to me.
It is a feature, not a bug Smiley
If we disallow this feature (we can not, but hypothetically), somebody would create a tool which posts large data chunks as several small (chained or parallel) transactions.
sr. member
Activity: 333
Merit: 252
April 15, 2015, 07:06:16 AM
#9
this is ugly.
I mean, obviously there will always be ways to embed data into the blockchain;
but if one has to split them between a long chain of transcations, and also encode them somehow inside,
 then the information (and effort)  needed to extract the data is non-neglible, so one can ignore it.

But the possibility of  pushing large chuncks of plain text in a single transaction
looks like a bug to me.

Is it possible to make this kind of things non-standard, without compromising the
expressive power of the script? Like, the way those SASSAMA/ Bernanke ASCII pictures
were put was somehow "outlawed" later on.
legendary
Activity: 1260
Merit: 1019
legendary
Activity: 1120
Merit: 1164
April 14, 2015, 08:44:54 PM
#7
It is not too difficult to create a tool to get data as a plain text from these transactions (but I do not have interest to do it)

Speaking of tools ... http://bitcoinstrings.com/blk00251.txt Wink

Also here: https://github.com/petertodd/python-bitcoinlib/blob/master/examples/publish-text.py
legendary
Activity: 1106
Merit: 1026
April 14, 2015, 05:31:55 PM
#6
It is not too difficult to create a tool to get data as a plain text from these transactions (but I do not have interest to do it)

Speaking of tools ... http://bitcoinstrings.com/blk00251.txt Wink
legendary
Activity: 1260
Merit: 1019
April 13, 2015, 01:46:58 PM
#5
I wish this stuff didn't happen in the blockchain, the thing is bloated enough.
You may wish anything. But this is consensus code for accepting such things  Grin
legendary
Activity: 1274
Merit: 1000
April 13, 2015, 12:48:10 PM
#4
I wish this stuff didn't happen in the blockchain, the thing is bloated enough.
legendary
Activity: 1260
Merit: 1019
April 13, 2015, 07:00:55 AM
#3
link to the P2SH techinque?
BIP-16

Quote
the data is basically in plain text?
I see someone storing plain texts.
Of course it is possible to store any content.
Pages:
Jump to: