Bitcoin core, can’t send my BTC (not in memory pool) - page 2.

djhomeschool

full member

Activity: 340

Merit: 164

Quote from: Ocakypa on April 19, 2019, 04:30:30 AM

Quote from: BitMaxz on April 17, 2019, 01:38:47 PM

Quote from: Ocakypa on April 17, 2019, 09:58:42 AM

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 ?

Ocakypa

full member

Activity: 700

Merit: 100

Quote from: BitMaxz on April 17, 2019, 01:38:47 PM

Quote from: Ocakypa on April 17, 2019, 09:58:42 AM

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?

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

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?

LoyceV

legendary

Activity: 3290

Merit: 16489

Thick-Skinned Gang Leader and Golden Feather 2021

Quote from: Ocakypa on April 17, 2019, 05:47:05 AM

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 Cheesy

Quote from: Ocakypa on April 17, 2019, 09:58:42 AM

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.

BitMaxz

legendary

Activity: 3374

Merit: 3095

Playbet.io - Crypto Casino and Sportsbook

Quote from: Ocakypa on April 17, 2019, 09:58:42 AM

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.

Ocakypa

full member

Activity: 700

Merit: 100

Quote from: elda34b on April 17, 2019, 07:53:43 AM

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://bitcointalksearch.org/topic/bitcoin-core-transaction-not-reaching-mempools-missing-parents-2637574

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?

elda34b

sr. member

Activity: 910

Merit: 351

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://bitcointalksearch.org/topic/bitcoin-core-transaction-not-reaching-mempools-missing-parents-2637574

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

djhomeschool

full member

Activity: 340

Merit: 164

Quote from: Ocakypa on April 17, 2019, 06:25:43 AM

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

Quote from: djhomeschool on April 17, 2019, 06:07:19 AM

Maybe this helps:

Quote

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.

Ocakypa

full member

Activity: 700

Merit: 100

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

Quote from: djhomeschool on April 17, 2019, 06:07:19 AM

Maybe this helps:

Quote

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

full member

Activity: 340

Merit: 164

Maybe this helps:

Quote

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

full member

Activity: 700

Merit: 100

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

Topic: Bitcoin core, can’t send my BTC (not in memory pool) - page 2. (Read 436 times)