Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please Support Received Transaction Expedition #6020

Closed
dabura667 opened this issue May 13, 2017 · 0 comments
Closed

Please Support Received Transaction Expedition #6020

dabura667 opened this issue May 13, 2017 · 0 comments

Comments

@dabura667
Copy link
Contributor

Anyone who is not following Copay issues, please see the same issue. #5102

"Child Pays for Parent" is a technical term that means "Spend some money to make a transaction you received confirm faster."

In a perfect world, every sender uses Copay and has a proper fee on their transaction, but some companies are cheap (like OKCoin withdrawals, still using a flat fee) and some companies just don't know anything (Some Bitcoin ATMs).

The response "well, just wait and maybe it will reverse itself or maybe it won't hmm idk let's just wait mmkay?" is not acceptable to people who are receiving maybe $50k or some other high amount.

It would be best to have a tool for those people to spend $1-2 (or more if fees keep increasing) to incentivise the miners to confirm the entire unconfirmed chain.

I currently have a PR open for insight-api (bitpay/insight-api#508) to make a simple end point to figure out how much extra fee is needed to add to CPFP a utxo. This could be made much more efficient if bitcore supported v0.13.0 or later of bitcoind because it allows getmempoolentry.

The UI being complicated is not an issue. It can be buried in an advanced menu. Opening the CPFP menu will scan all utxos for 0 confirmations && neededExtraFee > 0 (from my PR) and show them with one utxo per entry. The user could then tap a button that would gather all of them as inputs, create one output (maybe the next change address would be sufficient for use) and the fee for this transaction would be calculated, AND the needed extra fees for each parent would be calculated and added on to make the whole unconfirmed change consistent with the "Priority" setting (or the user's current setting... but it might not make sense to CPFP up to "Economy" etc...)

Electrum has a similar feature, right clicking an incoming transaction that's 0 confirms allows you to click CPFP and you will CPFP that one utxo in a new transaction to yourself.

Seeing all these new posts in the issues that could be solved by adding CPFP (and maybe RBF... but I am personally against RBF since you can use CPFP as long as there is a change utxo going back to yourself.) it makes me a little sad every time the response is "well, just wait. Sorry."

When we see an influx of "I lost my phrase" type issues, the UI is changed to try and encourage safe storage of backups.

Yet when we see an influx of "I received BTC that is never confirming" why is the response "wait and see?"

Sure there is a possibility that waiting it out might get confirmed in a few days, but some people would be willing to spend $1-2 to see it confirm in a few minutes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants