restoring and spending bitcoin

[markzenn11]

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?

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.

[1714938878]

1714938878

[1714938878]

1714938878

[1714938878]

1714938878

[1714938878]

1714938878

[HCP]

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

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".

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".

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.

[nc50lc]

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.

[markzenn11]

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?

[HCP]

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.

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?

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.

[HCP]

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



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

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

[markzenn11]

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]

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

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.