Create account

2086d · memo
I've released the #CashID specification (https://www.yours.org/content/introducing-cashid--an-open-protocol-for-authentication-with-optional-e3df11d498e6). Would love to see it on memo.
3 / 28 4
102,000
arruah
replied 2083d
I can translate to Russian and Kazakh.
4
2,443
anarchovegan
replied 2083d
I can translate anything into gibberish.
4
1,266
Metalbrushes_Tattoo
replied 2082d
I am fluent in pig Latin 😜
2
replied 2082d
I'm fluent in Rachet!!!!!!!!!!!
2
anarchovegan
replied 2082d
Well this is just a racket now ;)
1
555
replied 2082d
Rachet jackets impounded latches. Spaghetti fluid improved movements. #RatchetNonsense
1
anarchovegan
replied 2082d
Gibberish translating - contagious! :D
I prefer bi-directional ratchets with a closed spaghetti loop. Impounding lachets does nothing for the ricochet.
selami yanık
replied 2083d
A Kazakh BCH'er?
3
666
arruah
replied 2083d
Yes, Almaty.
1
555
replied 2083d
That would be useulf. The spec is in gitlab (https://gitlab.com/cashid/protocol-specification/blob/master/README.md).

Are you familiar with Git and MarkDown?
arruah
replied 2083d
Sure.
replied 2082d
Good. Let me know if you have any questions.
1
546
replied 2083d
Looks like a good spec! There is a MIP for delegated keys in the works that could potentially use this. https://github.com/memocash/mips/blob/master/mip-0003/mip-0003.md
2
10,999
replied 2083d
Just to be make sure I understand this correctly:

any memo-implementation creates child keys, puts a request on-chain that if signed by the users master key, links it to user identity
1
replied 2083d
The user could then post a revocation transaction on-chain that delinks the child key at a given blockheight.
1
replied 2083d
Final worklow, with memo.cash as example:

user visits memo.cash. scans CashID code, logs in. memo.cash create child keys, user use CashID to sign them, memo.cash can now post for user
6
4,666
replied 2083d
If I understood this right, then my only complaint on memo.cash (that I am not in control of my own keys) is finally solved - and with a userfriendly design!
6
1,666
replied 2083d
Hey will this allow me to use my vanity gen addresses on Memo.cash? I don't ever want to upload their private keys.
2
replied 2083d
with this, you can use your vanity address as your identity. your posts won't be made by it directly, but linked to it. memo would have their own child keys, which you sign to approve.
2
1,000
replied 2082d
Ah now I get it.
1
replied 2083d
Thank you, I read that MIP and it's a perfect example of how a reputation protocol complementing an authentication protocol should work.
1
1,000
replied 2083d
What additions/extension to CashID is needed for it to be used in this way? Is the "sign" action (a=sign&d=data) sufficient?

I'm thinking that custom memosign actoin is better UX.
replied 2082d
I'm not sure yet, but probably a custom action like you said. Delegated keys is something I was hoping to start working on in next few months. Once I dig in I'll know more.
replied 2082d
While for a custom action, the identity manager / wallet could both sign, build and broadcast the TX, then return TXID in response.

For compatibility, offer a generic solution as well
replied 2082d
Based on MIP, there is two actions sign: one that grant, and one that revoke, permission.

Generic a=sign&d=data can be used, but memo client would need to build and broadcast TX.
replied 2082d
So you basically reinvented X509?
replied 2082d
At first, I just want to say "no, it's not". Then I read the first part of the X509 wikipedia page and there are similarities. I guess it comes down to what "basically" means here.
replied 2077d
I still dont like using DSA for something it's not designed for.


About Privacy Terms Stats