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

Taiga Wallet API #134

Open
6 tasks
bazzilic opened this issue Mar 7, 2023 · 2 comments
Open
6 tasks

Taiga Wallet API #134

bazzilic opened this issue Mar 7, 2023 · 2 comments
Labels

Comments

@bazzilic
Copy link
Contributor

bazzilic commented Mar 7, 2023

Taiga API for wallets.

  • createPtx() : Ptx Creates the initial partial transaction, spending user’s available assets and possibly creating some notes (intent notes or the desired assets directly). For every note created in the partial transaction, we need to include the nullifier key for the solvers to be able to spend them to balance the transaction
  • createEncData() Actually because nullifier keys stored in the notes are short-term, we don’t need a separate call for that and can put it inside the createPtx() call. Is this redundant then? @vveiln @XuyangSong
  • retrieveVP() Solvers need information about the VPs in order to be able to satisfy them efficiently. There was some design question around that, was it resolved? @vveiln @XuyangSong
  • createIntent() Intent is a data structure that contains partial transactions, VPs and other data that might be required. Each intent contains at least one partial transaction.
  • finalizeTxn() Trivial transactions (e.g., send tokens to someone) don’t need solving and can be finalized by the wallet itself thus saving solver fees.
  • ExecuteVP() Solving/finalizing locally might require execution of VP. Does it need to be exposed or it will be concealed by finalizeTxn()? -- request for comments on this one @vveiln @XuyangSong @Acentelles
@bazzilic bazzilic added the API label Mar 7, 2023
@XuyangSong
Copy link
Collaborator

createEncData() Actually because nullifier keys stored in the notes are short-term, we don’t need a separate call for that and can put it inside the createPtx() call. Is this redundant then?

I agree. We might not need this API. We would use verifiable encryption in VP, and the encrypted data would be part of the public inputs of the VP.

@XuyangSong
Copy link
Collaborator

retrieveVP() Solvers need information about the VPs in order to be able to satisfy them efficiently. There was some design question around that, was it resolved?

Not yet.
Solvers would get some plaintext of the (intent)notes to generate proofs when receiving the unbalanced partial transaction. We need a design to get the full vk and an understandable description of the (intent)vp from the compressed vk in the note.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants