If the majority of hashing power The majority of hashing power voted, and the vote was: rollback and revert to 0.7 |
|
|
|
|
Let's make clear this: if your computer is infected then everything you do on that computer is not safe, no matter what.
|
|
|
|
Reverse other people's transactions
Send coins that never belonged to him
I don't agree with this. As far as i know, yes he can! |
|
|
|
What does chargeback mean?
Reversal of payment. Yea, but as far as I can see, chargeback only applies when there is a dispute, or goods are not as expected etc. I cant see how it would apply in purchasing bitcoins. Not exactly. What happens is that a guy buy bitcoin with credit card and then revert the payment. You don't believe me? Try selling bitcoins for paypal or credit cards payment and tell me how it goes  |
|
|
|
What is to stop a government or even an institution (read bank) putting 10,000 asic miners in a building and subverting the network to their new chain? Nothing. There are some suggestions about what to do in this case and how to avoid the attacker chain to be used by the clients but well, so far nothing serious. Technically a 51% attacker can rebuild the chain from where he want and do what he want with all the transactions, keep them or reject them. |
|
|
|
It makes sense, you have to check how much time it took to find this block  And the reward system of the pool etcetc |
|
|
|
|
Nothing.
If you don't trust pools, then use p2pool, a decentralized pool, everything is managed by a software and thus 100% safe.
|
|
|
|
Oh noes, the ATM networks is forked! -MarkM- The Euro just forked. There is Euro on bank account in cyprus and there is Euro cash on hand or in Germany. Their exchange rate is not 1:1. This, sir, is awesome |
|
|
|
|
It seems now they no more laugh at bitcoin but moved to attack it.
|
|
|
|
we're working on solving blocks for "new" BTC, and we're solving other blocks that are created during wallet transfers? More or less yes. Mining find blocks, when a block is found, the miner (the pool in this case) put inside it the transactions and also the transaction of the "new" BTC. |
|
|
|
|
Or use a lightweight client
|
|
|
|
Confirming (putting them in a block) transactions IS exactly why mining exist. |
|
|
|
|
Easy, it refuse the second transaction.
The node receive the first connection. Then receive the second one, it is a doublespend, so it is invalid and refused. The node will only keep the first one.
|
|
|
|
|
Show Posts
