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

Address with Base58Check #43

Closed
wanseob opened this issue Aug 3, 2020 · 1 comment
Closed

Address with Base58Check #43

wanseob opened this issue Aug 3, 2020 · 1 comment
Labels
spec about specification

Comments

@wanseob
Copy link
Member

wanseob commented Aug 3, 2020

Is your feature request related to a problem? Please describe.

By the issue #34, a Zk account will have 64 bytes public address data which is a set of
(P, N) where P is poseidon(p*G, n) and N is n*G. (p is spending key and n is nullifier seed)

In this context, Base58Check is a good option to shorten the address for the readability.

P: 32bytes = poseidon(p*G, n)
N: 32bytes = encode(n*G)
checksum: 4bytes = keccak256(P, N)
totalBytes: 68 bytes = P + N + checksum
address = base58(totalBytes)

Describe the solution you'd like
N/A

Describe alternatives you've considered
Base58 without checksum

Additional context
#34

@wanseob wanseob added the spec about specification label Aug 3, 2020
@wanseob wanseob added this to the Nullifier updates milestone Aug 3, 2020
@wanseob
Copy link
Member Author

wanseob commented Aug 16, 2020

closed by #44

@wanseob wanseob closed this as completed Aug 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec about specification
Projects
None yet
Development

No branches or pull requests

1 participant