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 #180

Open
monsterbitar opened this Issue Dec 12, 2018 · 4 comments

Comments

Projects
None yet
2 participants
@monsterbitar
Copy link

monsterbitar commented Dec 12, 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

@monsterbitar

This comment has been minimized.

Copy link
Author

monsterbitar commented Dec 14, 2018

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

@swansontec

This comment has been minimized.

Copy link
Contributor

swansontec commented Dec 14, 2018

Ah, I'm glad to see an open specification for this type of thing. The HandCash $handles system was completely centralized so we weren't interested in integrating that. This specification is simple and on-chain, which makes it much better.

On the flip side, Edge has publicly committed to supporting the FIO project. This means we will be integrating a handle system into the wallet eventually. I'll see if we can architect that work in a more generic way, so we could include not only FIO handles, put also possibly Cash Accounts and Ethereum Name Service names. I don't know if our agreement with FIO is exclusive or not.

@monsterbitar

This comment has been minimized.

Copy link
Author

monsterbitar commented Dec 14, 2018

Interesting to see that there are more approaches I was not aware of.

If you end up supporting multiple systems, cash accounts has a regexp-identifieable form that might allow them to be used in the same user interface as other handles - if the concurrent systems don't have collisions in the naming structure.

If it is a requirement for getting support in wallets, I would willing to add a prepending identifier to further make the name unique among participants so that you can detect which system to use based on the user input available.

Public release of the CashAccounts is intended for the 10-year anniversary of the genesis block (jan 3). Feel free to join us on discord to discuss what requirements edge wallet might have and how we best can accomodate your needs.

@monsterbitar

This comment has been minimized.

Copy link
Author

monsterbitar commented Jan 2, 2019

a beta of the system is now live at https://www.cashaccount.info/ and tomorrow the finalized v1.0 version of the spec will be released.

Feel free to test out and give me feedback on if there's anything wallet-related I could do to help.

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