https://www.regjeringen.no/no/sok/id86008/?term=bitcoins- Enkelte har opplevd usikkerhet knyttet til den avgiftsmessige behandlingen av bitcoin. Jeg er svært fornøyd med at det nå har kommet en avklaring på dette spørsmålet. Dette ivaretar hensynet til likebehandling og forutberegnelighet, sier finansminister
|
|
|
|
or contact a mining pool and offer to pay them to confirm it for you.
there are online services work? Use -zapwallettxes I know, but I need to complete this transaction Use -zapwallettxes and complete the transaction. By the way, that site you have linked is dangerous, something virus or malware. |
|
|
|
or contact a mining pool and offer to pay them to confirm it for you.
there are online services work? Use -zapwallettxes |
|
|
|
|
Dear DannyHamilton,
Just to be sure, I start the Bitcoin Core like this: "C:\Program Files\Bitcoin\bitcoin-qt.exe" -zapwallettxes
Thank you very much for all advices. Problem solved. BTC back to my wallet minus the fee.
|
|
|
|
|
"Create a backup of your wallet before you do ANYTHING else. Store that backup in a safe place. If you do not have a good backup of your wallet, YOU SHOULD NOT BE USING YOUR WALLET AT ALL!
"
I have a copy/backup from November 6.
"Other options are to remove the transaction from your wallet and re-send it with a higher fee, or contact a mining pool and offer to pay them to confirm it for you."
Problem, it's not possible to remove the transaksjon from wallet, as I told before.
|
|
|
|
Always rebroadcast, so maybe I should only wait?
You have waited 3 months, the fee is simply too low. Backup your wallet.dat, then zap it. Not 3 months. It was sent December 8. This is the Blockchain info today December 16: Transactions No. Transactions 305 Total Received 102.36899048 BTC Final Balance 0.00141177 BTC |
|
|
|
It won't destroy your wallet. It will delete all of your transaction and do a rescan (your confirmed transactions will show up again after rescan). Unless you get rid of that transaction bitcoin core will keep rebroadcasting it until it gets confirmed.
2016-12-16 11:20:05 ResendWalletTransactions: rebroadcast 1 unconfirmed transactions 2016-12-16 12:06:48 ResendWalletTransactions: rebroadcast 1 unconfirmed transactions 2016-12-16 12:27:15 ResendWalletTransactions: rebroadcast 1 unconfirmed transactions 2016-12-16 12:56:27 ResendWalletTransactions: rebroadcast 1 unconfirmed transactions 2016-12-16 13:16:29 ResendWalletTransactions: rebroadcast 1 unconfirmed transactions 2016-12-16 15:21:54 ResendWalletTransactions: rebroadcast 1 unconfirmed transactions Always rebroadcast, so maybe I should only wait? |
|
|
|
Right click on the transaction and choose abandon transaction or start core with -zapwallettxes (instructions on how to do it here). The bitcoins will return to your wallet and you'll be able to resend. Don't work. "Abandon transaction" is grey. Second method then. Use zapwallettxes. I don't get why abandon transactions never works.I'm afraid to use that. Maybe it will destroy the wallet. This is the Blockchain info: Transactions No. Transactions 305 Total Received 102.36899048 BTC Final Balance 0.00141177 BTC The final Balance shows the amount minus the fee 0.00000339 BTC So why is the system still keeping it and don't send it back to wallet? |
|
|
|
Right click on the transaction and choose abandon transaction or start core with -zapwallettxes (instructions on how to do it here). The bitcoins will return to your wallet and you'll be able to resend. Don't work. "Abandon transaction" is grey. |
|
|
|
|
Sent low amount btc, 0.0014. fee 0.00001, September 8. Still unconfirmed.
Something I can do to resend?
Status: 0/unconfirmed, in memory pool
Date: 08.12.2016 21:15
To: 18DFG8EWgwWCLxh6To8BLaqQvUvfUU4KFg
Debit: -0.00140838 BTC
Transaction fee: -0.00000339 BTC
Net amount: -0.00141177 BTC
Transaction ID: d8ed4644c31d868cae533c63c85b40f3ae3bdc2cca0c24b258f83b909ca03266
Output index: 0
Think the fee is to small.?
December 15: Shows Final Balance 0.00141177 BTC i Blockchain. No unconfirmed transaction, men viser Transaction rejected by our node. Reason: Fee is too low. Minimum fee is 1.5 satoshi / B. Is: 1.0.
Will it come back to my wallet, or? Anyone knows?
Using Bitcoin Core versjon v0.13.1 (64-bit)
|
|
|
|
Nå er det skjedd noe. Kunne ikke finne transaksjonen lenger, men søkte på id: Transaction rejected by our node. Reason: Fee is too low. Minimum fee is 1.5 satoshi / B. Is: 1.0.
Vet ikke om beløpet bare er forsvunnet. Det er ikke kommet noe til wallet.
Hmm... Nå er unconfirmed transaction tilbake igjen. Viser Final Balance 0.00141177 BTC i Blockchain. Ingen unconfirmed transaction, men viser Transaction rejected by our node. Reason: Fee is too low. Minimum fee is 1.5 satoshi / B. Is: 1.0. Vil det komme tilbake til min wallet, eller? Noen som vet? |
|
|
|
Nå er det skjedd noe. Kunne ikke finne transaksjonen lenger, men søkte på id: Transaction rejected by our node. Reason: Fee is too low. Minimum fee is 1.5 satoshi / B. Is: 1.0.
Vet ikke om beløpet bare er forsvunnet. Det er ikke kommet noe til wallet.
Hmm... Nå er unconfirmed transaction tilbake igjen. |
|
|
|
|
Nå er det skjedd noe. Kunne ikke finne transaksjonen lenger, men søkte på id: Transaction rejected by our node. Reason: Fee is too low. Minimum fee is 1.5 satoshi / B. Is: 1.0.
Vet ikke om beløpet bare er forsvunnet. Det er ikke kommet noe til wallet.
|
|
|
|
Har du noen aning om hvor mange dager/uker det kan ta?
Denne kan ta mange månader å få stadfesta. Det er alt for mykje spam om dagen, og alt for få som filtrerer. Ser at transaksjonen ikkje har vekslepengar heller. Då kan du heller ikkje prøve deg med CPFP (child pays for parent). Fordelen er at txfee er sopass låg at mange vil kaste han ut av mempool og akseptere ein ny transaksjon med same inputs og høgare txfee. Kva lommebok brukar du? Jeg bruker Bitcoin Core versjon v0.13.1 (64-bit) Har vanligvis brukt anbefalt gebyr, men det virket som det spiste opp hele det lille beløpet. så jeg satte det til egendefinert 0.00001000 pr, kilobyte. |
|
|
|
Har du noen aning om hvor mange dager/uker det kan ta? |
|
|
|
Sendte et mindre beløp btc, 0.0014, fee 0.00001, den 8. desember. Fortsatt ingen bekreftelser.
Something I can do to resend? Status: 0/unconfirmed, in memory pool Date: 08.12.2016 21:15 To: 18DFG8EWgwWCLxh6To8BLaqQvUvfUU4KFg Debit: -0.00140838 BTC Transaction fee: -0.00000339 BTC Net amount: -0.00141177 BTC Transaction ID: d8ed4644c31d868cae533c63c85b40f3ae3bdc2cca0c24b258f83b909ca03266 Output index: 0 Think the fee is to small.? |
|
|
|
|
Sendte et mindre beløp btc, 0.0014, fee 0.00001, den 8. desember. Fortsatt ingen bekreftelser.
|
|
|
|
I had a similar problem a couple of times. Now I'm using Norton Firewall after a consultant from Norton helped me to make exception, and 0.13.1 running ok.
But after Windows update I got crash like you. I shut down my computer and startet again. Startet bitcoin-qt wallet and after a couple of minuts it was up and go.
Hi usually if bitcoin-qt hangup due to a block corruption, it will work again, as long as it does not attempt to access that block, once that detects the fucked up block it will hangup again, so the only solution is to do a --reindex, which takes a very long time, and my main complain is that why, if it detects a damaged block, it does not redownload it, instead, it forces you to do a full disk reindex which is crazy!. at least with the hyper-mega tip achow101 give me of use the --dbcache=hughememoryusenumber lowered the processing time a lot, but it still takes a long time (and i know my computer is two - three year old machine, i should get at least a 6th gen intel i5 with pci-e M2 SSD, will do as soon as i can get the money for it  that kind of hw is very expensive here in my area ) the other way is to restore from backup, which i can do, i backup the entire blockchain to a 7z file once a month and keep three copies, but i wanted to find another solution to prevent this or solve it quickly. 3weeks behind... almost done!! Here is how it looks for me: 2016-11-11 20:34:20 UpdateTip: new best=000000000000000001542e46acf8bd8901baae7dfa47f44950c48b139c88371a height=438440 version=0x20000000 log2_work=85.529235 tx=169959484 date='2016-11-11 20:15:51' progress=0.999995 cache=126.1MiB(62820tx)
2016-11-11 20:34:21 tor: Thread interrupt
2016-11-11 20:34:21 torcontrol thread exit
2016-11-11 20:34:21 scheduler thread interrupt
2016-11-11 20:34:21 addcon thread interrupt
2016-11-11 20:34:21 net thread interrupt
2016-11-11 20:34:21 opencon thread interrupt
2016-11-11 20:34:21 ProcessMessages: advertising address [2001:0:5ef5:79fd:24ba:1f45:a322:8ce1]:8333
2016-11-11 20:34:21 receive version message: /Satoshi:0.13.1/: version 70014, blocks=438444, us=92.221.115.30:59592, peer=5
2016-11-11 20:34:21 msghand thread interrupt
2016-11-11 20:34:21 Shutdown: In progress...
2016-11-11 20:34:21 StopNode()
2016-11-11 20:34:23 Corruption: block checksum mismatch
2016-11-11 20:34:23 *** System error while flushing: Database corrupted
2016-11-11 20:34:41 Shutdown: done It did'nt reindex. |
|
|
|
|
I had a similar problem a couple of times. Now I'm using Norton Firewall after a consultant from Norton helped me to make exception, and 0.13.1 running ok.
But after Windows update I got crash like you. I shut down my computer and startet again. Startet bitcoin-qt wallet and after a couple of minuts it was up and go.
|
|
|
|
|
Have been ok for some days now, but yesterday it start to fail again. Was away from my computer a couple of hour and when I went back there was an error.
2016-11-12 19:07:24 AdvertiseLocal: advertising address 92.221.115.30:8333
2016-11-12 19:07:27 UpdateTip: new best=0000000000000000010da44e2ec140d1612ce7038e78bb7f756b770f1b7c5cb4 height=438583 version=0x20000000 log2_work=85.53327 tx=170156352 date='2016-11-12 17:07:28' progress=0.999965 cache=90.6MiB(74746tx) warning='1 of last 100 blocks have unexpected version'
2016-11-12 19:07:29 UpdateTip: new best=000000000000000003b0051ac9037f7c1989f965a187656b54dcddd241d47bf4 height=438584 version=0x20000000 log2_work=85.533298 tx=170158138 date='2016-11-12 17:08:01' progress=0.999965 cache=94.0MiB(78528tx) warning='1 of last 100 blocks have unexpected version'
2016-11-12 19:07:29 ProcessMessages: advertising address [2001:0:9d38:6ab8:18ed:237:a322:8ce1]:8333
2016-11-12 19:07:29 receive version message: /Satoshi:0.13.1/: version 70014, blocks=438600, us=92.221.115.30:49189, peer=10
2016-11-12 19:07:29 AdvertiseLocal: advertising address [2001:0:9d38:6ab8:18ed:237:a322:8ce1]:8333
2016-11-12 19:07:30 UpdateTip: new best=0000000000000000025e24e7cf970ed267d1d8fa9dc614850069c7158639954e height=438585 version=0x20000000 log2_work=85.533327 tx=170160224 date='2016-11-12 17:21:28' progress=0.999969 cache=95.9MiB(81524tx) warning='1 of last 100 blocks have unexpected version'
2016-11-12 19:07:30 ProcessMessages: advertising address [2001:0:9d38:6ab8:18ed:237:a322:8ce1]:8333
2016-11-12 19:07:30 receive version message: /Satoshi:0.13.1/: version 70014, blocks=438600, us=92.221.115.30:49207, peer=11
2016-11-12 19:07:30 AdvertiseLocal: advertising address 92.221.115.30:8333
2016-11-12 19:07:31 LevelDB read failure: Corruption: block checksum mismatch
2016-11-12 19:07:31 Corruption: block checksum mismatch
2016-11-12 19:07:54 Error reading from database: Database corrupted
|
|
|
|
|
Show Posts
