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

implicit account VP #8

Closed
Tracked by #73
tzemanovic opened this issue May 7, 2021 · 2 comments · Fixed by #592
Closed
Tracked by #73

implicit account VP #8

tzemanovic opened this issue May 7, 2021 · 2 comments · Fixed by #592
Assignees
Labels

Comments

@tzemanovic
Copy link
Member

tzemanovic commented May 7, 2021

Add a VP for implicit account addresses. This should be used for all the implicit accounts (related to anoma/anoma#186)

┆Issue is synchronized with this Asana task by Unito

@tzemanovic
Copy link
Member Author

We'll need a way to "reveal" a public key for an implicit account (write its public key in its account's sub-space in the ledger). Implicit account has to have its public key revealed in order to authorize actions on itself. For example, the DKG "wrapper" Tx will need to be signed by the implicit source account address (that pays for the wrapper gas).

@tzemanovic
Copy link
Member Author

We'll need a way to "reveal" a public key for an implicit account

Currently, we have the field pk: PublicKey inside the struct WrapperTx. We could change the field to use e.g.:

enum AddressOrPk { Addr(Address), Pk(PublicKey) }

and then for

  • Pk write the PK into the storage of the address derived from the PK (ignore if it's already set)
  • Addr use the previously revealed PK from storage (fail if it's not been revealed)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: Tested in Devnet
Development

Successfully merging a pull request may close this issue.

2 participants