but I think we'll be focusing on finishing HD, adding CoinJoin, and then things like BIP70 and another very huge project
If that's meant to be a chronological roadmap, it's nice to see CoinJoin near the top  . |
|
|
|
I understand for mining one can specify the number of cores (in this case to all) as setgenerate true genproclimit -1 Can I instruct a freshly installed bitcoind to use all the cores to verify the signatures to speed up the initial set up of the core client? It's a command-line/bitcoin.conf parameter called "par". See the builtin help. |
|
|
|
Por cierto la drástica subida del precio parece que ha empezado, como siempre la he clavao.
Sigue sigue! Que mi oferta va en serio  . Suave pero sin pausa, cual era el objetivo? $450 a fin de mes. No ahora, coñe, que aún no hemos cobrado! (lo de "ahora" lo digo porque se han alcanzado en bitfinex). |
|
|
|
(I've actually changed my vote to the rainbow. Yay for being able to remove vote and re-vote)
I didn't know this! Thanks for mentioning it, I've just changed my vote as well. |
|
|
|
|
Only works in the javascript enabled ddg. Plain HTML has no magic.
|
|
|
|
|
A partir de ahora en español, que lo entienda mi padre (y el de muchos otros) si se pasa por aquí. Si luego además lo queréis poner en ελληνικά ya me da igual.
|
|
|
|
Por cierto la drástica subida del precio parece que ha empezado, como siempre la he clavao.
Sigue sigue! Que mi oferta va en serio . |
|
|
|
Thanks dree12, theymos_away and DannyHamilton, now I think I have it (but I'll have to try to actually *see* it  ). |
|
|
|
I must be missing something then. Let's say I (user id 17768) achieve Legendary status next tuesday, when my activity goes from 798 to 812. That means that: 799 <= 775 + conv(substr(sha1(concat('17768',secretSeed)), 1, 2), 16, 10) <= 812
24 <= conv(substr(sha1(concat('17768',secretSeed)), 1, 2), 16, 10) <= 37
0x18 <= substr(sha1(concat('17768',secretSeed)), 1, 2) <= 0x25And by removing the substr(…, 1, 2) part we infer that secretSeed is either: - some word such as sha1(concat('17768',secretSeed)) results in any hash starting with 18, or - some word such as sha1(concat('17768',secretSeed)) results in any hash starting with 19, or - some word such as sha1(concat('17768',secretSeed)) results in any hash starting with 1a, or ... - some word such as sha1(concat('17768',secretSeed)) results in any hash starting with 25. And it isn't difficult to find those 14 possible seeds, right? |
|
|
|
But even after having a bigger samplesize of existing Legendary members you can't get any results, because you don't know what activity level each of those was needed for the status.
But you only have a narrow space possible, if you take into account that activity doesn't increase by more than 14 each period. That complicates things somewhat, but by looking at what members became Legendary in each activity-payday, it shouldn't be very complicated to find a suitable seed. |
|
|
|
I guess I'm almost to the next level (Legendary) except I was randomly chosen to wait a little bit longer.
As was I. I feel robbed. Seems there are a few of us on the verge of becoming legend . @DH, we both even have the same activity . Re: the secretSeed, the resulting hash is substr'ed to extract only two hex digits, so if I'm not mistaken there are tons of seeds that yield the same substr(sha1(…), 1, 2). It's easily bruteforceable. |
|
|
|
Venga, sigue. Si a finales de mes estamos en $450, te pago . |
|
|
|
Will there be a transitional period, in which some users and miners do not attempt to reconstruct blocks and rely on the old block propagation method? Yes. Read Gavin's gist. Also what happens to new nodes. New nodes won’t have the memory pool data from say 12 months ago, how will they reconstruct those old blocks. Will the download of the historic blockchain work in the same way as it does now?
Older blocks are downloaded like now, newly mined blocks are propagated following this new mechanism. If mostly all transactions in the memory pool end up in a block, the pool starts (almost) empty every 10 minutes for everybody so "getting up to speed" isn't a problem. |
|
|
|
|
Para usar dumpprivkey primero tienes que usar walletpassphrase.
|
|
|
|
In members page, the position is in this order : VIP>Staff>Sr.Member . So where is Hero Member? Was Hero Member applied later but didn't changed the code in the navigation page? Can you change it to : Administrator > Global Moderator > Moderator > Staff(If any) > VIP > Legendary > Hero Member and so on or VIP after admin or global mod?
I think the order is alphabetic. Legendary people start on page 7368 (as of this writing but that changes fast!). |
|
|
|
Esto sigue en blanco .
|
|
|
|
|
I'm wondering how effective would a "Please spare me the details" strategy be. Like "I don't want the details, just BTC for fiat period".
|
|
|
|
|
No sobraba un "NSFW" en el título.
|
|
|
|
Más infomaricón se puede encontrar en la página web.
Bastante oportuna la secuencia de errores . |
|
|
|
|
Estas son mis notas personales que tomé en su día. "Coiner" tiene BTC, "Seller" tiene algún producto o servicio (que pueden ser euros):
1) Escrow, en la sección "Escrow Agent" genera dos claves (Escrow Invitation A y Escrow Invitation B) y da a Coiner la A y a Seller la B.
Escrow: A B
Coiner: A
Seller: B
2) Seller con su clave B irá a la sección "Payee (Generate Payment Invitation)" y generá una clave C (Payment Invitation), y un address publico en donde Coiner deberá pagar con sus BTC por lo que está comprando.
Escrow: A B
Coiner: A
Seller: B C addr
3) Seller entrega a Coiner la clave C (Payment Invitation) y el address público en donde Coiner deberá bloquear su pago. No debe entregar a Coiner la clave B ni tampoco debe entregar al escrow la clave C.
Escrow: A B
Coiner: A C addr
Seller: B C addr
4) Coiner con la clave A, que recibió del Escrow, y con la clave C (Payment Invitation), que recibió de Seller, verifica en la sección "Payer (Verify Escrow & Payment Invitations)" que el address público que le envió Seller es el correcto.
Escrow: A B
Coiner: A C addr, verifies addr
Seller: B C addr
5) Coiner envía y congela los BTC con los que le comprará a Seller el producto. Esto lo hace enviando los BTC al address de quien, por ahora, todavía nadie es dueño.
Escrow: A B
Coiner: A C addr, makes tx
Seller: B C addr
6) Coiner comunica a Seller la transacción. Seller lo verifica en blockchain.info.
Escrow: A B
Coiner: A C addr
Seller: B C addr, verifies tx
7) Visto que los fondos están bloquedos, Seller finalmente envía su producto a Coiner de forma verificable. Esto por si surgen problemas, el Escrow pueda interceder.
Escrow: A B
Coiner: A C addr
Seller: B C addr, sends item
8) Una vez que Coiner recibe el producto, entrega a Seller la clave A.
Escrow: A B
Coiner: A C addr
Seller: A B C addr
9) Seller a este punto es la única persona que tiene las tres claves: A, B y la C (Payment Invitation). Con las tres claves va a la sección "Collect Bitcoins" e introduce las tres claves. Esto le generará la llave privada con la que podrá retirar los BTC bloqueados por Coiner en el address público.
Escrow: A B
Coiner: A C addr
Seller: A B C addr, generates privkey
|
|
|
|
|
Show Posts
