|
This post will be rather useless but I think it's important to thank people that helps Bitcoin
So, once again, thank you!
|
|
|
|
|
With non-standard transactions it would have been easy to do
|
|
|
|
|
Triple posting isn't necessary, we have a magical "edit" button for this
|
|
|
|
|
Try dumping your wallet with pywallet
|
|
|
|
|
I couldn't find any
I'm sure there was a wiki article about this though...
|
|
|
|
|
This address likely belongs to your account at happycoins, I'm sure you can withdraw it to another address being on your computer
I didn't know how happycoins work
|
|
|
|
|
Twitter is definitely going evil as the time goes
|
|
|
|
|
I'm not sure Google would accept Bitcoin ads
|
|
|
|
|
You can verify that no node broadcasted the tx, then delete it from your wallet, then create the same tx but with fees
|
|
|
|
|
You can't "fix" the transaction but you can delete it from your wallet
|
|
|
|
Re-using an address is a bad practice for anonymity. You are welcome to do so if you wish, but if you care about anonymity you should use a brand new address for EVERY TRANSACTION. That address should only be shared between the sender and the receiver. In that way, only the sender and receiver have any idea who the parties to the transaction are. This satisfies your concerns about only the involved parties knowing who participated, while maintaining a public ledger that provides every participant to verify the validity of the bitcoins that they receive without needing to trust any other peer.
How often do you verify random transactions of others? Oh. Wow. |
|
|
|
|
I made the rules for rock-paper-scissors-lizard-Spock-Bitcoin-FED
I'll upload them soon
|
|
|
|
|
Ah ok!
C'est par simplicité, soit la transaction est utilisée soit elle ne l'est pas. Pas de morceaux de transactions semi-utilisées.
Sinon, à chaque fois que tu utilises une transaction il faudrait re-vérifier dans toute la blockchain toutes les fois où cette transaction a été utilisée, puis sommer pour vérifier que ça dépasse pas ce qu'elle t'avait apporté
J'espère que ce que je dis est compréhensible
|
|
|
|
"Pope Benedict XVI will die by the end of September 2013" This can't be refused  |
|
|
|
Everyone's heard of rock/paper/scissors, and since Bitcoin uses cryptographic hashes to make it secure, why can't rock/paper/scissors? So, here's what you do: Choose rock, paper, or scissors, and hash that , underscore, and 20 random capital letters, with sha256. For example, if you were choosing paper, you could hash "paper_WJJADWEQJGOSOTHIURXX", and get df9c9320c577fff3cfe35beb8e139a7ecb4d7fd155a48118f28d30e254128295. Post your hash, wait for someone else to reply with their hash, then both people provide their original strings, revealing the winner. Sound fun? You can use the random string generator here to get the 20 characters: random.org/stringsChoose 1 string, 20 characters, only uppercase letters. I'll start with bb42b7b6f3522e643ba2880c986f8d7b4098a302a832e52a8d1e327071b3158f Good idea you should make a web app I'm not OP but I liked the idea! http://cryrps.net46.net Btw Gage, you can't have an even number of options because you need as many winning "battles" than defeating ones. I'm sure it's not clear I'll try to be clearer once I wake up in a few hours! I assume that only applies to Base 10. What? Being even or odd has nothing to do with bases |
|
|
|
|
Show Posts
