transactions – Bitcoin sent, confirmed in my final – never received at the other end

They sent me a link that took me to a coinbase processor. I got the address of the wallet and sent the money from my Electrum wallet. I have 157 confirmations, Electrum shows that it is there and complete, but the receiver says he never received it.

One of the three things has happened:

  • The receiver's wallet is not properly synchronized with the network and has not seen your transaction
  • The receiver lies about not receiving the transaction
  • Somehow, it sent Bitcoin to the wrong address (for example, the malware injected a malicious address into its copy / paste clipboard)

Someone told me that if btc is not claimed within 30 days, it automatically returns to its place of origin.

This is incorrect. Perhaps there are escrow services that work this way, but if you send a real Bitcoin transaction and it is confirmed in the blockchain, then the probability of it being reversed is basically zero.

So, where could the money be if they say they no longer use Bitcoin? Is not he still in that wallet? They just have to do it right?

If you can link an address you sent, or a transaction ID, someone could take a look at the chain of blocks to see where the Bitcoin ended, but in general:

If you sent to a coinbase payment page, then the payment was sent to a Bitcoin address controlled by Coinbase. Coinbase may You have forwarded this payment to the person who was paying, or you may still be in that person's base currency account. He would have to contact Coinbase and / or his counterpart to solve the problem. There is nothing more anyone can do to help you remedy the situation.

I sent Bitcoin to my e-wallet address without hitting the application first now it says it is confirmed and I have no money after requesting it

I sent Bitcoin to my e-wallet address without hitting the application first now it says it is confirmed and I have no money after requesting it after Isent. Can I receive my currency?

Bitcoin Core – Transaction confirmed but not used

enter the description of the image here

Hello, I have a serious problem since this transaction is successful, but the recipient insists that it is not in your wallet or received any confirmation of the transaction, I have been trying to understand what went wrong and why I continue to see this transaction as & # 39; not worn & # 39; How can I solve this please?

Mueller confirmed that Seth Rich did not steal Hillary's emails. Why Sean Hannity or Julian Assange will not apologize for spreading lies?

Like Trump they do not care if they lie.

Rich, 27, was an employee of the Democratic National Committee (DNC), and his murder spawned several right-wing conspiracy theories,[3] including the false claim that Rich had been involved with the leaked emails of DNC in 2016, contradicted by the police authorities who investigated the murder.

Data verification websites such as,[5][8],[9] and stated that these theories were false and unfounded.[4] The New York Times, Los Angeles Times and The Washington Post wrote that the promotion of these conspiracy theories was an example of false news.[10][11][12]

These conspiracy theories were promoted by Mike Cernovich, Sean Hannity, Geraldo Rivera, Kim Dotcom, Paul Joseph Watson, Newt Gingrich, Jack Posobiec and others.[81][82][83]

The same places that fostered the false theory of the Pizzagate conspiracy helped to enact the conspiracy theories of Seth Rich's murder,[11][84][85] and each one shares similar characteristics.[86][87][88] Both were promoted by individuals who subscribed to the politics of the extreme right,[89] and by campaign officials and individuals appointed to high-level national security positions by Donald Trump.[90][91][92] After the previous coordination in Facebook, each theory was spread on Twitter using automated robots using a brand hashtag, with the aim of becoming a trend topic.[84] Both the Pizzagate conspiracy theory and Seth Rich's murder plot conspired in the subreddit / r / The Donald forum.[93] In both conspiracy theories, the promoters tried to change the burden of proof, asking others to try to refute their claims, without citing justified evidence.[94]


How to include all recent confirmed files from git cherry-pick the latest confirmation?

If I have an extraction request in which I have multiple confirmations that include 12 to 15 files, then, during the selection process, what would be the best compromise for git cherry-pick to include all the confirmed files?

Blockcjain Transaction transfer delay while it is ready confirmed in the block chain

enter the description of the image here

As you can see … I made a transaction of this specific address from my blockchai. Wallet
But until now I still received this finding, while in the history of blockchain the transaction is ready to be confirmed.

What taxi do I do to get my money back in my blockchain wallet?
Is it possible to cancel this transfer transaction so that my money can be returned?

Please .. Nees a help.

Why is my transaction not confirmed and what can I do about it?

Here is a guide for as many portfolios as you could find out how to perform an RBF with. This was adapted from my bitcointalk publication:

A "stuck" transaction is a transaction that has remained unconfirmed for a period of time with which the recipient or sender does not feel comfortable. Stuck transactions can be annoying because it means that recipients often feel that the senders have not yet paid or that the recipient needs the money as soon as possible.

Stuck transactions are usually caused by low transaction fee rates. However, other things can cause stuck transactions, such as spending on an unconfirmed transaction, having dust outs in the transaction or being a double expense of another transaction. If a transaction has a double-spending transaction and the double investment confirms, then the transaction will be "stuck" forever, since it can never be confirmed.

There are several options to confirm stuck transactions:

For both the recipient and the sender of the transaction, you can:

  • Wait for the transaction to be confirmed.
  • Wait for the network to "forget" about the transaction.
  • Ask a miner to confirm it

For the sender of a transaction, you can also:

  • Try a double-spending transaction of Replace-By-Fee
  • If you have a change result, you can try a Child-Pays-For-Parent transaction

For the recipient of a transaction, you can also:

  • Try a "Child-Pays-For-Parent" transaction

Waiting for a confirmation

If you can not do any of the other options or are too afraid to do so, you can simply wait and wait for the transaction to finally confirm. To ensure that the transaction is constantly reminded to the network, you can reissue it periodically. Most wallets will be retransmitted automatically, so simply leaving your wallet open will allow the retransmission to take place.

Waiting for the network to "forget" about the transaction

If a transaction remains unconfirmed for too long, most nodes in the Bitcoin network will "forget" it eventually if nobody re-transmits the transaction. This happens due to node restarts, mempool expiration times or mempool eviction because the minimum mempool rate has increased. This process usually takes a few days (usually 3). Once a transaction has been "forgotten," you may not see it in your wallet and you probably will not see it in most block explorers. Once the transaction has been "forgotten", you can simply send the Bitcoin again but include a higher transaction fee. If you still see the transaction in your wallet but can not find it in any block explorer, you should follow the instructions in the next section of Replacement for Charge.

Keep in mind that some wallets will reissue the transaction continuously while the wallet is on, so you must delete the wallet transaction following the instructions in the RBF section, or close the wallet and keep it for several days.

Ask a miner for help

Some mining and mining groups offer services that allow you to prioritize your transaction in your mempool so that it is chosen before it is included in a block. One of these services is Note that ViaBTC has an accelerator limit of 100 transactions per hour and requires you to pay a minimum rate of 10 satoshis / byte, so your accelerator does not necessarily work. Another service of this type is It is not that requires another form of payment to "speed up" your transaction.

Also note that if you attempt to perform a Replacement transaction by charge, both the original transaction and the RBF transaction will be considered double expenses. The miners will probably not help with any transaction marked as double spending.

Attempt of a double-spending transaction in Replace-By-Fee (RBF)

What is an RBF transaction?

A Replacement by Fee transaction is a transaction that is almost identical to your blocked transaction but pays a higher transaction fee. Because the original transaction probably does not use Opt-in RBF, the RBF transaction that we will create will be considered double spending and will be marked as such. The transaction uses Full-RBF and, therefore, may take a little longer to be confirmed, since it is technically a double expense.

The difference between the types of RBF transactions.

The Replacement by Fee transactions have 3 different types, RBF First-Seen-Safe (FSS), full RBF and RBF Opt-in. FSS RBF requires that the RBF transaction include the same results as the transaction that replaces and consumes the same entries. Full RBF means that the transaction is simply a double expense of another transaction, but pays a higher transaction fee than the one it replaces. Opt-in RBF means that the RBF transaction can only replace a transaction that you have opted to allow to be replaced. Opt-in RBF follows BIP 125.

The instructions given in this section will be used to perform full RBF transactions. The optional RBF transactions will be described in the section "How to avoid blocked transactions in the future".

How to make a complete RBF transaction

The completion of a complete RBF transaction depends completely on the wallet you are using. Some portfolios support the advanced functionality required to complete a complete RBF transaction, others do not. The following will be guides for each wallet on how to make a complete RBF transaction with that wallet. In general, the procedure is to eliminate the unconfirmed transaction from the portfolio and then resend the Bitcoin but with a higher transaction fee.

When making a complete RBF transaction, the transaction must include the recommended effective fare rate at the time of creating the transaction. See the "How to avoid this problem in the future" section for help with that.

Bitcoin Core

Bitcoin Core makes making Full RBF transactions very easy. Simply go to the transaction list, right-click on the transaction that is stuck and choose the Leave the transaction option.

If that option is disabled, go to Bitcoin Core datadir and eliminate the mempool.dat case file. Then restart Bitcoin Core with the -walletbroadcast = 0 option and then you should be able to use Leave the transaction.

If the two previous options fail for some reason, start Bitcoin Core with the -zapwallettxes Option to delete all unconfirmed transactions from your wallet.

Once the transaction is Abandoned or deleted from the portfolio, you can simply go to the Send and send Bitcoin tab again, but be sure to include a sufficient transaction fee.

Bitcoin Armory

Bitcoin Armory also makes it easy to make Full RBF transactions. To go Help> Delete all unconfirmed transactions and restart the armory. This will erase all unconfirmed transactions from the portfolio and, therefore, allow you to create the complete RBF transaction. Once Armory has restarted, simply send Bitcoin again as you would normally, but be sure to include a sufficient transaction fee.

MultiBit HD

MultiBit HD allows to make the Full RBF transactions also quite easy. To go Manage wallet and click Repair portfolio and follow the assistant. This process will erase all unconfirmed transactions from your wallet in much the same way as Bitcoin Core and Armory do. Once the repair of the wallet is completed, simply send the Bitcoin again as you would normally. Keep in mind that some users have had problems with this method in the past and it may not always work. You may have to wait for the transaction to "forget" for this method to work.

Wallets that do not allow you or those that do not know how to make transactions Full RBF

Not all portfolios support the creation of complete RBF transactions. Many portfolios do not allow deleting all unconfirmed transactions to allow Full RBF transactions. The following is a list of wallet software that does not support Full RBF transactions. If a wallet on this list supports FullRBF transactions, please let me know and provide instructions so you can add it above.

  • and web portfolios in general.
  • Electrum (supports Opt-in RBF, but not Full RBF)
  • Mycelium
  • MultiBit Classic
  • Bitcoin wallet for Android
  • Roll
  • Copay

Trying a Child-Pays-For-Parent transaction

What is a Child-Pays-For-Parent transaction?

A Child-Pays-For-Parent (CPFP) transaction is exactly as its name implies, a secondary transaction is spent on an unconfirmed principal transaction and includes a transaction fee that covers both the minor and the principal rates. However, creating CPFP transactions is much more difficult since it requires expenses of an unconfirmed transaction, something that many portfolios do not allow.

Use of dynamic rates

The best way to avoid having blocked transactions is to make sure you are not spending on an unconfirmed transaction and include a sufficient transaction fee. If your wallet supports dynamic transaction fees, you should use them. If you want very fast confirmations, set the dynamic rates to choose the fastest rate possible. The dynamic rates are calculated by the purse analyzing the current state of the network and determining an optimal transaction rate from there. Since the state of the network changes constantly, the optimal transaction rate calculated one day may not necessarily be the best rate for the next day.

If your wallet does not support dynamic rates, but allows you to set a custom transaction fee rate for each transaction, you can search for the optimal fare rate at sites such as and https: // bitcoinfees. github .io / and set the rate of each transaction based on those sites. You must do this for every transaction you make; otherwise, you may end up paying a fee below the optimal level.

If your wallet does not support any type of fare or does not allow you to set custom transaction fees, you must upgrade to a new wallet. Using a fixed or fixed rate is no longer a good idea since the network changes constantly. You can use this formula: * 148 + * 34 + 10 where is the number of entries and is the number of departures to estimate the size of your transaction and determine the optimal rate for it.

Keep in mind that some portfolios (for example,, although they use dynamic rates, set an upper limit to the transaction rate. If you notice that your transactions are constantly stuck even though you are using dynamic rates, you should check your wallet settings and perhaps even switch to a new wallet that has no limit on the transaction fee.

Use Opt-In RBF

Opt-In RBF is a function that allows an RBF transaction to be created more easily since these transactions will not be rejected by nodes that support Opt-In RBF.

Currently few portfolios support the creation of RBF Opt-In transactions


To create a transaction that can be replaceable, go to Tools> Preferences and check the box "Enable Replacement by Position". Then, when you want to send a Bitcoin, there is a box with the "Replaceable" label next to the Rate slider. Check that box so that while the transaction is not yet confirmed, you can replace the transaction with one that pays a higher rate.

To increase the rate of a transaction using Opt-In RBF, right-click on the transaction in the history list and choose the "Increase rate" option.


Armory also allows the creation of RBF transactions. When sending a transaction, select the "Enable RBF" checkbox.

To increase the rate of a transaction using Opt-In RBF, right-click on the transaction in the transaction list and choose the "Reduction Rate" option. Transactions whose rate can be increased are clearly indicated in the list of transactions.

Transactions not confirmed, with low rates

Is there a way to estimate when a transaction or a set of transactions will be extracted from the same party? For example, let's say the company paid a small fee for transactions.

How would you estimate the time this bit of Bitcoin transaction hash will spend?


Thank you

I sent bitcoin from electrum, but I never received it, it has been confirmed, but I can not say what happened with the btc. Can someone help me?

Your transaction is visible in the block chain. Click here to find your transaction ID on the website of a block explorer.

The previous block browser shows what you already know about your screenshot: it shows that address bc1q7hsnpd794pap2hd3htn8hszdfk5hzgsj5md9lz received 0.23975489 BTC from you on 2019-02-19.

Now click here to see the history of the address bc1q7hsnpd794pap2hd3htn8hszdfk5hzgsj5md9lz. As you can see, there are 13 pages of transactions, dating back more than a year. If you do not recognize them, it probably means that bc1q7hsnpd794pap2hd3htn8hszdfk5hzgsj5md9lz is someone else address.

sql server – Can MSSQL CDC be used to capture old confirmed transactions?

I can successfully capture the change data of mssql CDC by issuing the query

cdc.fn_cdc_get_all_changes_capture_instance (from_lsn, to_lsn,
& # 39;& # 39;)

Here, de_lsn is the min_lsn (the oldest uncommitted transaction) that I can get from the database.

But I already have an old confirmed transaction that I want to replicate, so I got the LSN for one of its rows and tried to issue the previous query using the obtained LSN (from_lsn) that failed with the following error message

Error executing SQLException queries; ErrorCode: 313; SQLCode: S0003; SQL message: A sufficient number of arguments were not provided for the procedure or function cdc.fn_cdc_get_all_changes_ ...

Is it possible to capture past changes of MSSql? If yes, some guidance would be appreciated.