Bitcoin core, can’t send my BTC (not in memory pool)

[Ocakypa]

Hello everyone!
I found my wallet.dat from 2015 and have several problems:
1. It’s consist of 0.0001 BTC x 90000 transactions = ~9 BTC. Bitcoin’s dust in fact.
2. When I send a transaction it has a status:0/unconfirmed not in memory pool.

Please help me to collect bitcoin’s dust and transfer it with minimal looses.

I’m ready to pay for this job 

[1714953078]

1714953078

[1714953078]

1714953078

[1714953078]

1714953078

[1714953078]

1714953078

[1714953078]

1714953078

[djhomeschool]

Maybe this helps:

The current dust limit fee rate is 3 satoshis/byte. If, at 3 satoshis per byte, an output would cost more in fees to spend that it has in value, then that output is considered dust. If you are sending to non-segwit addresses, this limit is 3 sat/byte * 148 bytes = 444 sats. If you are sending to P2SH-segwit addresses (the default address type in Bitcoin Core), then the fee limit is 3 sat/byte * 91 bytes = 273 sat. If you are sending to bech32 addresses, then the fee limit is 3 sat/byte * 68 bytes = 204 sat.

You can lower your dust limit by setting -dustrelayfee to something lower than 0.00003 BTC/kB (equivalent to 3 sat/byte). However I do not recommend that you change this as even though your node will accept transactions with outputs that are otherwise dust, other nodes will not and your transactions will not be relayed.

Furthermore, you should not set your transaction fee rate to be less than 0.00001 BTC/kB (equivalent to 1 sat/byte) as this is the default minimum relay fee and transactions that have a fee rate less than this will not be relayed. Just because your node accepts a transaction does not mean that other people's nodes will.

Credits to: https://bitcoin.stackexchange.com/questions/78096/in-bitcoin-core-how-to-avoid-the-dust-exception

[Ocakypa]

Thank you, I will check!
But what about that my transaction doesn’t reach Mempool?

Maybe this helps:

The current dust limit fee rate is 3 satoshis/byte. If, at 3 satoshis per byte, an output would cost more in fees to spend that it has in value, then that output is considered dust. If you are sending to non-segwit addresses, this limit is 3 sat/byte * 148 bytes = 444 sats. If you are sending to P2SH-segwit addresses (the default address type in Bitcoin Core), then the fee limit is 3 sat/byte * 91 bytes = 273 sat. If you are sending to bech32 addresses, then the fee limit is 3 sat/byte * 68 bytes = 204 sat.

You can lower your dust limit by setting -dustrelayfee to something lower than 0.00003 BTC/kB (equivalent to 3 sat/byte). However I do not recommend that you change this as even though your node will accept transactions with outputs that are otherwise dust, other nodes will not and your transactions will not be relayed.

Furthermore, you should not set your transaction fee rate to be less than 0.00001 BTC/kB (equivalent to 1 sat/byte) as this is the default minimum relay fee and transactions that have a fee rate less than this will not be relayed. Just because your node accepts a transaction does not mean that other people's nodes will.

Credits to: https://bitcoin.stackexchange.com/questions/78096/in-bitcoin-core-how-to-avoid-the-dust-exception

[djhomeschool]

Thank you, I will check!
But what about that my transaction doesn’t reach Mempool?

Maybe this helps:

The current dust limit fee rate is 3 satoshis/byte. If, at 3 satoshis per byte, an output would cost more in fees to spend that it has in value, then that output is considered dust. If you are sending to non-segwit addresses, this limit is 3 sat/byte * 148 bytes = 444 sats. If you are sending to P2SH-segwit addresses (the default address type in Bitcoin Core), then the fee limit is 3 sat/byte * 91 bytes = 273 sat. If you are sending to bech32 addresses, then the fee limit is 3 sat/byte * 68 bytes = 204 sat.

You can lower your dust limit by setting -dustrelayfee to something lower than 0.00003 BTC/kB (equivalent to 3 sat/byte). However I do not recommend that you change this as even though your node will accept transactions with outputs that are otherwise dust, other nodes will not and your transactions will not be relayed.

Furthermore, you should not set your transaction fee rate to be less than 0.00001 BTC/kB (equivalent to 1 sat/byte) as this is the default minimum relay fee and transactions that have a fee rate less than this will not be relayed. Just because your node accepts a transaction does not mean that other people's nodes will.

Credits to: https://bitcoin.stackexchange.com/questions/78096/in-bitcoin-core-how-to-avoid-the-dust-exception

I think because bitcoin core has a set min transaction fee and if it is lower it will not broadcast it, that is what i understand from above text.

[elda34b]

As far as I understand, djhomeschool got it correctly. Essentially if your transaction was considered as dust by other (almost every) nodes then it won't get transferred, therefore it won't reach the mempool.

However, judging from your case, I assume you're consolidating a lot of small input and then send it as a single output, is this right? Then it should not be considered as dust imo as long as your fee is high enough. Anyway, you can read more about this case here: https://bitcointalk.org/index.php?topic=2637574.0

Maybe one of your input is already spent. Can you post any raw data?

[Ocakypa]

As far as I understand, djhomeschool got it correctly. Essentially if your transaction was considered as dust by other (almost every) nodes then it won't get transferred, therefore it won't reach the mempool.

However, judging from your case, I assume you're consolidating a lot of small input and then send it as a single output, is this right? Then it should not be considered as dust imo as long as your fee is high enough. Anyway, you can read more about this case here: https://bitcointalk.org/index.php?topic=2637574.0

Maybe one of your input is already spent. Can you post any raw data?

Okay, I will post raw data a bit later.
Right, I'm trying to consolidate a lot of small input, but then bitcoin core writes error "transaction too large". After that, I tried to send a small amount like 0.01 BTC with priority fee and it still writes not in memory pool.
So, is there any opportunity to send bigger amount and solve a problem with "not in memory pool".

Regarding the case, i see that it looks like the same situation as mine, but don't fully understand steps to solve it. Maybe you can expain?

[BitMaxz]

Okay, I will post raw data a bit later.
Right, I'm trying to consolidate a lot of small input, but then bitcoin core writes error "transaction too large". After that, I tried to send a small amount like 0.01 BTC with priority fee and it still writes not in memory pool.
So, is there any opportunity to send bigger amount and solve a problem with "not in memory pool".

Regarding the case, i see that it looks like the same situation as mine, but don't fully understand steps to solve it. Maybe you can expain?

Let me ask if your all 90k transaction is received only in a single bitcoin address or it is in multiple addresses?

The only thing that comes to my mind If all inputs are only in a single bitcoin address dump the private key and import it to other wallets like electrum(Orig URL is electrum.org if you are planning use it) and simply make a new transaction and send it to the same address and pay 3 to 10 sat per byte(for low fee) to consolidate/merge all transactions into a single input. I don't know how fast the transaction to confirm but I have experienced consolidating all transaction into one in electrum with 1 sat/byte and it takes minutes to confirmed.

Now, you can send it to exchanges after confirmed with a lesser fee.

[LoyceV]

1. It’s consist of 0.0001 BTC x 90000 transactions = ~9 BTC. Bitcoin’s dust in fact.

Would you mind sharing your Bitcoin address here? I'm curious

I’m ready to pay for this job

Challenge accepted Let me start with some questions:
Have you read Fees are low, use this opportunity to Consolidate your small inputs! yet? Which version of Bitcoin Core are you using? Are you using coin control (explained in the topic linked above)? Did you make a backup of your wallet.dat yet?

According to https://coinb.in/#fees , 100 legacy inputs gives a 15 kB transaction. Since you've had the coins for a very long time, I assume you're not in a hurry, so you can save a lot on fees by setting low fees (1 sat/byte) and probably waiting a few days up to a week for confirmation.
With coin control, it's going to be a lot of work, but puts you in the driver seat.

Right, I'm trying to consolidate a lot of small input, but then bitcoin core writes error "transaction too large". After that, I tried to send a small amount like 0.01 BTC with priority fee and it still writes not in memory pool.

Coin control should help

If you're holding 9 Bitcoin from 2015, you also hold many different Forkcoins. LoyceV's Bitcoin Fork claiming guide (and service) is largely outdated, but still a good place to start reading.

[nc50lc]

Are you sure that it's a BitcoinCore or QT wallet.dat? It seems like your node instantly rejects the tx because it's invalid.
There were reports from users who've loaded altcoin wallet.dat to core and successfully viewed the alleged balance but failed to create a valid transaction and resulted with the same error.

Can you post any transaction ID (and its info like sent amount and addresses involved) from the History so that we can verify that it is in the network?

[Ocakypa]

Okay, I will post raw data a bit later.
Right, I'm trying to consolidate a lot of small input, but then bitcoin core writes error "transaction too large". After that, I tried to send a small amount like 0.01 BTC with priority fee and it still writes not in memory pool.
So, is there any opportunity to send bigger amount and solve a problem with "not in memory pool".

Regarding the case, i see that it looks like the same situation as mine, but don't fully understand steps to solve it. Maybe you can expain?

Let me ask if your all 90k transaction is received only in a single bitcoin address or it is in multiple addresses?

The only thing that comes to my mind If all inputs are only in a single bitcoin address dump the private key and import it to other wallets like electrum(Orig URL is electrum.org if you are planning use it) and simply make a new transaction and send it to the same address and pay 3 to 10 sat per byte(for low fee) to consolidate/merge all transactions into a single input. I don't know how fast the transaction to confirm but I have experienced consolidating all transaction into one in electrum with 1 sat/byte and it takes minutes to confirmed.

Now, you can send it to exchanges after confirmed with a lesser fee.

Hi man, I dumped private keys (there are 700+ not to include reserved addresses). So, regarding your question, - I've got transactions on multiple addresses.
I imported my keys to Electrum, but it's synchronizing already 24 hours. Is it ok?

[djhomeschool]

Okay, I will post raw data a bit later.
Right, I'm trying to consolidate a lot of small input, but then bitcoin core writes error "transaction too large". After that, I tried to send a small amount like 0.01 BTC with priority fee and it still writes not in memory pool.
So, is there any opportunity to send bigger amount and solve a problem with "not in memory pool".

Regarding the case, i see that it looks like the same situation as mine, but don't fully understand steps to solve it. Maybe you can expain?

Let me ask if your all 90k transaction is received only in a single bitcoin address or it is in multiple addresses?

The only thing that comes to my mind If all inputs are only in a single bitcoin address dump the private key and import it to other wallets like electrum(Orig URL is electrum.org if you are planning use it) and simply make a new transaction and send it to the same address and pay 3 to 10 sat per byte(for low fee) to consolidate/merge all transactions into a single input. I don't know how fast the transaction to confirm but I have experienced consolidating all transaction into one in electrum with 1 sat/byte and it takes minutes to confirmed.

Now, you can send it to exchanges after confirmed with a lesser fee.

Hi man, I dumped private keys (there are 700+ not to include reserved addresses). So, regarding your question, - I've got transactions on multiple addresses.
I imported my keys to Electrum, but it's synchronizing already 24 hours. Is it ok?

It should not take that long, i have Electrum wallets with over 2k addresses and it synchronizes in a few seconds.
What version of Electrum are you using? The latest one downloaded from https://electrum.org/#download ?

[AdolfinWolf]

Hi man, I dumped private keys (there are 700+ not to include reserved addresses). So, regarding your question, - I've got transactions on multiple addresses.
I imported my keys to Electrum, but it's synchronizing already 24 hours. Is it ok?

No, that doesn't sound OK. Electrum is an SPV wallet, which means there is not really any synchronizing[1] needed, atleast not one that takes 24H.

Either you have a really crappy internet connection, or there's something wrong with either

I. your PC/Network settings/firewall,

II. your wallet. (Outdated, corrupt, (fake version?(unlikely)).
III. The server you're connecting to on Electrum itself. Please try switching that up as well.

Please verify that you're using the latest version of electrum, and that you're using the right version. (Checksum matching, verify the signature.)

Didn't read the fact that you have over 90k transactions...  My bad. That could be a big factor in why it won't sync, but it's still something i've never heard happening before...

[LoyceV]

Hi man, I dumped private keys (there are 700+ not to include reserved addresses). So, regarding your question, - I've got transactions on multiple addresses.
I imported my keys to Electrum, but it's synchronizing already 24 hours. Is it ok?

There's no reason to abandon Bitcoin Core and use Electrum for this. It's no surprise for Electrum to take a long time synchronizing 90,000 (or more) transactions, if you really want to use Electrum, don't import all private keys at once.

If you answer my previous questions I can continue with more suggestions

[Ocakypa]

1. It’s consist of 0.0001 BTC x 90000 transactions = ~9 BTC. Bitcoin’s dust in fact.

Would you mind sharing your Bitcoin address here? I'm curious

I’m ready to pay for this job

Challenge accepted Let me start with some questions:
Have you read Fees are low, use this opportunity to Consolidate your small inputs! yet? Which version of Bitcoin Core are you using? Are you using coin control (explained in the topic linked above)? Did you make a backup of your wallet.dat yet?

According to https://coinb.in/#fees , 100 legacy inputs gives a 15 kB transaction. Since you've had the coins for a very long time, I assume you're not in a hurry, so you can save a lot on fees by setting low fees (1 sat/byte) and probably waiting a few days up to a week for confirmation.
With coin control, it's going to be a lot of work, but puts you in the driver seat.

Right, I'm trying to consolidate a lot of small input, but then bitcoin core writes error "transaction too large". After that, I tried to send a small amount like 0.01 BTC with priority fee and it still writes not in memory pool.

Coin control should help

If you're holding 9 Bitcoin from 2015, you also hold many different Forkcoins. LoyceV's Bitcoin Fork claiming guide (and service) is largely outdated, but still a good place to start reading.

Yes, I read your thread
I'm using the last one - 0.17.1
Yes, I tried to use coin control and it writes me that transaction too big (there were 15k bytes). If I make a smaller transaction in writes "not in memory pool" in history. Maybe it makes sense, I put recipient address, which from my Ledger, not generated inside Bitcoin Core.
Yes, I made several backups. 

[Ocakypa]

Okay, I will post raw data a bit later.
Right, I'm trying to consolidate a lot of small input, but then bitcoin core writes error "transaction too large". After that, I tried to send a small amount like 0.01 BTC with priority fee and it still writes not in memory pool.
So, is there any opportunity to send bigger amount and solve a problem with "not in memory pool".

Regarding the case, i see that it looks like the same situation as mine, but don't fully understand steps to solve it. Maybe you can expain?

Let me ask if your all 90k transaction is received only in a single bitcoin address or it is in multiple addresses?

The only thing that comes to my mind If all inputs are only in a single bitcoin address dump the private key and import it to other wallets like electrum(Orig URL is electrum.org if you are planning use it) and simply make a new transaction and send it to the same address and pay 3 to 10 sat per byte(for low fee) to consolidate/merge all transactions into a single input. I don't know how fast the transaction to confirm but I have experienced consolidating all transaction into one in electrum with 1 sat/byte and it takes minutes to confirmed.

Now, you can send it to exchanges after confirmed with a lesser fee.

Hi man, I dumped private keys (there are 700+ not to include reserved addresses). So, regarding your question, - I've got transactions on multiple addresses.
I imported my keys to Electrum, but it's synchronizing already 24 hours. Is it ok?

It should not take that long, i have Electrum wallets with over 2k addresses and it synchronizes in a few seconds.
What version of Electrum are you using? The latest one downloaded from https://electrum.org/#download ?

Yes, the latest one

[Ocakypa]

Hi man, I dumped private keys (there are 700+ not to include reserved addresses). So, regarding your question, - I've got transactions on multiple addresses.
I imported my keys to Electrum, but it's synchronizing already 24 hours. Is it ok?

No, that doesn't sound OK. Electrum is an SPV wallet, which means there is not really any synchronizing[1] needed, atleast not one that takes 24H.

Either you have a really crappy internet connection, or there's something wrong with either

I. your PC/Network settings/firewall,

II. your wallet. (Outdated, corrupt, (fake version?(unlikely)).
III. The server you're connecting to on Electrum itself. Please try switching that up as well.

Please verify that you're using the latest version of electrum, and that you're using the right version. (Checksum matching, verify the signature.)

Internet connection perfect.

What to check regarding I?
 II. If it's corrupted, why Bitcoin Core didn't send errors?

[LoyceV]

Yes, I tried to use coin control and it writes me that transaction too big (there were 15k bytes). If I make a smaller transaction in writes "not in memory pool" in history. Maybe it makes sense, I put recipient address, which from my Ledger, not generated inside Bitcoin Core.

Sorry, I don't know what causes this. It doesn't sound like normal behaviour, so maybe your wallet needs a rescan or something.

[HCP]

Yes, I tried to use coin control and it writes me that transaction too big (there were 15k bytes).

Correct. There is no way you will be able to consolidate all 90,000 inputs in one transaction. You will need to do it in batches.

If I make a smaller transaction in writes "not in memory pool" in history.

If it is showing as "not in mempool", this is due to your transaction being refused by upstream nodes as invalid. This could be caused by missing inputs, missing signatures, invalid outputs etc... but generally, you should get a popup with an error code+message when sending "fails".

Do you get any sort of error message when attempting to send the smaller transactions?

Or does it simply create and entry in "history"?

Is your Bitcoin Core fully synced?

Maybe it makes sense, I put recipient address, which from my Ledger, not generated inside Bitcoin Core.

That shouldn't make any difference... Bitcoin Core is able to send to addresses generated on a Ledger device.

[nc50lc]

Are you sure that it's a BitcoinCore or QT wallet.dat? It seems like your node instantly rejects the tx because it's invalid.
There were reports from users who've loaded altcoin wallet.dat to core and successfully viewed the alleged balance but failed to create a valid transaction and resulted with the same error.

Can you post any transaction ID (and its info like sent amount and addresses involved) from the History so that we can verify that it is in the network?

Quoting myself here since OP somehow ignored the fact that it may be an Altcoin wallet.dat that's compatible with Bitcoin core like Litecoin and DogeCoin.

One transaction in the history is enough to tell that it's an altcoin wallet.dat or not (Forks may be harder to tell though).

[Ocakypa]

Are you sure that it's a BitcoinCore or QT wallet.dat? It seems like your node instantly rejects the tx because it's invalid.
There were reports from users who've loaded altcoin wallet.dat to core and successfully viewed the alleged balance but failed to create a valid transaction and resulted with the same error.

Can you post any transaction ID (and its info like sent amount and addresses involved) from the History so that we can verify that it is in the network?

Quoting myself here since OP somehow ignored the fact that it may be an Altcoin wallet.dat that's compatible with Bitcoin core like Litecoin and DogeCoin.

One transaction in the history is enough to tell that it's an altcoin wallet.dat or not (Forks may be harder to tell though).

Hi man, how can I check it?
Because very strange situation, bitcoin core shows balance, but when I check same addresses on the blockchain it shows zero balance.