Name the first currency that pops to your head when you see this image: Was it bitcoin? No. It was "Monopoly Money".
|
|
|
If he is in hiding (not stashed in some hotel in Hong Kong), sending him bitcoin will potentially out him.
what are you talking about? if he posts an address and ppl send him coins, so what? since when is that illegal? and since when would that reveal an ip address? any spending out of his address would be unknown as to its purposes or usage since you wouldn't know the identity of anyone associated with those receiving addresses. he could buy alpaca socks for all you know. Because the actual posting of the address could reveal his IP.
|
|
|
Do the advertisers pay premium for the anti-ABP code?
Actually, ABP charges money to unblock ads. You have to be considered non intrusive AND pay em. This is why you should use Adblock without a plus. They're not corrupt.
|
|
|
Payment offered: .08 BTC
what i need: src code to be fixed so i can compile it. i keep running into key test errors and can't make head nor tails of it. if you can get the src to compile,create the genesis block, then compile again and send the windows binary back to me, i will pay you .1
I won't pay if:
-you mine the genesis block.
-it won't compile after you send it back to me, or if you compile it before sending it me.
-you try to keep a copy and pre-mine my coin.
Wait, so you pay if they create the genesis block, but don't pay if they create the genesis block?
|
|
|
#3 is amazing!
Yeah, but 4 is so friendly looking!
|
|
|
I agree. I've watched a few episodes, and it's entertaining.
|
|
|
Hello all. The wonderful moltenmich has given me these great logos to use for Frog! If you're wondering what Frog is, check out the thread and the Bitcoinstarter. Please make sure you understand the project before voting. Here are the options: Which do you like best? You can choose two if you're having a tough time.
|
|
|
I have tried to build a proper .app for Bitmessage for a while, but I could never figure out how to properly bundle OpenSSL. So, I made this guide. But now it's obsolete as a great OS X build script is now included in Bitmessage! You can download the DMG here: MEGAVery cool to hear! Does it work for you?
|
|
|
Whoa, what a useful thread. Am I supposed to send Bitcoins to those addresses?
|
|
|
I have tried to build a proper .app for Bitmessage for a while, but I could never figure out how to properly bundle OpenSSL. So, I made this guide. But now it's obsolete as a great OS X build script is now included in Bitmessage! You can download the DMG here: MEGA
|
|
|
They steal bitcoins for their users. Randomly. And usually inactive wallets. Noone even knows it And wallets where people have lost the key right? That was a joke. No good clients steal Bitcoin.
|
|
|
https://blockchain.info/wallet/send-sharedOver $ 4,776,872,509.45 Successfully Transacted They charge a 0.5% fee, it used to be 1-3%... $4776872509.45 * 0.005 = $23884362.54725 I think piuk is a very, very rich man now. If only. That figure includes none-shared transactions as well and the majority of blockchain's transactions are free. Luckily the site has very low operating costs. OK. Thanks for explaining that. I'd like to thank you for operating the Blockchain site, and I especially appreciate the iOS app. It's the only Bitcoin wallet available, and it's pretty good.
|
|
|
fucking nerds. C'mon. If you're going to use this currency, might as well know how it works.
|
|
|
Thanks. Can you link me to the formula used to convert difficulty to target? Is it simply the max target divided by the difficulty?
Yes. maximum_target = 0x00000000FFFF0000000000000000000000000000000000000000000000000000 difficulty = maximum_target / current_target multiply both sides by current_target: current_target * difficulty = maximum_target divide both sides by difficulty: current_target = maximum_target / difficulty Thank you! Now I understand.
|
|
|
1JaxkrMxYZQiqtKExdwB1NAAE98mQ4RRVt
|
|
|
Thanks. Can you link me to the formula used to convert difficulty to target? Is it simply the max target divided by the difficulty?
|
|
|
Make sense?
Kind of. So the target is a 64 bit number that represents what the hash of the block in numeric form needs to be less than. So, the hash of the block is treated as a hex number, and compared to the target, and it has to be less than the target? Kind of. A sha256 hash is always a number, no matter how you represent it (hex or not). The target is also a number, and it can be represented however you want. Regardless of format, the hash of the block 's header is treated as a number, and it has to be less than the target. OK. The header contains a hash of the list of transaction in the block, so there is no computational incentive not to include transactions. And the reason a large amount of zeros are needed prefixing the hash is because it make the value of the hash less than the target. Thank you for explaining that. Could a POW algorithm work just as well when the hash has to be greater than the target? Eg. It's prefixed with "fffffff" instead of "000000"?
|
|
|
Looking for n-zeroes in front isn't precise enough: difficulty jumps exponentially with every digit. Instead, the miner looks for hashes that are numerically less than the target. Here's the maximum target: 0x00000000FFFF0000000000000000000000000000000000000000000000000000 A maximum target means a minimum difficulty, because the higher the target, the more hashes are less than that target. The difficulty is the maximum target divided by the current target. As the current target goes down, it becomes harder to generate blocks. The current target is the denominator of the difficulty equation, so as current target goes down, "difficulty" goes up. Make sense? Kind of. So the target is a 64 bit number that represents what the hash of the block in numeric form needs to be less than. So, the hash of the block is treated as a hex number, and compared to the target, and it has to be less than the target?
|
|
|
I'm having a really hard time wrapping my head around what the difficulty number means. I don't understand how it can be so high, and how it can affect the target. I have read the wiki page, and it didn't really help. I understand how a rudimentary POW algorithm works. In fact, I've even written one. It hashes data, and adds a number on the end, and hopes that the resulting hash is prefixed with a certain amount of 0's (or any special character). I know that a hash that has a prefix of 5 zeroes is significantly more difficult than a hash that hash a prefix of 1 zero. Each nonce has a lower probability of producing that hash, therefore it's more difficult. So why isn't the difficulty just a whole integer? A difficulty of 1 means that the hash needs to have one zero. A difficulty of 2 means that the hash needs two zeroes in front of it. And so on. What does 19339258.272387 mean? And how does it affect the miner's target? Sorry for my cluelessness.
|
|
|
|