|
Feb 14 2013: 27.0 -
Jan 01 2012: 4.7 =
22.3 / 13.5 = 1.65
|
|
|
|
|
Your wallet always changes, it contains information about any transactions you have sent or received and the current state of the Bitcoin network (the last block seen when it was running).
Your backup, provided you made it when Bitcoin was completely closed, will be good for at least 100 new addresses you create or 100 transactions you send, however it won't be good forever if you continuously use Bitcoin. There are 100 reserve pool addresses in the wallet that are for future use - one you have exhausted these and Bitcoin has to make new addresses that aren't in the backup, you can lose money if your backup is out of date.
|
|
|
|
It took just four hours back in June 2011 for the price to rocket from 27 to the still-standing record price of $31.90/BTC:  Guess what, the price is 27.4 again, the highest Bitcoin has been for it's entire history except for a few fleeting hours on that June 9. We are one button-click away from a new record price! Will it happen?  |
|
|
|
|
Good work noob for a random necro, and the above commenter congratulating something that is already completed in Bitcoin.
What is further described above doesn't make much sense.
A full Bitcoin client knows about every pending transaction on the network, and knows what transactions would be included if it were to presently mine a block using standard Bitcoin rules. It would be very easy to calculate an appropriate optional fee to ensure likely placement in the next block.
|
|
|
|
I never said it was one entity, probably a bunch of people that imagined June 2011 happening all over again:  |
|
|
|
This is what $600,000 of profit-taking looks like:  AKA how to make 20% in four hours if you knew when to buy and sell. |
|
|
|
That's no rebranding...  |
|
|
|
|
If you notice the one post he made on the forum a year ago, the "flash miner" was likely a flash remote exploiter that nobody got suckered into taking.
|
|
|
|
|
"I think I smell something too...smells like bacon. Yeah, I'm definitely getting some kind of pork product smell."
|
|
|
|
Like this, just click on the image below: |
|
|
|
|
If it was rich and wanted to become poor.
It's a much better business to let users transfer money between themselves and keep 1%.
|
|
|
|
There is no time restriction on re-spending transaction inputs; the same transaction can immediately be double-spent - resent with less change and more fees. The unconfirmed transaction will be discarded from memory pools when a replacement transaction using the same inputs is included in a block. I think you misunderstood any node following the reference client rules will drop and refuse to relay a double spend. I don't think this is true. I was able to double spend MtGox by sending a payment with the same coins (with fee) as was transmitted by MtGox auto-sweep an hour before (without fees). https://bitcointalk.org/index.php?topic=139180.msg1483106#msg1483106. It was included in the next block. |
|
|
|
afaik no miner software has that implemented.
The OP has two solutions: The first solution is to delete the offending transactions locally (requires some wallet.dat surgery). Other nodes including miners will "forget" about the unconfirmed transactions in time (I believe 24 hours?). This would allow creating a replacement transaction with an appropriate fee to ensure timely inclusion. There is no time restriction on re-spending transaction inputs; the same transaction can immediately be double-spent - resent with less change and more fees. The unconfirmed transaction will be discarded from memory pools when a replacement transaction using the same inputs is included in a block. The only caveat is that if you delete the transaction from the Bitcoin client and send a different total amount, Bitcoin may compose the replacement transaction from different inputs, since it uses an algorithm that chooses inputs based on minimizing change. A "resend transaction with more fees" feature could be implemented in Bitcoin that ensures a duplicate spend of the same inputs (plus more inputs if needed to add the increased fee). However there is little need, because the reference Bitcoin always includes at least the minimum fees. blockchain.info will temporarily brand your address with a double-spend warning for others when it detects them on the network. |
|
|
|
Here's the debug log's tail:
...
LoadBlockIndex(): transaction index disabled
LoadBlockIndex(): hashBestChain=0000000000000290e9c5ca7f9c4fb014c4f9f639dcffa6821c4616b7762509f7 height=220932 date=2013-02-13 09:02:08
init message: Verifying block database integrity...
Verifying last 288 blocks at level 3
LevelDB read failure: IO error: /home/default/.bitcoin/chainstate/029837.sst: No such file or directory
************************
EXCEPTION: 13leveldb_error
Database I/O error
bitcoin in Runaway exception
Is there any way to recover from this error?
I double-checked that there's plenty of disk space left.
I have a feeling that the tech support answer for this will be "remove the index directories and reindex". I would try fsck, and then look in lost+found for a 0-2MB file. Move it to the datadir as 029837.sst. See if Bitcoin doesn't stop crashing. |
|
|
|
|
Carrier pigeon may be another. Undersea 100 Gb/s direct wave access transatlantic fiber optic is a third.
|
|
|
|
|
Show Posts
