restoring and spending bitcoin | Bitcointalksearch.org

ABCbits

legendary

Activity: 2870

Merit: 7490

Crypto Swap Exchange

Quote from: markzenn11 on January 16, 2020, 09:35:15 PM

and then send it again to the same address but it says it cannot be broadcasted immediately.

There are various reason a transaction cannot be broadcasted immediately such as timelock isn't expired yet or the transaction is above maximum chain of unconfirmed change.

Please do it again and copy full message.

Quote from: markzenn11 on January 16, 2020, 09:35:15 PM

i really need your idea guys. what will my bitcoin config file must looks like?

You don't even need to create or modify your bitcoin config file, Bitcoin Core works well without it.

HCP

legendary

Activity: 2086

Merit: 4363

"Missing inputs" means that your transaction is attempting to spend inputs that no longer exist in the UTXO set... AKA actual unspent transaction outputs. Undecided

This is not good news.

It means that the inputs either "never existed" or they have already been spent. In the former case, it's possible that they were the result of an orphaned block, that your wallet never found out about. It's also possible you've loaded a wallet for a different coin (like LTC or DOGE) into Bitcoin Core.

In the latter case, it's possible that someone else has a copy of the wallet and the inputs you're spending have already been spent by someone in another transaction.

Without more details of the addresses involved it's impossible to tell which situation you are in... But in either case, I suspect you are going to be quite disappointed with the realisation that you don't have the coins you think you do. Undecided

markzenn11

full member

Activity: 422

Merit: 102

going back to bitcoin core qt, i used command sendrawtransaction and ive got the message ''Missing inputs (code -25)''. i then go to rpc and tried myusername@bitcoin:~$ deriveaddresses "wpkh([7a0282b8/84h/0h/0h]0........... maybe this will fix my wallet. what else could i possibly do to have successful transactions?

it's been 4 days since the command deriveaddresses.... and it's not done yet, there are approximately 56000 addresses in that wallet alone.

HCP

legendary

Activity: 2086

Merit: 4363

Quote from: ?? on ??

The ubuntu method might work but you should also send a mail to [suspicious email address redacted], a recovery firm that specializes in all types of cryptocurrency retrievals without payment of any upfronts.

I would not trust some "no history" newbie shilling a "recovery" site. That site looks very dodgy... I especially like the way they have a UK address and a North American phone number Huh

Oh... and the premises at "94 Green Lane in Worcester"?

(note, the postcode listed on their website WR65 6YB doesn't actually exist)

Roll Eyes

HCP

legendary

Activity: 2086

Merit: 4363

Quote from: markzenn11 on January 16, 2020, 09:35:15 PM

i really need your idea guys. what will my bitcoin config file must looks like?

Firstly, your bitcoin config will not be causing the issues you are seeing.

Quote from: markzenn11 on January 16, 2020, 09:35:15 PM

back to my node,in debuglog ive seen those old transactions the 400 and .36 btc was still there for relay. i then abandon the .36btc and then send it again to the same address but it says it cannot be broadcasted immediately.

What was the exact error message? Can you screen shot it when you try and create/broadcast the transaction?

Quote

i will try to apply zapwallettxes to config and maybe include mempoolexpiry to clear my wallet. then ill try to send my bitcoins again to my other wallet.

Those items don't need to be applied in the config file to fix your issue.

"zapwallettxes" is just a way to clear the local list of transactions in your wallet file... so that the blockchain can then be re-scanned and only related transactions that are currently on the blockchain or being broadcast/received from other nodes are then re-added. It is useful after you "abandon" a transaction to remove them from your transaction history list etc, if you don't want them to show any longer. Generally you only want to run this as a "one off", to clear the unwanted transactions... so, it probably shouldn't be in your config file, but used as a temporary command line argument when you start the node.

"mempoolexpiry" is not going to solve your problem at all. It is not related to your inability to send the transaction.

markzenn11

full member

Activity: 422

Merit: 102

i installed virtualbox with ubuntu on it in my pc. then i run a pruned node with a replaced wallet.dat file. i also generated a receiving address and send some mbtc on it then sent those in my coinomi phone app. it was very quick,
back to my node,in debuglog ive seen those old transactions the 400 and .36 btc was still there for relay. i then abandon the .36btc and then send it again to the same address but it says it cannot be broadcasted immediately. i will try to apply zapwallettxes to config and maybe include mempoolexpiry to clear my wallet. then ill try to send my bitcoins again to my other wallet.

im very sorry for very late reply from me, setting up everything in my country takes days with 1 to 3 mbps download speed, even weeks and i even tried multiple times like trial and error.
i really need your idea guys. what will my bitcoin config file must looks like?

nc50lc

legendary

Activity: 2618

Merit: 6452

Self-proclaimed Genius

Quote from: markzenn11 on January 06, 2020, 08:08:09 AM

what about dusts btc balances? those 400 bitcoin actually came from about 100 plus addresses. about 80 addresses do have sufficient amount, the rest do have dusts balances.

You seem to be keeping the result from online broadcaster to yourself, was it an error?
Or you didn't because of privacy reasons? FYI, in terms of privacy, it's basically the same as pasting your address to their site.
If you're thinking that they can get your keys, no; or change the output, no, it's impossible without you changing the SIGHASH type which is "all" by default (changing anything will invalidate the signature).
So why don't you try to broadcast it through a blockexplorer instead?

BTW, please don't dodge this question: Did you bought that wallet.dat or was it given to you by a "friend"?
Because the balance is suspiciously identical to those tampered wallets that has been circulating in the internet.

HCP

legendary

Activity: 2086

Merit: 4363

It shouldn't really matter if you're trying to spend dust balances... You'll just pay a lot in fees Tongue

The only time "dust" matters is if you try to send or create a dust UTXO. That's what will generally trigger nodes to refuse your transaction for "dust".

Quote

Transaction total size: 2722 bytes

In any case, I don't think you're spending that many UTXOs... with a transaction size of only 2722 bytes (spending UTXOs from transactions that obviously pre-date SegWit)... you're probably only spending around ~15-18 UTXOs. depending on if you're using compressed or uncompressed keys. So I doubt you're spending from "100 plus addresses". Wink

without the actual transaction details, it's difficult to know why your transaction isn't propagating properly. I had hoped one of the external services might give you a "reason" if you tried to use them instead of simply trying to broadcast from Bitcoin Core/bitcoind yourself.

markzenn11

full member

Activity: 422

Merit: 102

Quote from: HCP on January 06, 2020, 04:57:55 AM

Did you try broadcasting the raw hex using a broadcast tool on an external site like blockcypher or coinb.in? If so, did you get any error messages or did it broadcast successfully? Huh

I'm curious as to why the transaction appears to be "valid", but is not propagating... as mentioned earlier, there must be something "non-standard" about your transaction causing nodes to refuse to relay it... hopefully one of the broadcast tools might give you a clue as to what that "something" might be.

what about dusts btc balances? those 400 bitcoin actually came from about 100 plus addresses. about 80 addresses do have sufficient amount, the rest do have dusts balances.

HCP

legendary

Activity: 2086

Merit: 4363

Did you try broadcasting the raw hex using a broadcast tool on an external site like blockcypher or coinb.in? If so, did you get any error messages or did it broadcast successfully? Huh

I'm curious as to why the transaction appears to be "valid", but is not propagating... as mentioned earlier, there must be something "non-standard" about your transaction causing nodes to refuse to relay it... hopefully one of the broadcast tools might give you a clue as to what that "something" might be.

markzenn11

full member

Activity: 422

Merit: 102

still working on the problem. as of today im updating to a new version of bitcoin core wallet. im using ver 0.18.0 before and im currently downloading the new ver 0.19.0.1. open the wallet there, the one that is copied from ver 0.18.0 which contain the unconfirmed transactions. then i will push the same transactions to different nodes.

nc50lc

legendary

Activity: 2618

Merit: 6452

Self-proclaimed Genius

Quote from: markzenn11 on January 02, 2020, 11:35:22 PM

if i do that, it wont double spend the transactions?

I won't, it will be a double-spend if it's a different transaction (with a different hash) spending the same UTXO.
What you will do is simply re-broadcast the same transaction to another node instead of your own.

I already suggested you this three days ago (post link) to check if the culprit is your node or wallet.dat's saved transaction history.

markzenn11

full member

Activity: 422

Merit: 102

Quote from: HCP on January 02, 2020, 05:42:35 PM

That's very odd. It doesn't generate an error when you broadcast it... But it seems like it is not being propagated Huh

So, possibly your transaction is not being broadcast correctly. What happens if you copy the raw transaction hex (result from gettransaction command)...

And paste it here to broadcast it: https://live.blockcypher.com/btc/pushtx/

Does it broadcast Ok? Do you get an error?

if i do that, it wont double spend the transactions?

HCP

legendary

Activity: 2086

Merit: 4363

That's very odd. It doesn't generate an error when you broadcast it... But it seems like it is not being propagated Huh

So, possibly your transaction is not being broadcast correctly. What happens if you copy the raw transaction hex (result from gettransaction command)...

And paste it here to broadcast it: https://live.blockcypher.com/btc/pushtx/

Does it broadcast Ok? Do you get an error?

markzenn11

full member

Activity: 422

Merit: 102

Quote from: HCP on January 01, 2020, 01:37:24 PM

Quote from: markzenn11 on January 01, 2020, 06:20:36 AM

Quote from: HCP on December 30, 2019, 02:53:36 PM

What is the result of that? Do you get an error? Or does it simply return the TransactionID? Huh

it simply return the TransactionID.

Ok... so now what does it say when you right click the transaction in the history list and select "show transaction details"? What is the "status" now?

It should either say something like "0/unconfirmed, in memory pool" or... hopefully, it now says "XXX confirmations"

HCP

legendary

Activity: 2086

Merit: 4363

Quote from: markzenn11 on January 01, 2020, 06:20:36 AM

Quote from: HCP on December 30, 2019, 02:53:36 PM

What is the result of that? Do you get an error? Or does it simply return the TransactionID? Huh

it simply return the TransactionID.

Ok... so now what does it say when you right click the transaction in the history list and select "show transaction details"? What is the "status" now?

It should either say something like "0/unconfirmed, in memory pool" or... hopefully, it now says "XXX confirmations"

markzenn11

full member

Activity: 422

Merit: 102

Quote from: HCP on December 30, 2019, 02:53:36 PM

Ok... try and open the console in Bitcoin Core: Window -> Console

Then try:

Code:

getrawtransaction INSERT_THE_TRANSACTION_ID_HERE

eg: getrawtransaction 71dcc757a518b328e9d0493d.......................

That should hopefully give you the raw transaction hex... a very long string of hexadecimal numbers/letters. If you get an error, then there is a good chance that the transaction doesn't actually exist (wasn't broadcast, or has been dropped) on the network and is only local to your wallet. You'll need to try gettransaction instead.

Code:

gettransaction 71dcc757a518b328e9d0493d.......................

That should show you a "hex" as well.

Once you've managed to get a hex, then you need to copy it and try:

Code:

sendrawtransaction INSERT_LONG_HEXADECIMAL_STRING_HERE

What is the result of that? Do you get an error? Or does it simply return the TransactionID? Huh

it simply return the TransactionID.

HCP

legendary

Activity: 2086

Merit: 4363

Ok... try and open the console in Bitcoin Core: Window -> Console

Then try:

Code:

getrawtransaction INSERT_THE_TRANSACTION_ID_HERE

eg: getrawtransaction 71dcc757a518b328e9d0493d.......................

That should hopefully give you the raw transaction hex... a very long string of hexadecimal numbers/letters. If you get an error, then there is a good chance that the transaction doesn't actually exist (wasn't broadcast, or has been dropped) on the network and is only local to your wallet. You'll need to try gettransaction instead.

Code:

gettransaction 71dcc757a518b328e9d0493d.......................

That should show you a "hex" as well.

Once you've managed to get a hex, then you need to copy it and try:

Code:

sendrawtransaction INSERT_LONG_HEXADECIMAL_STRING_HERE

What is the result of that? Do you get an error? Or does it simply return the TransactionID? Huh

tranthidung

legendary

Activity: 2310

Merit: 4085

Farewell o_e_l_e_o

Quote from: markzenn11 on December 30, 2019, 07:18:23 AM

Transaction fee: -0.00054440 BTC
< ... >
Transaction total size: 2722 bytes

The fee is good, at 20 satoshis/ byte. Your transactions should be confirmed already. That is high enough to get confirmations fastly, according to ^{1, 2}
[1]: https://whatthefee.io/
[2]: https://coinb.in/#fees
In addition, I saw that mempool looks good now, so if you move your coins correctly (correct bitcoin address), I guess it will be confirmed very soon from now.

However, I think what nc50lc pointed out is right. Your transaction has not yet been broadcasted.

For your privacy,

If you care about privacy, and that one (the image in that post) comes from your same wallet, I believe you should blur or hide those addresses.
I did not quote that image, just in case you decide to delete it.

nc50lc

legendary

Activity: 2618

Merit: 6452

Self-proclaimed Genius

Quote from: markzenn11 on December 30, 2019, 07:18:23 AM

Status: 0/unconfirmed, not in memory pool

Not in mempool means that it wasn't broadcast yet.
It might be: saved without broadcasting, rejected by your own node for some reason or just a connection issue of your node.

Try to check if that transaction was already confirmed using an online blockexplorer by pasting the "Transaction ID" to the search bar.
If there's a result, it's just your node/client; If there's no result, re-broadcast it to any blockexplorer and see if it will be accepted.

Steps for broadcasting using a blockexplorer: Right-click the transaction, select "Copy raw transaction",
paste it here: https://blockstream.info/tx/push or https://blockchair.com/broadcast (select bitcoin) and click Broadcast transaction.
If it resulted with an error message, paste it here.

Topic: restoring and spending bitcoin (Read 783 times)