You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 20, 2020. It is now read-only.
This plugin does not work well for bitcoin sent from non-Coinbase wallets.
The Coinbase sandbox also doesn't work for testing this with API v1, so this plugin is dead. I have no idea if it works with Coinbase accounts as it rejects payments sent to the same account.
Edit: I got it to work, and overpayments were listed. However Coinbase didn't react to these payments in time, and the orders expired. One payment to 11 minutes to confirm, and the other one took well over 15 minutes. When it works it says "received payment, waiting for confirmation", and confirms it without actual confirmation on the blockchain.
Edit 2: All came finally. Perhaps the bug is simply Coinbase doesn't look for transactions under a certain size. There should be coded 5.4 uBTC minimum as well by coinbase on the server side. There is of course no way to send dust unfortunately. I will test the overpayment.
Edit 3: Well panic averted, not so massive of an issue as the plugin fails with amounts under 5.4 uBTC even if you overpay. That's the bug. No big deal since this isn't going to happen in production. It's a flaw of bitcoin in general, because it excludes it's use for micropayments.
Ranting Conclusion
Generating addresses in a deterministic manner is not the greatest idea for all solutions. It would be better to attach a global address, or group of address you manually generate to associate with products. Sure, people would be able to see what has been paid, but for many reasons you want this transparency. Deterministic addresses lead to panic when things go wrong. It's much harder to trace an infinite number of addresses down when accounting forensically.
Hoping for a v2 API release to make testing easier.
The text was updated successfully, but these errors were encountered:
This plugin does not work well for bitcoin sent from non-Coinbase wallets.
The Coinbase sandbox also doesn't work for testing this with API v1, so this plugin is dead. I have no idea if it works with Coinbase accounts as it rejects payments sent to the same account.
Edit: I got it to work, and overpayments were listed. However Coinbase didn't react to these payments in time, and the orders expired. One payment to 11 minutes to confirm, and the other one took well over 15 minutes. When it works it says "received payment, waiting for confirmation", and confirms it without actual confirmation on the blockchain.
One payment is still in space. Who knows where the money is, but it's not in my Coinbase account. https://blockchain.info/tx-index/9afaa5021484bb23c94ab3a5f0e0a7297c9a8e0186295eeb2b68c5c8f274e8f4
Edit 2: All came finally. Perhaps the bug is simply Coinbase doesn't look for transactions under a certain size. There should be coded 5.4 uBTC minimum as well by coinbase on the server side. There is of course no way to send dust unfortunately. I will test the overpayment.
Edit 3: Well panic averted, not so massive of an issue as the plugin fails with amounts under 5.4 uBTC even if you overpay. That's the bug. No big deal since this isn't going to happen in production. It's a flaw of bitcoin in general, because it excludes it's use for micropayments.
Ranting Conclusion
Generating addresses in a deterministic manner is not the greatest idea for all solutions. It would be better to attach a global address, or group of address you manually generate to associate with products. Sure, people would be able to see what has been paid, but for many reasons you want this transparency. Deterministic addresses lead to panic when things go wrong. It's much harder to trace an infinite number of addresses down when accounting forensically.
Hoping for a v2 API release to make testing easier.
The text was updated successfully, but these errors were encountered: