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! |
|
|
|
blocks will never stop being created.
My HDD does not approve this message |
|
|
|
|
I was wondering about how much instant sports bets with European leagues is wanted.
I know BTCsportsbet and blockbet. But they are really poor about EU sports.
Anonibet is kinda full but requires an account, an email account, being 18yo, agreeing to some conditions, doing deposits and withdrawals
I'm quite interested in developping that with many sports/countries(even out of EU) but I don't want to lose my time as I also develop pywallet.
That would work like SatoshiDICE, you would receive to the address you sent the money from, no account or anything
|
|
|
|
Je ne comprends pas ce que tu demandes ou ne comprends pas Du coup je vois pas vers quoi te diriger On utilise les transactions précédentes parce que justement c'est de là que vient l'argent Tu peux regarder ici: https://en.bitcoin.it/wiki/TransactionsTu connais le principe d'un chiffrement asymétrique? |
|
|
|
|
1. Everyone stop mining
2. Difficulty falls
3. Mining become more and more profitable
4. People start mining again
5. There are so many people mining that mining isn't profitable anymore
6. Go to 1
7. ? ? ?
8. Profit
|
|
|
|
Coins become lost when the private keys to them aren't stored anywhere, and nobody is holding them. So though the coins never really disappear, they can't be moved anywhere, because no one has the private keys required to move them.
Can't the private keys be cracked the same way they are discovering new coins? I wouldn't have to bruteforce 115792089237316195423570985008687907853269984665640564039457584007913129639936 possibilities Have they invented -illion words for how much that is?  115 quattuorvigintillion, 792 trevigintillion, 89 duovigintillion, 237 unvigintillion, 316 vigintillion, 195 novemdecillion, 423 octodecillion, 570 septendecillion, 985 sexdecillion, 8 quindecillion, 687 quattuordecillion, 907 tredecillion, 853 duodecillion, 269 undecillion, 984 decillion, 665 nonillion, 640 octillion, 564 septillion, 39 sextillion, 457 quintillion, 584 quadrillion, 7 trillion, 913 billion, 129 million, 639 thousand and 936  I smell Wolfram Alpha |
|
|
|
N'hésite pas si tu as d'autres questions! Si tu veux utiliser mon fork, tu peux lire le post à son sujet (signature), la dernière version est là (c'est la dernière version, qui est en beta, mais pour la fonction en question ça fait longtemps que ça marche) Il utilise blockexplorer.com pour trouver le solde, il met un peu moins de 2min/100adresses |
|
|
|
je ne comprends pas comment ces clés supplémentaires interviennent dans le processus d'utilisation.
Envoyer des bitcoins ce n'est pas vraiment comme envoyer de l'argent. Ça marche par transactions. Par exemple, disons que ton seul argent (1BTC) provient d'une seul transaction (de p2pool) vers ton adresse 1xxxxx, et que tu m'envoies 0.3BTC. Lorsque tu reçois de l'argent aucune adresse "secrète" n'intervient. Elles interviennent lors de la sortie. Quand tu paies, tu utilises TOTALEMENT ce qu'une (ou plusieurs) transaction t'a apporté. Tu dis j'utilise telle transaction (ici 1BTC), et en sortie j'utilise l'argent de telle manière. Ici ça donnera "J'utilise la transaction *****, ce qui fait 1BTC en entrée. En sortie, je paie 0.3BTC à l'adresse 19Qceuzhiuhziuzajza(moi) et je me renvoie les 0.7BTC restants." Puisque tu te renvoies de l'argent il te faut une adresse, et mais ce n'est pas vraiment une transaction puisque ça reste chez toi, du coup bitcoin utilise une adresse cachée. J'ai actuellement 3 transactions qui sont le fruit d'un minage avec p2pool (je l'ai fait pour essayé, je n'ai que quelque centimes), qui ont été payé sur l'adresse ayant été généré par p2pool. Du coups, je suppose que si je récupère la clé privé de cette adresse et que je la réimporte dans un autre client, les bitcoins présents sur cette adresse seront disponible également dans l'autre client, je me trompe ?
Non tu ne te trompes pas Du coups, en quoi conserver ces adresses seraient important ? Si tu n'as jamais payé quoi que ce soit, aucune utilité Surtout que vu leur nombre, toute les importer prendrait un temps considérable En deux clics avec mon fork Mon fork permet aussi d'afficher le solde de TOUTES les adresses d'un wallet |
|
|
|
Coins become lost when the private keys to them aren't stored anywhere, and nobody is holding them. So though the coins never really disappear, they can't be moved anywhere, because no one has the private keys required to move them.
Can't the private keys be cracked the same way they are discovering new coins? I wouldn't have to bruteforce 115792089237316195423570985008687907853269984665640564039457584007913129639936 possibilities |
|
|
|
According to a few on zerohedge some of the banks will never re-open.
Unlikely IMO. But we'll know soon. |
|
|
|
I predict a jump in the price of pop-corn of around 100%  As for Bitcoin, I don't think anything will change, or yeah something like 2-3$ |
|
|
|
I'm releasing a beta version: http://pastebin.com/R1C8Qavv (put all the code in a new file you name pywallet.py) Yes it's public, yes it works, but no it's not 100% sure yet so use only disposable or backed up wallets with it I hope the beta testers didn't find some big issues I didn't see |
|
|
|
Fixed prob by changing browser from chrome.
wat |
|
|
|
|
Oh yeah thanks
I'll try to find such pools. I believe I saw on blockchain.info a form to submit a tx, do you know if it is only working with standard ones?
|
|
|
|
|
Elles sont utilisées lors de paiements, donc oui il faut absolument les sauvegarder même si beaucoup seront vide en effet
Ton wallet est-il chiffré?
Tu utilises quel pywallet? Celui de Joric ou mon fork?
|
|
|
|
Addresses with 6 fixed characters are pretty common (K1773R owns 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y), the odds are ~1/57billions
The odds of having an address with only upper case letters and digits is (36/62)^34 ~ 1/17billions
It's about 4 times quicker to find such an address than an address with 6 fixed characters. Far from impossible. But the last characters are checksum. Just because you can get all uppercase in what you go for vane doesn't mean you can get an all uppercase checksum as well. Since a checksum is a hash, I doubt you can even calculate the odds on that... Given the random nature of a hash, though, I doubt it can be proven impossible either. The random nature is exactly why I think we can apply odds to this For exemple, let's take characters in "0123456789" Addresses in that system is 6 random digit + 4 digit from hash The condition we want is "<3" So: - the odds for the 6digits part is (3/10)^6 - about the hash part: the hash is random, so you have 3/10 odds that one character of the hash is <3 - then the hash part has (3/10)^4 odds to be written with 4 "<3" digit So finally, we get (3/10)^10, just like if we don't take into account the fact that last characters are from a hash This works because a hash is random, this gives the necessary linear independance I might be proven wrong though |
|
|
|
|
The money is not stored in your wallet but in the bitcoin blockchain, which says for example that the address 19Qndhcus62ggx2794n has 10BTC
In order to redeem that money, you need to prove you possess the keys associated with the address (kind of a password)
In the wallet file, you only have those keys
So you may copy a thousand times your keys, you would have the same amount of coins because the amount stored in the blockchain wouldn't have changed
|
|
|
|
|
Show Posts
