No Confirmations, no transaction? | Bitcointalksearch.org

shorena

copper member

Activity: 1498

Merit: 1499

No I dont escrow anymore.

Quote from: TigerMart on March 01, 2016, 08:32:27 AM

Quote from: Knabber on March 01, 2016, 05:11:06 AM

i would doublespend, but i never did this before and i read several threads about it.. seems not to be a perfectly safe way if you mess around the wrong way.. As yóu might already know: I'm no genius on this topic

If i double spent or receive the btc back is the same to me at this moment; i just want a safe way to get my disappeared btc back somehow..

You can not double spend all the inputs of your current Tx, because one of them has already been double spent...

Original: 9731f6c3450a993c637fb8c6b4e4c921e1d8ae038bade05cc982031b2bda9473

Double Spend: 2fa79356561ab63afc0b8b92d3877070fbfac073ede941d3e54c42651b795cf4 (has 6+ confirmation)

It seems, your bitcoin QT was not up to date and hence it tried to spend some unconfirmed output which are already spent. That is why the problem. As a wallet, QT has always seem to be unreliable to me (because it relies on so many factors to work perfectly) and that is what has been proven to be true once again.

Yes, bitcoin core spends unconfirmed change, there is a setting to disable it if you dont like that behavior.

It can however not be "out of date" unless you explicitly force that state via command line (e.g. with -zapwallettxes). If you force such a state you can only force it for unconfirmed transactions, not for confirmed ones.

Im not sure what you mean with "so many factors to work perfectly".

TigerMart

full member

Activity: 271

Merit: 117

Quote from: Knabber on March 01, 2016, 05:11:06 AM

i would doublespend, but i never did this before and i read several threads about it.. seems not to be a perfectly safe way if you mess around the wrong way.. As yóu might already know: I'm no genius on this topic

If i double spent or receive the btc back is the same to me at this moment; i just want a safe way to get my disappeared btc back somehow..

You can not double spend all the inputs of your current Tx, because one of them has already been double spent...

Original: 9731f6c3450a993c637fb8c6b4e4c921e1d8ae038bade05cc982031b2bda9473

Double Spend: 2fa79356561ab63afc0b8b92d3877070fbfac073ede941d3e54c42651b795cf4 (has 6+ confirmation)

It seems, your bitcoin QT was not up to date and hence it tried to spend some unconfirmed output which are already spent. That is why the problem. As a wallet, QT has always seem to be unreliable to me (because it relies on so many factors to work perfectly) and that is what has been proven to be true once again.

shorena

copper member

Activity: 1498

Merit: 1499

No I dont escrow anymore.

Quote from: Knabber on March 01, 2016, 05:11:06 AM

allright..

fact is: There are, after -rescan and -zapwallettxes,loading the complete blockchain again and so on, no btc in my wallet.. I guess my transaction is therefore not forgotten and cancelled by mempool.

Does it still show in the list of transactions? Did you update the a version that is no longer called "qt"? -zapwallettxes will not exist in <0.9 versions AFAIK.

Quote from: Knabber on March 01, 2016, 05:11:06 AM

i would doublespend, but i never did this before and i read several threads about it.. seems not to be a perfectly safe way if you mess around the wrong way.. As yóu might already know: I'm no genius on this topic

If i double spent or receive the btc back is the same to me at this moment; i just want a safe way to get my disappeared btc back somehow..

edit: yeah, i learned now.. I payed a fee of 0.0001, will never ever go again with a fee lower than 0.01.. This whole thing i ruining my nerves so hard and isn't worth 1 or 2 bucks

edit: I found this "ERROR: CTxMemPool::accept() : nonstandard transaction type" like a thousand times in my debug window... should this mean the mempool declined my tx or accepted it?

I really hope someone understands what happened here and could help me out

The error has nothing to do with your transaction, its about transactions of others. Bitcoin core (again, newer versions) is good at estimating fees, 0.01 will almost always be too much.

Knabber

newbie

Activity: 10

Merit: 0

allright..

fact is: There are, after -rescan and -zapwallettxes,loading the complete blockchain again and so on, no btc in my wallet.. I guess my transaction is therefore not forgotten and cancelled by mempool.
i would doublespend, but i never did this before and i read several threads about it.. seems not to be a perfectly safe way if you mess around the wrong way.. As yóu might already know: I'm no genius on this topic

If i double spent or receive the btc back is the same to me at this moment; i just want a safe way to get my disappeared btc back somehow..

edit: yeah, i learned now.. I payed a fee of 0.0001, will never ever go again with a fee lower than 0.01.. This whole thing i ruining my nerves so hard and isn't worth 1 or 2 bucks

edit: I found this "ERROR: CTxMemPool::accept() : nonstandard transaction type" like a thousand times in my debug window... should this mean the mempool declined my tx or accepted it?

I really hope someone understands what happened here and could help me out

shorena

copper member

Activity: 1498

Merit: 1499

No I dont escrow anymore.

What exactly is the goal here? Double spend the original TX or keep sending it?

It looks like the network pretty much forgot about your TX, so either is easily possible. -zapwallettxes removes unconfirmed TX from your wallet. Im not entirely sure what you mean with "I already used... -zapwallettxed". If you did you can just create a new TX.

Quote from: mocacinno on February 29, 2016, 10:09:56 AM

Quote from: Knabber on February 29, 2016, 10:03:38 AM

so I'm at hour 76 now..

@TigerMart: this perfectly looks like my transaction.. this is my only transaction for about 1 week..

any ideas how to solve?
I already used -rescan, -zapwallettx etc.. desperate here -.-

I'm not an expert (just learning the technical aspect myself) but maybe you could:
- search witch addresses contain coins
- dumpprivkey
- close the wallet, don't open it again
- wait untill the network forgets about your transaction
- sweep the private keys directly into blockchain (since you seem to want to use an online wallet).

(-maybe you can import the keys into electrum, and create a double spend with a higher fee?)

As i said before: i'm no expert... Maybe Shorena or somebody else with loads of knowledge can confirm/deny this method?

I'd personally never use an online wallet to hold 0.9BTC, but each to his own.

If OP wants to replace the original TX and use an online wallet this is sound advice. I would however keep the key in core and just remove the TX with zapwallettxes.

TigerMart

full member

Activity: 271

Merit: 117

Quote from: Knabber on February 29, 2016, 10:03:38 AM

so I'm at hour 76 now..

@TigerMart: this perfectly looks like my transaction.. this is my only transaction for about 1 week..

any ideas how to solve?
I already used -rescan, -zapwallettx etc.. desperate here -.-

This is what your Tx skeleton looks like...

Code:

{
  "block_height": -1,
  "block_index": -1,
  "hash": "2fec578241e93c47f3495ddf41cafb8f91b561af297b8414ecb23e8afb408f72",
  "hex": "0100000006db81c19aac87acabe6c2515e3b4bd6d6f6217974fc9c6be32726eaade9b5578d000000006a473044022023a7d1f6da68d8362d7051c2a53dfd629592bb109bbf631184a25b5d3a55701c022021e9aeba9f1134e1b7cd19cac68ed7820064c431ceabe18b11538fc0a160d889012103b1a45b3e9c6516e487cf4adf4892e02f51db5456d220ec205151c7b06b876e32ffffffffe148e02b099e2016f783afcb7df4dbd6e42cc483bb6438475d0e16a71e3f89c7010000006b48304502204814c9c6a36cb111671f9fdce510822eafbc1b9cbfb409632f9c5a4206924588022100ecae424a7da16849ce37534dd9dce54e60a019eef2482180351d4ce028c332f90121036b9e8578b2ad61d94ea2d5d9c9b54f4622b7fa4cc62fb32b94e83597492ddeb7ffffffff3158137aec3b559c2d0a5ca4558c9150d010976ec8c2d5f67f25642a39e0e4e7000000006c493046022100a35be96e6824c4b8c3dad4c0d443c657a433d32b15edaf5b95f323bd7f5adcc6022100f357b37f2c44f6ea23492655411b049d57679926236b391ec520fb234e6093eb012103edc245b9999917a00030c1a471a04e51d6cc8488a266f118e527850d4ef4182affffffff7394da2b1b0382c95ce0ad8b03aed8e121c9e4b4c6b87f633c990a45c3f63197000000006a47304402203bb9dbf7cb31b96ddc11618193db9b9407fd600b8741761b660ded8ed765e2ae0220150620d106de9c06c3034937d26a19ba443d2996284417b1ca58ab6805b9a541012103616b6d63f7d6bf58f24cd24ecba424ec10d18b68cd1e5ff3291299ae139d146affffffffa7f3761a9a155112ab0394be451672befc8e289ad7620e47cc8e3a28a447590b000000006b48304502204a383d4205d81cd338a732163615fce1626935bb2d6c33ce28dab31161d61212022100910db627133e02805d02dfa1de839d2874744af6875e4a79fdf9b40874c5e6c4012103217674379355354b4616fb21558463728931e1ef593001e8f13ee3ba35245462fffffffff45c791b65424ce5d341e9ed73c0fafb707087d3928b0bfc3ab61a565693a72f000000006c49304602210091dc111872188ef0a97e15ae1e27f8cd34ecb6242124632a8d49423b96e301df022100829b63736b806ae0b5db1d9fa35067ba1990f471bc5420361a359869178885d0012103616b6d63f7d6bf58f24cd24ecba424ec10d18b68cd1e5ff3291299ae139d146affffffff026b860000000000001976a9142ff32a7c8afe064dcb700e3cf3e2fcc89f15aab188ac009a6f05000000001976a914b456ddf061a3881e42df7fb1180f2e376671a60088ac00000000",
  "addresses": [
    "142GpK3kbfdeccFUp8cSRGMKm9Rk6SkdtH",
    "15NY4V2v2ikx9umNwt55F4LbKwEpWrQqhS",
    "17xCC21F3JKXby4kZwBw55tLf2e5txNQn1",
    "19XwJGc16pU7VPRp7DmMK34jzFg7nsvSSN",
    "1G9JRPiDZSj24VbLUMbMLfc5oepse6AM2E",
    "1Ge1piX9doo1xJcRA7jDivvJTpF2C12GzB",
    "1HSYh9kgXsoG4gbiNU98hPKNBNQ9agaday"
  ],
  "total": 91234411,
  "fees": 0,
  "size": 966,
  "preference": "low",
  "relayed_by": "5.28.126.216:8333",
  "received": "2016-02-26T20:06:26.07Z",
  "ver": 1,
  "lock_time": 0,
  "double_spend": false,
  "vin_sz": 6,
  "vout_sz": 2,
  "confirmations": 0,
  "inputs": [
    {
      "prev_hash": "8d57b5e9adea2627e36b9cfc747921f6d6d64b3b5e51c2e6abac87ac9ac181db",
      "output_index": 0,
      "script": "473044022023a7d1f6da68d8362d7051c2a53dfd629592bb109bbf631184a25b5d3a55701c022021e9aeba9f1134e1b7cd19cac68ed7820064c431ceabe18b11538fc0a160d889012103b1a45b3e9c6516e487cf4adf4892e02f51db5456d220ec205151c7b06b876e32",
      "output_value": 0,
      "sequence": 4294967295,
      "script_type": "empty",
      "age": 0
    },
    {
      "prev_hash": "c7893f1ea7160e5d473864bb83c42ce4d6dbf47dcbaf83f716209e092be048e1",
      "output_index": 1,
      "script": "48304502204814c9c6a36cb111671f9fdce510822eafbc1b9cbfb409632f9c5a4206924588022100ecae424a7da16849ce37534dd9dce54e60a019eef2482180351d4ce028c332f90121036b9e8578b2ad61d94ea2d5d9c9b54f4622b7fa4cc62fb32b94e83597492ddeb7",
      "output_value": 0,
      "sequence": 4294967295,
      "script_type": "empty",
      "age": 0
    },
    {
      "prev_hash": "e7e4e0392a64257ff6d5c2c86e9710d050918c55a45c0a2d9c553bec7a135831",
      "output_index": 0,
      "script": "493046022100a35be96e6824c4b8c3dad4c0d443c657a433d32b15edaf5b95f323bd7f5adcc6022100f357b37f2c44f6ea23492655411b049d57679926236b391ec520fb234e6093eb012103edc245b9999917a00030c1a471a04e51d6cc8488a266f118e527850d4ef4182a",
      "output_value": 0,
      "sequence": 4294967295,
      "script_type": "empty",
      "age": 0
    },
    {
      "prev_hash": "9731f6c3450a993c637fb8c6b4e4c921e1d8ae038bade05cc982031b2bda9473",
      "output_index": 0,
      "script": "47304402203bb9dbf7cb31b96ddc11618193db9b9407fd600b8741761b660ded8ed765e2ae0220150620d106de9c06c3034937d26a19ba443d2996284417b1ca58ab6805b9a541012103616b6d63f7d6bf58f24cd24ecba424ec10d18b68cd1e5ff3291299ae139d146a",
      "output_value": 0,
      "sequence": 4294967295,
      "script_type": "empty",
      "age": 0
    },
    {
      "prev_hash": "0b5947a4283a8ecc470e62d79a288efcbe721645be9403ab1251159a1a76f3a7",
      "output_index": 0,
      "script": "48304502204a383d4205d81cd338a732163615fce1626935bb2d6c33ce28dab31161d61212022100910db627133e02805d02dfa1de839d2874744af6875e4a79fdf9b40874c5e6c4012103217674379355354b4616fb21558463728931e1ef593001e8f13ee3ba35245462",
      "output_value": 0,
      "sequence": 4294967295,
      "script_type": "empty",
      "age": 0
    },
    {
      "prev_hash": "2fa79356561ab63afc0b8b92d3877070fbfac073ede941d3e54c42651b795cf4",
      "output_index": 0,
      "script": "49304602210091dc111872188ef0a97e15ae1e27f8cd34ecb6242124632a8d49423b96e301df022100829b63736b806ae0b5db1d9fa35067ba1990f471bc5420361a359869178885d0012103616b6d63f7d6bf58f24cd24ecba424ec10d18b68cd1e5ff3291299ae139d146a",
      "output_value": 0,
      "sequence": 4294967295,
      "script_type": "empty",
      "age": 0
    }
  ],
  "outputs": [
    {
      "value": 34411,
      "script": "76a9142ff32a7c8afe064dcb700e3cf3e2fcc89f15aab188ac",
      "addresses": [
        "15NY4V2v2ikx9umNwt55F4LbKwEpWrQqhS"
      ],
      "script_type": "pay-to-pubkey-hash"
    },
    {
      "value": 91200000,
      "script": "76a914b456ddf061a3881e42df7fb1180f2e376671a60088ac",
      "addresses": [
        "1HSYh9kgXsoG4gbiNU98hPKNBNQ9agaday"
      ],
      "script_type": "pay-to-pubkey-hash"
    }
  ]
}

Re-spend the Tx inputs with some mining fee. I never use bitcoin QT. Hence, no idea how to use it. Services like coinb.in may come handy to decipher these issues.

mocacinno

legendary

Activity: 3402

Merit: 5004

https://merel.mobi => buy facemasks with BTC/LTC

Quote from: Knabber on February 29, 2016, 10:03:38 AM

so I'm at hour 76 now..

@TigerMart: this perfectly looks like my transaction.. this is my only transaction for about 1 week..

any ideas how to solve?
I already used -rescan, -zapwallettx etc.. desperate here -.-

I'm not an expert (just learning the technical aspect myself) but maybe you could:
- search witch addresses contain coins
- dumpprivkey
- close the wallet, don't open it again
- wait untill the network forgets about your transaction
- sweep the private keys directly into blockchain (since you seem to want to use an online wallet).

(-maybe you can import the keys into electrum, and create a double spend with a higher fee?)

As i said before: i'm no expert... Maybe Shorena or somebody else with loads of knowledge can confirm/deny this method?

I'd personally never use an online wallet to hold 0.9BTC, but each to his own.

Knabber

newbie

Activity: 10

Merit: 0

so I'm at hour 76 now..

@TigerMart: this perfectly looks like my transaction.. this is my only transaction for about 1 week..

any ideas how to solve?
I already used -rescan, -zapwallettx etc.. desperate here -.-

TigerMart

full member

Activity: 271

Merit: 117

Quote from: Knabber on February 28, 2016, 10:30:09 AM

TX-ID (2fec578241e93c47f3495ddf41cafb8f91b561af297b8414ecb23e8afb408f72).. blockchain.info --> Sorry we could not find any blocks or transactions matching this hash

Your Tx is confusing. It seems, you have already spent the inputs of this Tx in some other Tx. But, it is still available in some mempools.

https://live.blockcypher.com/btc/tx/2fec578241e93c47f3495ddf41cafb8f91b561af297b8414ecb23e8afb408f72/

shorena

copper member

Activity: 1498

Merit: 1499

No I dont escrow anymore.

Quote from: Knabber on February 28, 2016, 12:39:49 PM

I'm very sorry if it seems so; i'm seriously confused right now and have a very silly question:

where to find sending adress?

edit: part of the btc lost i received via

17xCC21F3JKXby4kZwBw55tLf2e5txNQn1

QT/core does not just forget about a transaction, you have to tell it to do so.

#1 close core/qt (if you are still on "qt" you should update to 0.12 btw)
#2 make sure its fully closed
#3 start with -zapwallettxes, e.g. on windows you:
#3.1 hit win+r (to open run)
#3.2 enter: c:\Program Files\Bitcoin\bitcoin-qt.exe -zapwallettxes (modify path if needed) and confirm with ok
#4 let core do its thing, it might take a few minutes to a few hours depending on your overal system speed (CPU, disk mainly)

--Encrypted--

copper member

Activity: 924

Merit: 1007

hee-ho.

I have no idea how to get the address in core if you don't remember it. you can try updating your qt to 0.12 and copy the raw transaction instead (right-click on tx and copy raw tx.).

Knabber

newbie

Activity: 10

Merit: 0

I'm very sorry if it seems so; i'm seriously confused right now and have a very silly question:

where to find sending adress?

edit: part of the btc lost i received via

17xCC21F3JKXby4kZwBw55tLf2e5txNQn1

--Encrypted--

copper member

Activity: 924

Merit: 1007

hee-ho.

maybe you should post it here. I'm starting to suspect that you're just trolling. really very sorry if you're not.

Mickeyb

hero member

Activity: 798

Merit: 1000

Move On !!!!!!

Quote from: Knabber on February 28, 2016, 12:01:58 PM

Quote from: --Encrypted-- on February 28, 2016, 11:50:00 AM

well what's the sending address? check that address and see if it still have the bitcoins. if the bitcoins is still there get the private key and just import it to your blockchain wallet. you can spend it to another address then.

the sending adress is blank, not btc there.. this is what was freaking me out Wink

but i guess if its stuck somewhere in the mempool, somewhen the transactian will be cancelled and i get my btc back to the sender add.

Well can you post the address you sent the BTC from, publicly for tracking purposes?

Knabber

newbie

Activity: 10

Merit: 0

Quote from: --Encrypted-- on February 28, 2016, 11:50:00 AM

well what's the sending address? check that address and see if it still have the bitcoins. if the bitcoins is still there get the private key and just import it to your blockchain wallet. you can spend it to another address then.

the sending adress is blank, not btc there.. this is what was freaking me out Wink

but i guess if its stuck somewhere in the mempool, somewhen the transactian will be cancelled and i get my btc back to the sender add.

--Encrypted--

copper member

Activity: 924

Merit: 1007

hee-ho.

well what's the sending address? check that address and see if it still have the bitcoins. if the bitcoins is still there get the private key and just import it to some other wallet (I think your old wallet have issues. create a new one and update your core.). you can spend it to another address then.

Knabber

newbie

Activity: 10

Merit: 0

Quote from: Mickeyb on February 28, 2016, 11:06:38 AM

Quote from: Knabber on February 28, 2016, 11:00:55 AM

allright.. i just hope my btc didn't vanish..

BTCs don't vanish Wink

. Best thing is to keep waiting for at least another week, you should get it back. What is the address you sent it from(do add the one you sent it to as well) anyway?

receiver: 1HSYh9kgXsoG4gbiNU98hPKNBNQ9agaday

trinaldao

copper member

Activity: 1218

Merit: 1007

Post your ann & bounty just contact me

trying use blocktrail but still not found
Search by tx failed
2fec578241e93c47f3495ddf41cafb8f91b561af297b8414ecb23e8afb408f72

i think your transaction will be reject from blockchain and your bitcoin will be back to your wallet

Mickeyb

hero member

Activity: 798

Merit: 1000

Move On !!!!!!

Quote from: Knabber on February 28, 2016, 11:00:55 AM

allright.. i just hope my btc didn't vanish..

BTCs don't vanish Wink

. Best thing is to keep waiting for at least another week, you should get it back. What is the address you sent it from(do add the one you sent it to as well) anyway?

Knabber

newbie

Activity: 10

Merit: 0

yeah, gave that a shot like 12h ago.
allright.. i just hope my btc didn't vanish..

Thank you guys, i just have to be patiant i guess

Topic: No Confirmations, no transaction? (Read 1388 times)