The fee goes to the miner who puts your transaction into the block chain. The transaction fee goes to the bitcoin pool owner, how they share it to miners is up to them and their honesty! The miner only gets the fee if they mine solo (and who does that these days?).
|
|
|
Thanks Libertaad, I was going to use that as a last resort. I really wanted to get Bitcoin-QT 0.8.1 working to be part of the Bitcoin network (I think that's important). Anyway, think I solved it, found all my coins now. This is what I did... Installed Bitcoin-QT 0.8.1 (if you ran it previously just delete the home/.bitcoin directory.)
I copied over the complete .bitcoin old directory (not just the wallet.dat I suspected it needs the old database)
I plugged in a wired network cable instead of wifi (I suspected network corruption = DB corruption).
Run it from the Command Line (Ctrl+Atl+T) with ./usr/bin/Bitcoin-QT -upgradewallet
Let it complete the sync from scratch, stopping it and making backups every so often, so you don't have to start over.
You need at least 40GB of hard drive space to do this.
Amazingly it all worked. Success in finding both my old and new coins!
You're welcome to donate to 1LUF4Jp8PprpHcQVwXyLjCrdbSjFuaycUs if this helped you avoid pulling your hair out in anger. Thanks. I'm putting it back on Wifi, I'll post here if I have any more problems with it, so bookmark this thread, if you're wondering about upgrading to 0.8.1.
|
|
|
okay, started over with the backup folder this time I run.. /usr/bin/bitcoin-qt -upgradewallet /usr/bin/bitcoin-qt -rescan which throws up this error.. EXCEPTION: St13runtime_error CWalletDB::ListAccountCreditDebit() : cannot create DB cursor bitcoin in Runaway exception
file wallet.dat has LSN 780/2077553, past end of log at 1/572406 Commonly caused by moving a database from one database environment to another without clearing the database LSNs, or by removing all of the log files from a database environment DB_ENV->log_flush: LSN of 780/2077553 past current end-of-log of 1/572406 Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment PANIC: DB_RUNRECOVERY: Fatal error, run database recovery wallet.dat: unable to flush page: 7 txn_checkpoint: failed to flush the buffer cache: DB_RUNRECOVERY: Fatal error, run database recovery PANIC: fatal region error detected; run recovery PANIC: fatal region error detected; run recovery PANIC: fatal region error detected; run recovery PANIC: fatal region error detected; run recovery PANIC: fatal region error detected; run recovery PANIC: fatal region error detected; run recovery PANIC: fatal region error detected; run recovery PANIC: fatal region error detected; run recovery File handles still open at environment close Open file handle: /home/user/.bitcoin/wallet.dat Open file handle: /home/user/.bitcoin/database/log.0000000001 PANIC: fatal region error detected; run recovery I close the CLI and GUI.. Restart Bitoin-QT and I see my old bitcoins but not my recently mined ones, the wallet is up to date hmm... any ideas?
|
|
|
Okay did it the other way around this time. Ubuntu 12.10 64bit (Quantal) and Bitcoin-QT 0.8.1 I let it run and it downloads all the blockchain. (backed up the whole directory this time) I then close it and copy in my wallet.dat file Then start it with... usr/bin/bitcoin-qt -salvagewallet but again I get... cannot initialize keypool on the GUI and bitcoin-qt: /usr/include/boost/thread/pthread/recursive_mutex.hpp:101: void boost::recursive_mutex::lock(): Assertion '!pthread_mutex_lock(&m)' failed. Aborted (core dump) on the CLI
|
|
|
Ubuntu 12.10 64bit (Quantal) and Bitcoin-QT 0.8.1 Crashes The previous version I had failed to complete the blockchain download so thought I'd upgrade. I deleted everything from previous version but for the wallet.dat file (i have copies though) Full blockchain downloading really fast until.. Bitcoin Error System error:CWalletDB::ListAccountCreditDebit():cannot create DB cursor ~14130 blocks remaining
file wallet.dat has LSN 780/2077553, past end of log at 1/333 Commonly caused by moving a database from one database environment to another without clearing the database LSNs, or by removing all of the log files from a database environment DB_ENV->log_flush: LSN of 780/2077553 past current end-of-log of 1/333 Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
so i try... usr/bin/bitcoin-qt -salvagewallet and i get... cannot initialize keypool
bitcoin-qt: /usr/include/boost/thread/pthread/recursive_mutex.hpp:101: void boost::recursive_mutex::lock(): Assertion '!pthread_mutex_lock(&m)' failed. Aborted (core dump) Any ideas? I'd really like to access my bitcoins!
|
|
|
You need 2Gb to play GTA4 on very high too
|
|
|
They've been 2 weeks away from shipping since October 2012 Bitforce SC (ASIC) products are in final stage development with initial shipping scheduled for the last half of November 2012. Bitforce SC (ASIC) products are in final stage development with initial shipping scheduled for the last half of December 2012. Bitforce SC (ASIC) products are in final stage development with initial shipping scheduled for the last half of January 2013. Bitforce SC (ASIC) products are in final stage development with initial shipping scheduled for the last half of February 2013. Bitforce SC (ASIC) products are in final stage development with initial shipping scheduled for the last half of March 2013. Bitforce SC (ASIC) products are in final stage development with initial shipping scheduled for the last half of April 2013.
|
|
|
The best ROI is the Ati 5830. About $90 used and 260-300MH/s.
|
|
|
Too long and even the rebuttal is wrong.
|
|
|
To go forward what about a biometric lock... fingerprint scanners are getting really cheap, and or a credit card reader modded to use bit coins....
Just my .02
George
Just get a big usb memory stick and boot linux (ubuntu etc.) from it, use it only for accessing your bitcoin wallet, throw it in a fire proof safe when you're done.
|
|
|
4850 is too old to mine with sell it and use the money to get a 5830 instead ($90 & 260-300MH/s).
|
|
|
Malware bytes picked up guiminer-scrypt, which was downloaded from mirror 2 in this thread https://bitcointalk.org/index.php?topic=150331.0Hitman Pro has picked up cgminer-fpgaonly.exe and cgminer.exe from the same download. Are these false positives? I'm gutted $700 is a lot of money for me. NEVER EVER STORE YOUR COIN WALLET ON THE SAME MACHINE YOU MINE ON! False positive my ass!
|
|
|
Place a cheap electrical timer on the power plug to force it to switch off/on every so many hours.
|
|
|
Cute, that is the single in the back row: Two mini single connected together with a water block The dual waterblock unit is 2 FPGA's sandwiched together,not ASIC's.The one with the black"clamp" thing on it may be an ASIC,can't see from this angle. God,I hope they ship soon For those that don't know, the image is a screen grab from the, Butterfly Labs Company Video http://www.youtube.com/watch?v=tSu5Yyc1bEMI see my comment and many others got deleted. Stuff like "box shifting", "people sitting around playing minecraft", "just a load of people moving boxes and sitting on offices", "9 months already", "video didn't show anyone using a solder iron or reflow unit", "at least we know the laser etching works" etc.
|
|
|
It stops mining around every 15 hrs, Place an electrical timer on the power plug to force it to switch off/on after 15 hrs.
|
|
|
Heat pipes should be hot, that's their purpose to move heat away from the chip, what temperature is the card reporting? I sometimes wonder if people will write code to steal a fraction of someone's hashing power. You can break a card by not letting it go through it's cooling cycle but it would probably be totally dead. Check you have crossfire disabled sometimes this slows a card down.
|
|
|
Proves nothing because you're hiding the delivery name and address so the assets many not even belong to the LTD company but directly to Emmanuel Abiodun.
Not true. Out terms and conditions actually specify that for indefinite contract holders, the device belongs to the contract holders (our clients). We merely charge a maintenance fee. These are handled by the legal terms not a PO. I handle the orders so specify my name as a contact. A LTD Company is a legal person so all orders should be in a bold type name like "COMPANY NAME LTD" or you're breaking the law. A LTD Company cannot offer to sell it's shares to the public, or your breaking the law. For a LTD to sell financial contracts, issue e-money or shares of anything, you need to register with http://www.fca.org.uk or you're breaking the law. Even MtGox cannot get a bank account in the UK. They take regulations seriously here.
|
|
|
|