Topic: Upload download data from blockchain (Read 1136 times)
Anyone for python?
Oh no? So why its says "@petertodd petertodd Change publish-text.py txouts to be a bare OP_RETURN" ?
Because it is not possible to create a transaction without outputs.Publishing data is not a classic transaction which transfers some value from person A to person B.
Quote
Also the point is to have the scripts to parse the blockchain for data and to upload.
I can create such 'downloader' for @petertodd's 'uploader'Unfortunately, I prefer programming in C++, not in python.
Also have a look here: https://bitcointalk.org/index.php?topic=1023190.5
Thanks i know the technical background but i need someone to modify the above scripts to work!
Why not to use https://github.com/petertodd/python-bitcoinlib/blob/master/examples/publish-text.py ?It doesn't use op_return technique
Oh no? So why its says "@petertodd petertodd Change publish-text.py txouts to be a bare OP_RETURN" ? Also the point is to have the scripts to parse the blockchain for data and to upload.
Thanks i know the technical background but i need someone to modify the above scripts to work!
Why not to use https://github.com/petertodd/python-bitcoinlib/blob/master/examples/publish-text.py ?It doesn't use op_return technique
IIRC Bare multisig is not standard, but using OP_RETURN is. Using bare multisig for this will burn Bitcoin.
The basic idea is to break up your data into 65 byte chunks, which are the "public keys" as interpreted by Bitconi's scripting system. Then you just make the output in the multisig format,
. You can only go up to OP_15.
The basic idea is to break up your data into 65 byte chunks, which are the "public keys" as interpreted by Bitconi's scripting system. Then you just make the output in the multisig format,
Code:
OP_1 ... OP_X OP_CHECKMULTISIG
where OP_X is the number of Thanks i know the technical background but i need someone to modify the above scripts to work!
IIRC Bare multisig is not standard, but using OP_RETURN is. Using bare multisig for this will burn Bitcoin.
The basic idea is to break up your data into 65 byte chunks, which are the "public keys" as interpreted by Bitconi's scripting system. Then you just make the output in the multisig format,
. You can only go up to OP_15.
The basic idea is to break up your data into 65 byte chunks, which are the "public keys" as interpreted by Bitconi's scripting system. Then you just make the output in the multisig format,
Code:
OP_1 ... OP_X OP_CHECKMULTISIG
where OP_X is the number of
Noone? tip inside <-- 
That uses op_return...i am searching to modify the above scripts to work with standard output and multisig
I found this http://www.righto.com/2014/02/ascii-bernanke-wikileaks-photographs.html#ref13 article.
It describes some techniques to upload/download data from blockchain, but the scripts referred are not working.
I know the default to upload custom data is op_return but i want to try multisig too.
https://gist.github.com/shirriff/64f48fa09a61b56ffcf9#file-bitcoin-file-downloader-py
https://gist.github.com/shirriff/bfc4df70a02732493a28#file-bitcoin-insertion-tool-py
Anyone know how to modify these to work? they seem deprecated. I am willing to send a tip!
It describes some techniques to upload/download data from blockchain, but the scripts referred are not working.
I know the default to upload custom data is op_return but i want to try multisig too.
https://gist.github.com/shirriff/64f48fa09a61b56ffcf9#file-bitcoin-file-downloader-py
https://gist.github.com/shirriff/bfc4df70a02732493a28#file-bitcoin-insertion-tool-py
Anyone know how to modify these to work? they seem deprecated. I am willing to send a tip!
Jump to: