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

Cash Accounts #15

Open
monsterbitar opened this issue Dec 31, 2018 · 3 comments
Open

Cash Accounts #15

monsterbitar opened this issue Dec 31, 2018 · 3 comments

Comments

@monsterbitar
Copy link

@monsterbitar monsterbitar commented Dec 31, 2018

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

@SpendBCH
Copy link
Contributor

@SpendBCH SpendBCH commented Jan 1, 2019

This looks very promising, will continue to review it.

Thank you! @GitCash 512 bits for @monsterbitar

@GitCash
Copy link

@GitCash GitCash commented Jan 1, 2019

Hey monsterbitar, user SpendBCH tipped you 512 bits in Bitcoin Cash ( ~ $0.0794 ).

Click here to claim it!

You can also add the "thumbs down" reaction to SpendBCH's comment above to prevent future tips.

@monsterbitar
Copy link
Author

@monsterbitar monsterbitar commented Mar 22, 2019

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 badgerwallet can be ready when the registration support gets implemented elsewhere.

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

Successfully merging a pull request may close this issue.

None yet
3 participants