"This is why the bitcoins sent in this special transaction are unspendable, as the addresses are being generated from the document's hash fragments instead of from a private ECDSA key." I hadn't realised before that this means that you can provably "destroy" bitcoins. That is, you can "prove" that a certain bitcoin amount will never be spent again by anyone including yourself...
Yeah, the fact that bitcoins can be permanently destroyed is a little bit worrying, one of BTC's benefits is it's cap. What's the economical consequences of these coins being destroyed?
Proof of Existence: Storing Hashed Files in the Bitcoin Block Chain
41–44 of 44 posts
Re: Proof of Existence: Storing Hashed Files in the Bitcoin Block Chain
#42Adding lots of data to the transaction logs is one easy DDoS. Do so many transactions that the logs get to be larger than fit on most systems. With multiple Gigs of data already required, if someone was evil they could up the volume and keep people out of the game by making sure that that there were over a terabyte of transaction logs. Most machines won't have that kind of storage and would "fall off" the network. Pa…
Re: Proof of Existence: Storing Hashed Files in the Bitcoin Block Chain
#43Earlier quoted context omitted.
Bitcoin doesn't work by passing tokens around to represent the value. In a Bitcoin spend the value is simply added to the wallet/address's balance. Any further spend is deducted from the wallets balance. The "coin" is not a single token that lives on and is broken apart to be spent, so there's no way a coin could self destruct after being transferred.
You keep telling yourself that. I understand fractional coins. I was over simplifying for brevity. I'll give you a hint. You have to move the coins between two wallets you own before you create a coin that will "break" when it goes in to the third's wallet. The Third wallet accepts a coin that no one will take afterwards. The coin becomes undependable.
Re: Proof of Existence: Storing Hashed Files in the Bitcoin Block Chain
#44Earlier quoted context omitted.
What determines the size_in_bytes value? In general, let's say a govt agency get assigned an $18.5m budget to break the Bitcoin currency as much possible, what could their plan of attack be, i.e. spend that money in the most efficient way possible? Create a large ring of wallets and send tiny payment around the ring? Create less wallets but send large payments between them?
Why $18.5m?