-
Notifications
You must be signed in to change notification settings - Fork 324
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
Cash Account Integration #34
Comments
If you have questions or want to chat for a bit with other developers working on this, feel free to join this discord chat: https://discord.gg/9kACN9t |
We are now several months into this project, there exist multiple lookup servers (written in javascript, go and c#), there exist a handful of websites around it and a small number of wallets have implemented send-support. The main issue that is still left to be resolved is creating and agreeing on a resuable address format so that we can retain privacy while still having userfriendly names, but I still feel that implementing sending support is something that should be a higher priority. I understand if you'd be hestitant to implementing registration support at the time being, given that address reuse is a bad practice - but ematiu from copay is working together with others to create a standardized implementation of peter todds stealth addresses that would allow us to keep the privacy. Please do not pass up this opportunity to build the user interfaces and send-support so that breadwallet can be ready when the registration support gets implemented elsewhere. |
courtesy of @emergent-reasons there is tests available (https://gitlab.com/cash-accounts/specification/blob/master/TEST.md) to help ensure a good integrity when implementing cashaccount support. If there is still anything that is missing or needing, please let us know. |
Is this the right place to discuss implementing CashAccounts for BitcoinCash in the BRD wallet? |
I am currently working on a specification for on-chain aliases that look like this: James#577821; to help convey payment information in a more convenient manner, particulary in verbal contexts.
The specification has undergone reasonable peer-review so far (by wallet developers, token developers, coinbase engineeers) but more feedback is always welcome.
Here's a link to the draft spec: https://gitlab.com/cash-accounts/specification/blob/master/SPECIFICATION.md
The text was updated successfully, but these errors were encountered: