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

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

Comments

Projects
None yet
5 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

@cculianu

This comment has been minimized.

Copy link
Collaborator

cculianu commented Dec 12, 2018

I think this is a great idea. I looked quickly at the spec and it's pretty simple and solid (simple is the best, quite often). Thanks for posting this.

I would like EC to support this when it's finalized at some point.

@cculianu

This comment has been minimized.

Copy link
Collaborator

cculianu commented Dec 12, 2018

It would probably need ElectrumX server-side support to be able to refer to people by the short-hand notation.. I think. And to also be able to do reverse lookups of Address -> Label (short or long).

Not a huge deal -- i think the ecosystem needs this. It's 1 step towards easier, more human friendly adoption.

@markblundeberg

This comment has been minimized.

Copy link
Collaborator

markblundeberg commented Dec 12, 2018

I love the protocol but I'm also not hot on the 'account' terminology. Too easy to misunderstand for normal folks, since bitcoin doesn't have accounts. 'Cash Nick' was an option in your poll, wasn't it?

@cculianu why would reverse lookups be needed, I'm curious? (they wouldn't be unique in general, especially not if I register the same address multiple times)

@cculianu

This comment has been minimized.

Copy link
Collaborator

cculianu commented Dec 12, 2018

Hmm. Yeah "Account" could be misleading since it has baggage as a term in that it means something else in other domains. Whereas a new term like "Cash Nick" that has no baggage might be ideal.

@cculianu

This comment has been minimized.

Copy link
Collaborator

cculianu commented Dec 12, 2018

Oh hey @markblundeberg that second message about ledgers ended up in the wrong issue. Ha ha. I didn't mean it!

@fyookball

This comment has been minimized.

Copy link
Collaborator

fyookball commented Dec 19, 2018

I support the Cash handles idea

@emergent-reasons

This comment has been minimized.

Copy link

emergent-reasons commented Feb 9, 2019

FYI pycashaccount now has reasonably well tested python code for making cash account op return data for p2pkh, p2sh and bip47 payment codes. Anyone working on this issue is welcome to use the library or the code itself.

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