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
bcoin (https://github.com/bcoin-org/bcoin, https://bcoin.io/) is the backend full node and wallet used by Purse.io. They could be listed together or separately (or just one or the other). bcoin offers a range of options, but Purse has been configured with specific settings. I'm happy to make a PR to this repo with details but I'm not sure if the services explicitly need to be tested by an OpTech associate?
Here's the quick details:
SegWit:
bcoin and Purse support SegWit in all forms: native, nested, send and receive.
Purse default receive address is bech32 with option for nested.
Change address type is either legacy or bech32 depending on wallet witness setting, Purse always uses bech32 for change.
bcoin and Purse reject RBF transactions by default (they do not enter the mempool or wallet until confirmed) meaning they will "show replaced" but not "show original" assuming the replacement is not itself signaling RBF.
The wallet by default can not send replaceable transactions or replace RBF transactions.
Mempool replacement for the bcoin full node is in review: BIP125: Enable replace-by-fee in mempool bcoin-org/bcoin#811. After merge we'll begin work on adding RBF options to the wallet although RBF will likely remain rejected by Purse, since deposits aren't credited before confirmation anyway.
Screen shots:
Purse -- illustrating bech32 and nested deposit addresses:
bcoin -- from our API docs illustrating legacy and SegWit wallet account types with receive, change, and nested addresses:
The text was updated successfully, but these errors were encountered:
Hey @pinheadmz ! Thanks for opening this. Would be great to get Purse.io in the matrix.
It is not required that an "Optech" person execute the testing and open the PR. Although usually as part of review, if its easy enough, I test myself too.
We are considering a "libraries" section for the future potentially, but not yet. So Id recommend a PR for Purse and not bcoin for now.
Let me know if you plan to open the Purse Compatibility Matrix PR.
bcoin (https://github.com/bcoin-org/bcoin, https://bcoin.io/) is the backend full node and wallet used by Purse.io. They could be listed together or separately (or just one or the other). bcoin offers a range of options, but Purse has been configured with specific settings. I'm happy to make a PR to this repo with details but I'm not sure if the services explicitly need to be tested by an OpTech associate?
Here's the quick details:
SegWit:
witness
setting, Purse always uses bech32 for change.RBF:
Screen shots:
Purse -- illustrating bech32 and nested deposit addresses:
bcoin -- from our API docs illustrating legacy and SegWit wallet account types with receive, change, and nested addresses:
The text was updated successfully, but these errors were encountered: