|
Send me some abstract coins, that will save you
|
|
|
|
Ca me rappelle mon interview devant l'ambassade d'Equateur à Londres le jour du discours d'Assange par une journaliste du Figaro: "Mon article vous citant sera en ligne dans la semaine" D'ailleurs j'avais casé une petite phrase sur Bitcoin J'attends encore  |
|
|
|
|
Bitcoin is the first true and secure money.
|
|
|
|
No.
We want mass adoption and adding a "milli" to the name just at a time when most people identify Bitcoin as, "That crazy internet bubble the geeks got stung by" is not going to help its image in my opinion.
Just call an mBTC something ELSE, a bit less geeky.
Apart from the US, the rest of the world is absolutely familiar in their daily lives with metric units like kilometers, milligrams, milliliters, millimeters, cents. It's not geeky at all and entirely natural to use millibitcoins, millibits or whatever. I suppose you are from the US? Look at all those geeks using those weird units.  GB in green? Hmmm... |
|
|
|
"Deposit"? Peut-être que le site que tu utilises arrondi mal? (tu donnes son nom? ) |
|
|
|
Rien à voir avec les commandes, mais plutôt sur leur utilisation.
A priori, ces systèmes utilisent les logiciels typiques cgminer ou bfgminer.
Avec plusieurs systèmes d'actifs, chaque Asic s'occupe de sa tâche à accomplir et au petit bonheur la chance, découvrir le nonce validant la cible. Évidement, plus il y a d'Asic, plus cette chance augmente. Pour autant, je ne pense pas qu'on puisse établir le constat suivant: capacité globale de travail effective = somme( capacité de chaque Asic ). Pour la capacité brute, oui, bien sûr, mais en résolution de travail non, vu que chaque Asic travaille de son côté. En d'autres termes, 10 Asics à 385 MH/s chacun, n'équivaut pas à un système global de 3850 MH/s (3.8 GH/s)
Ce qui pourrait être intéressant d'essayer, juste par curiosité, pour ceux qui possèdent de tels systèmes, c'est de "sérialiser" le travail à accomplir. Cela requière de développer un miner spécifique, mais peut être que le jeu en vaut la chandelle, comme on dit.
Par exemple, avec 4 Asics et en supposant que chacun a une capacité de calcul identique. Récupérer un travail à accomplir et la target (getwork).
Sachant que le nonce va jusqu'à 0xffffffff, chaque Asic reçoit un interval donné à explorer. Ici, 4 systèmes donc:
Asic #1: 0x00000000...0x40000000
Asic #2: 0x40000000...0x80000000
Asic #3: 0x80000000...0xc0000000
Asic #4: 0xc0000000...0xffffffff
Je me suis jamais vraiment intéressé au minage, mais je pensais que c'était le cas (avec asic, gpu ou cpu) Bonne idée sinon |
|
|
|
You are a braver guy than me.
Or stupid.
in fact i'd like to think all cryptocurrency is in part dedicated to President Kennedy.
and in a way it is, maybe not Bitcoin but hey? ha ha .
wat |
|
|
|
Why are addresses calculated from a hash of the public key, rather than using the public key itself? I understand why you would want to add a checksum to guard against typos, but why not append the checksum to the public key rather than its hash? Is it merely a matter of wanting to make the address shorter or is there a deeper reason?
This A public key is 65 or 33 bytes long A hash160 ( == ripemd160(sha256(x)) ) is 20 bytes long Also a bit of further security. Currently you need a signature AND the public key to redeem a transaction output. So even if someone breaks secp256k1, they would have to break ripemd260 and sha256 too to redeem that output. Except if that public key already redeemed an output once, in that case it is known: - unused address (notice "Public key: Unknown (not seen yet)") - used address (notice "Public key: 020338ce822bbf15ef68145e0d5a4838d8a2eb746ff024c1944e8d4f49c0574c55") |
|
|
|
Is it possible to convert tx_k tx_v to a raw transaction that can be sent by sendrawtransaction from within the newer clients?
tx_k is useless because it is '027478' (well I think so) + little endian tx id As far as I can remember, tx_v is not only the transaction: the bitcoin client adds some data (the transaction of its inputs if the client has them in its blockchain) So depending on what you're trying to do you can use it directly or parse it to put it in the newer client Don't worry, it's your project after all.
I would vote for a CLI. A seperate GUI is fine as well. A single pywallet with additional dependencies makes this great tool harder to use. But it's your tool - you decide.
It's my project but I'd prefer if people like using it and find it practical Also, I make all dependencies optional: currently you can use pywallet even if you don't have twisted+zope, you just won't be able to use the WUI. Same for ecdsa package and signature/verifications The new pywallet would follow this rule as well |
|
|
|
what are the rules for the lotto?
You play, you lose |
|
|
|
Genesis transaction: 2dd02e144c376dbb65c469c06bbcbb5b2d300ef5462f69d038298714aea19782 01000000010000000000000000000000
00000000000000000000000000000000
0000000000ffffffff5404ffff002001
044c4f6e636520746869732062616279
2068697473203838206d696c65732070
657220686f75722c20796f7527726520
676f696e6720746f2073656520736f6d
6520736572696f75732073686974ffff
ffff0100e40b54020000004341041ab8
6acc1a9f836807685d10121b0a21ba76
dc86f06d054d22188b38f8dc977448db
0e60841a13f2208d16d7835143623da2
3238ed4c48a2d0b4c59b18c7781cac00
000000
fuck anymore new coins, any new coins will literally be such a fail since we have over 1000 of them so far
This topic is just a sarcasm, can't you see it? You just won 20 FTR on your TRC address 1GobR3wsagS5BofoMvYfy5R4KgooeUBkWT Transaction id: b2119b2782ea7cb055b29c6ef28d0141438aa07bf5dc39e25bc987f1eaea5baf 01000000018297a1ae14872938d0692f
46f50e302d5bbbbc6bc069c465bb6d37
4c142ed02d0000000049483045022100
acfea88cbefeed43afb2eb0f13e30a9f
bfcbc45119975fa98a9ae65d27da260c
0220293cfd87f12efe209fc7b4dee397
1c91e34584f0e7de5dab64771b5a4748
962301ffffffff020050d6dc01000000
4341041ab86acc1a9f836807685d1012
1b0a21ba76dc86f06d054d22188b38f8
dc977448db0e60841a13f2208d16d783
5143623da23238ed4c48a2d0b4c59b18
c7781cac00943577000000001976a914
ad59bfb913ec1cc41ce5312cf97289be
d0b138f388ac00000000
Use decoderawtransaction RPC function in the Bitcoin client to check everything is ok |
|
|
|
There should be a limit of only 10 new alt coins per day. Any more than that and the whole alt coin concept becomes rediculous.
Yeah, 9 new coins per day isn't ridiculous |
|
|
|
The name speaks for itself THAT will be the best coin of all times Premine: 1917 blocks BlockTime: 2 years, 10 months and 2 days Reward: 1 JFK per block until block 1963, 0 after it Retarget: Once, block 1963 Koins are destroyed after 46 blocks of inactivity  |
|
|
|
LSD is worth 30,000$ per gram, doesn't stop people from "investing" into it even though they are buying 0.00005 of a gram for 20 bucks. Are drug users more enlightened than the average Bitcoin user?
They don't measure them in grams, but in "hits" (according to random internet searches), which is exactly the point being made here.  |
|
|
|
I think this is a good idea...not this coin but the general concept of spamming the first page of the Alternative Cryptocurrencies sub-forum with announcements for fake "shit/junk/pump-dump/garbage" coins. Hopefully the announcements for all the other POSCOIN will get lost in the clutter and people will quite releasing 2^16 coins a day.  How dare you say that Spider Pig Coin is FAKE?  I guess you can trade best with BBQcoin  after coin matures (5000 confirmations) it will be automatically exchanged for 10 BBQcoins  I approve SPCIP1 (Spider Pig Coin Improvement Proposal) I'll push that in the next protocol version |
|
|
|
|
Show Posts
