I tried opening my wallet.dat file without having qt client running, but when I browse the files to open it with the qt client it doesnt add it to the list of programs to use.
you can't open bitcoin wallets as a file. you must place it in bitcoin-qt's data directory. For the OS-specific file location to "restore" your wallet backup, see: https://en.bitcoin.it/wiki/Securing_your_walletHint: %appdata%\BitcoinIf Bitcoin doesn't have a wallet.dat in it's data directory when it starts, it will create a new blank one. |
|
|
|
The above doesn't solve the problem. You need to remove the unconfirmed transactions from your Bitcoin-qt wallet.dat, and then -rescan for payments. You wallet balance will then reflect the correct balance. 1. Install python 2.7.5: http://www.python.org/download/2. Install python-twisted package and python-zope packages: http://www.lfd.uci.edu/~gohlke/pythonlibs/#twisted - you must get versions compatible with 2.7 and your 32/64 bit version of python you installed. 3. Get the pywallet script: https://raw.github.com/jackjack-jj/pywallet/master/pywallet.py - save it to a known location on your computer. 4. Completely close Bitcoin, verify it is not running in task manager. 5. Back up your wallet.dat: file https://en.bitcoin.it/wiki/Securing_your_walletThen run pywallet with a command line that starts the web interface: pywallet.py --webnow: 1. Go to http://localhost:8989 in your browser to access your pywallet web server 2. Go to the Delete tab 3. fill in the wallet directory and filename. Type "all" into the keys box, and leave the transaction radio button checked. 4. Press delete, all transactions that are cached in your wallet.dat are removed. 5. You can close the web browser and pywallet after this is completed. Now, run bitcoin-qt -rescan and let it search the blockchain for all valid transactions and payments to you, you will now have a correct balance and no unconfirmed transactions. |
|
|
|
If I had a dollar for every time I have emailed that site and been ignored....................
If I had a dollar every time I emailed and got a response, I would have one dollar, because I only sent one email and got a response. Maybe you should cut back on your emailing. |
|
|
|
Looks like it's an identical repeat of this: Provider (Hetzner) messed the routing up. I couldn't even reach the server and the support didn't understand the problem ("Ping works fine so your server is up").
The site you saw seems to be served from 176.9.79.205 while bitcoincharts.com is 176.9.79.196.
I've PM'd tcatm, since obvously emailing @bitcoincharts will be futile. |
|
|
|
|
My guess would be that someone restored the parallels image on your-server.de that belongs on 176.9.79.205 (mail.pfaffender.net) to 176.9.79.196 (bitcoinwatch & bitcoincharts), or is routing the ip to the wrong vm. Dumb admin or such; the dns & domain info doesn't appear hijacked.
|
|
|
|
|
Look at your government currency page, it also has fees being removed from your account.
|
|
|
|
...and 6 days ago It would be about 10 seconds for an admin to add html to that page <p>Avatar changes temporarily disabled</p> and save this confusion... |
|
|
|
Don't trust research that comes with tweets from the authors "Immediate action required" "You heard it here first: now is a good time to sell your Bitcoins". https://twitter.com/el33th4xorNews reports are doing 0 research; "A major flaw that has gone unrealized until now" is just a plain lie. |
|
|
|
|
I've continued to plug around with some code features, but nothing that is worth sending over to the build machine.
- precision option other than 2 creates separate scid files with a suffix (like mtgoxUSD_p4.scid), so experimenting with this option doesn't screw up your data,
- max precision 5, as historic mtgox trades > 4294.9 will overflow precision 6 and higher,
- verbose option dumps individual history trades to console (slow); console presentation fixes,
- "max_time" option, won't write live stream or history after this epoch timestamp to scid (for creating accurate shareable files; the transition from downloading history to live stream may miss some trades). So I don't have to maintain a modded .py to do this.
|
|
|
|
Would increasing the fee and pushing it again help?
No. This blocking rule is about the creation and sending of dust that is completely worthless to the recipient, dust that is more expensive to spend out of a wallet than to discard. They are now considered non-standard transactions, and will not be accepted into the transaction memory pool. History: Bitcoin didn't anticipate that people would pay fees to spam the blockchain - we required a fee for anything below .01, and if you have a profit model you can pay that...
Payments need to be self-funding, that the recipient will have a net gain by receiving the payment after including retransmittal costs.
So then what is the definition of not making "economic sense to spend"?... I would say it is a payment that as an input, when evaluated by minimum fee rules in aggregate with like inputs, would cost more to send in fees than the value of the payment. This is a payment likely to become an unspent TXO - for most it is cheaper to discard than to spend.
1 input: 257-259 bytes = minimum payment .00050001
2 inputs: 436-439 bytes = minimum payment .00025001
5 inputs: 976-980 bytes = minimum payment .00010001
6 inputs: 1157-9 bytes = minimum payment .00016668
8 inputs: 1514 bytes = minimum payment 0.00012501
39 inputs: 5848 bytes = minimum payment 0.00008975
So it looks like a good "receiving this payment will cost the recipient" threshold is any output that is less than 1/5 of minimum fee, from the examples, 20%-40% of minimum fee should be required.
The amount decided on was if the payment was three times smaller than the minimum fee. The final formula for exactly what is useless dust spam ends up being dependent on the construction of the particular sending transaction: IsDust = TxOutAmount < 3 * MinRelayFeePerKB / 1000 * (TxOutBytes + 148) https://github.com/bitcoin/bitcoin/pull/2577Bitcoin design has the ability to recover hard drive space by pruning spent transactions. What you have created here is a transaction, that if a single recipient decides they can't spend their dust, has to be retained on every network node's hard drive forever. This wouldn't be the first transaction in two days that blockchain.info has sent that is doomed. |
|
|
|
|
My toes are warm from all the sockpuppets posting useless crap here.
|
|
|
|
Am I doing it right?  |
|
|
|
I have multiple wallet.dat files. How can I switch between them?
I would recommend that you consolidate by sending all bitcoins to addresses in one wallet. It is too tedious and there is too much danger of doing something wrong if you were to continue renaming wallet.dat files to use multiple wallets on one computer. This post details the steps just to move money to a fresh wallet on one computer. If you have addresses in a secondary wallet that may continue to receive payments in the future, you can export the private key and import the address into the main wallet. One alternative is to use multiple operating system logins. The Bitcoin data directory is a user directory, different user logins get a different directory. This will create multiple copies of the blockchain for each user though; you'll be updating the blockchain twice. (mod: split thread) |
|
|
|
|
To answer the actual question that is being asked:
Bitcoin-qt: File->Backup Wallet. Save the file to a removable backup media such as flash drive or burn to CD.
Don't forget an encrypted wallet's password, if needed you can write it down with the wallet if it is going to be secured in a safe. Forgetting the password used to encrypt a wallet will lose you your bitcoins too, so even if you think it memorable, a backup of the password will protect against brain failure.
To restore the wallet on a new computer, the wallet.dat file simply needs to be placed in the Bitcoin data directory before running Bitcoin.
|
|
|
|
However when i checked blockchain.info There's your problem. Don't look at that site. |
|
|
|
|
Maybe miners have increased the value of what they consider spam transactions themselves. BTC amounts:
0.00005450
0.00005450
0.00005500
0.00005500
0.00005550
0.00005550
0.00005550
0.00005600
0.00005650
0.00005650
0.00005650
0.00005650
0.00005650
0.00005700
0.00005700
0.00005750
0.00005750
0.00005750
0.00005750
0.00005850
0.00005900
0.00005935
0.00005950
0.00005950
0.00006050
0.00006300
0.00006300
0.00006400
0.00006500
0.00006500
0.00006550
0.00006600
0.00006800
0.00006805
0.00006850
0.00007000
0.00007000
0.00007300
0.00007750
|
|
|
|
|
The basic issue with this transaction is it didn't pay the minimum fees. This transaction activated every spam prevention feature there is:
1. The transaction was 34235 bytes; the fee is 0.0001 BTC per kB (not KiB) but this transaction paid 34x, not 35x minfee. Transactions with less than the minimum are considered the same as zero-fee by Bitcoin. They are not relayed across the Bitcoin network.
2. If free transactions make it to a miner, default Bitcoin has a small area of a block for including some free transactions if block is less than 27kB when received. This transaction is bigger than the whole free area - only transactions under 10kB in size are even considered.
3. The priority (based on total weighted coin age by value) was too low to be considered for any fee-free inclusion. This transaction was a whole bunch of dust, plus 25 BTC; the 25BTC had just recently been received by the wallet. If the contents of the wallet had been allowed to age for a few days, they likely could have been sent for free.
Blockchain.info is mostly at fault, they shouldn't let users do stupid things, and should calculate (and enforce) the exact minimum fee Bitcoin-qt would use. It also helps if users don't spam up their own wallets with dust.
Bitcoin doesn't easily allow web applications to figure out what the correct/current fee is; it needs an RPC feature I will call "sendtoaddressfee", where bitcoin txouts are not spent, but reserved, and the fee amount is returned. When the same bitcoin amount is actually spent, the transaction is constructed from the reserved bitcoins txouts; any other transaction besides the original clears the reservation.
|
|
|
|
|
You mean guess which company used a merchant service as an exchange to pay itself USD from it's "QA"-mined and pre-order Bitcoin hoard?
|
|
|
|
|
Show Posts
