Replying to Avatar Vitor Pamplona

They are messing with you. You will never be able to use a SHA-256 hash of some content inside the content itself. Making the URL hash match the event id hash, when the URL is inside the event, is like having Bitcoin's proof of work at the maximum difficulty possible. Not even the hash rate of the entire bitcoin network can solve that for you.
Avatar
BTCClock 2y ago

Vitor: What about extra layer to adopt mainstream? Today it's pubkey/private key. What about "brainwallet" way? Example: email and password. It would guarantee unique "brain wallet" key. User would not need to know/see that it creates a private/Public key.

Reply to this note

Please Login to reply.

Discussion

Avatar
Vitor Pamplona 2y ago

Impossible without centralizing the conversion between user + password into the private key.

Just to give you an idea, without centralizing it, the "e-mail" would have to use 22 words to represent it. It would be VERY long.

Avatar
BTCClock 2y ago

No. Use same logaritm as brain wallets use. Example: https://brainwalletx.github.io/

There is no lower or upper limit to create a private/public key. You can create a key pair using a single space even.

Also, you could support this in Amethyst alone and let the user see/get his private key after login, to be used in other clients.