bitcoin core – Resolve BTC long memory pool (lots of unconfirmed messages)

I started with the Bitcoin exchange service, creating rawtransaction and broadcasting it. The problem I have to deal with is the mempool string too long (more than 25 unconfirmed transactions), for example:
64: chain too long

Using limitancestorcount and limitdescendantcount Just solve on the local node, these late txs (transaction after the first 25) have to wait a long time to be rebroadcast like this:
Transaction not found in blockchain

Here is my testnet address has a lot of unconfirmed txs and still waiting, if I search on another explorer, I can not see 45 unconfirmed txs, same for getrawtransaction on the node, respose is No such mempool or blockchain transaction:

So, how can I avoid this problem, I just think of several methods, such as: divide the main address into a few sub-addresses, which divides the main UTXO into a few UTXOs, create a many-to-many transaction (currently 1 to 2, 1 target and 1 changeAddress back), using UTXO first with high confirmation, … Which options can bring better results and performance for a long scaling? term? Any advice is really appreciated. And last question, is there a way to mark 1 UTXO used 25 times (for example, I use UTXO X first, then it is returned, Y is used, Z is returned, total using X = 2, I have no related information to calculate it because the node returns, UTXO only contains txId).

unconfirmed transactions – exchange of cryptocurrency

As has been said, the centralized exchange first requires the user to deposit BTC (for example) on a newly created public key (private key held by exchanges). All exchanges are off-line. Chain operations are just deposits and withdrawals. From now on, if a user wishes to withdraw, he sends the public address to which he wishes to receive the BTC and the corresponding BTC is sent by exchange.
Should not exchanges manage the private key for each user right from the start? They could have simply created 10 Bitcoin trading accounts, on which they would have told the user to file their BTC. The exchanges then update the dashboard of the user with the same amount btc. The update of all exchanges takes place on a database and when the user wishes to withdraw, the exchange simply transfers to one of his addresses the amount of the B & C. End user.

What is the purpose of creating a portfolio for each user and exactly how does the withdrawal process work?

bitcoin core – Call RPC to get an unconfirmed balance on a wallet only in watch mode

You can use the make balances order. He will return all balances in the portfolio, including those that the portfolio can sign, only monitor things that are trustworthy (confirmed transactions and unconfirmed changes) and immature currency exits.

Here is the help output for this.

make balances
Returns an object with all balances in BTC.

"mine": {(object) balances outflows that the wallet can sign
"trustworthy": xxx balance of confidence (numeric) (exits created by the portfolio or confirmed)
"untrusted_pending": xxx (numeric) pending unapproved balance (exits created by others that are in mempool)
"immature": xxx balance (numeric) from the immature outputs of the database
"used": xxx (numeric) (present only if Avoid_reuse is defined), balance of coins sent to previously used addresses (risk of breach of confidentiality)
"watchonly": {(object) watchonly balance (not present if the wallet does not look at anything)
"trustworthy": xxx balance of confidence (numeric) (exits created by the portfolio or confirmed)
"untrusted_pending": xxx (numeric) pending unapproved balance (exits created by others that are in mempool)
"immature": xxx balance (numeric) from the immature outputs of the database

json rpc – `walletcreatefundedpsbt` with unconfirmed entries

Bitcoin Core will never select unconfirmed incoming outputs. These are still considered unreliable and unsafe for coin selection. This applies to all transactions created by Bitcoin Core, including those created with the help of Bitcoin Core. walletcreatefundedpsbt or fund transaction.

For a code reference, the Available parts function is used to search and filter the parts available for coin selection that calls the IsTrusted function for each available output (transaction actually stored in the wallet including incoming and outgoing transactions). If the transaction was not created by this portfolio, it is considered unreliable. IsTrusted returns false, which results in Available parts exclude all outputs from this transaction from all the outputs used for coin selection.

MultiBit HD Portfolio showing an unconfirmed amount

another idiot here with an old MultiBit HD wallet that has lost the words of the wallet.
I've had some hard drive issues on my laptop and after solving them, my wallet suddenly shows that the balance equals 0 and that the amount is not confirmed. This is incorrect in fact because I can see that everything is confirmed correctly in the blockchain:

A strange thing happened at the first time after solving the hard drive problem and syncing, the MultiBit HD complaining that the system time on my computer was incorrect, which was true. Maybe this caused an incorrect synchronization?

As I said, I do not have words in the wallet, I only have the password and the .wallet file.

I have tried the option "Wallet Repair" several times without result.

I'm using version 0.4.1 and this prompts me to upgrade to version 0.5.1, which I have not done yet

If any of you can give advice, I will consider you as my hero

blockchain – bitcoin lost due to an unconfirmed transaction

someone on blockchain support is asking me to tell him my reserve fund in 12 words in order to reverse my bitcoin that was not confirmed in my transaction

Sorry to say that you have been permanently scammed.

You can not reverse a bitcoin transaction that way, the scammer just told you that to give them the 12-word expression. With this sentence, the scammer could recreate your wallet on another device and steal your coins.

Never do give someone your private keys, start phrase, PIN code, password, and so on. Any legitimate customer service will not ask you.

unreal 4 – Why is my project overlap canceled / disabled / unconfirmed?

I finally discovered the problem that haunted me for some time, which made me ask these 3 questions:

How to make overlap detection more accurate?

Foolish mistake in the overlap between 2 warriors and a tower

The overlap detection does not work properly when there is more than one warrior colliding with the tower

In programming, you learn very early that if something goes wrong, guilt belongs to you, a wrong variable, a wrong condition, commas, etc.

The only possible answer when it's not your fault (directly) is something you do not know about the engine / program or a really unexpected result.

For this reason, in the questions above, I thought it was an error in my code because I had a bit of trouble communicating between plans. That's why I thought it was my fault.

I've made a code so that every second is written if the warrior rides the tower:

enter the description of the image here

Again (for all those who have already seen other issues), I notice that when only one warrior rides the tower, all is well:

enter the description of the image here

Now, when several warriors ride the tower simultaneously, it's not right:

enter the description of the image here

I thought the problem was maybe due to the fact that I wanted the warrior to stay to try to go to the tower when it was overlapping (just to not put an end to the overlap caused by the arrival of a new warrior) and I tried to stop him. move as soon as she rides the tower, but the error persists:

enter the description of the image here

The increase in the size of the collision box worked on a simpler test than the one I did on another project, but I think the cause of the problem is not that. In addition, the collision box of the tower is already huge in this project. I would like to know how to make sure that the overlap between the warriors and the tower is not broken for no reason.

altcoin – Transaction show unconfirmed alternately- Litecoin fork

I have a litter fork. I just installed an automatic miner for the transaction in my altcoin network. I then try to send a piece from one node to another, the transaction is confirmed alternately. This is the first transaction state as Status: 2 / not confirmed and the second status is 0 / unconfirmed, in memory pool. This process continues alternately. In addition, I mention that I have set higher fees for each transaction. I wait a long time and mine more blocks to confirm the second transaction. But no result. Do you have suggestions or solutions to solve this problem? Any help is grateful.

Thank you

bitcoin core – Sendmany unconfirmed parts (minconf = 0)

can anyone help me understand the opportunities if bitcoind RPC.

How to send unconfirmed parts? With the command RPC & # 39; sendmany & # 39; and param & # 39; minconf = 0 & # 39; for an impossible reason. But how to do this kind of transaction, as does the hardwallet Trezor?

And another question. How to send to an address in one transaction (example:
Sendmany also do not allow it.

Thank you in advance.

Unconfirmed Transactions – Why does the Bitcoin-core Wallet application not transmit payment?

Why does the Bitcoin-core Wallet application not transmit payment?

Bitcoin-core Wallet app no ​​delivery transaction.

From March 18th until the date, the Bitcoin-core Wallet application keeps my satoshis with the message "this payment has not yet been transmitted"; they invite you to increase the amount of network charges in the order of 0.000288 satoshis, increases that I paid 2 on 18 and 2 and over the 19 for a total increase of 0.001152 satoshis, more than generous attract the attention of minors (these increments do not record any address). The address generated by
The Wallet Bitcoin-core application after being received and consulted with explorers as blockchain records that "There is no transaction for this address". As additional data, the Bitcoin-core Wallet app received satoshis from the paper wallet. As you can see, it took more than prudential time to get results. I do not know what can happen in the menpool, I do not know who can
to be responsible for the delay, I do not know who to complain about, I only have the Bitcoin interested community that continues to be decentralized. For this reason, if someone can answer by clarifying what is happening with this deficient delay, we will be very happy.
In short, use the Bitcoin-core wallet application to receive a paper wallet, an accepted acknowledgment and the generation of a new address, invite to increase the commission of the network of action which is constituted several times, until present impossible to use the satoshis. Once again the community interested and competent to answer, thank you so much.