Miden Wallet features first iteration - DevCon 2024

[Dominik1999]

Goal is to showcase the Miden wallet at DevCon 2024

Now that we have the WebClient crate, the next step is to build the Miden wallet. The goal is to showcase the wallet during this year's Miden event in Bangkok at DevCon. The target audience is selected investors and builders who might have heard about Miden but have never used it or used any blockchain leveraging client-side proofs.

Ideally, the audience would download and use the wallet themselves rather than have us show a demo.

Minimal set of features

• Connect to a website

  • the wallet should be able to connect to the faucet (https://testnet.miden.io/) and mint tokens. Ideally, minting and consumption should only be one click even though it is two transactions
  • (maybe we need the wallet to connect to one of our Pioneer's projects. But maybe they also use the SDK. Let's discuss with them directly)

• Sync with the Miden chain:

  • ideally, this happens in the background querying notes with the predefined tag
  • set a list of tags users might be interested in (in Miden, note discovery works with note tags)

• Send assets:

  • the user must be able to input the recipient account ID or read a QR code
  • previously used account IDs should be stored
  • for standardized notes, a user should be able to choose between private and public notes
  • exporting notes, when private notes are used, the user should be able to import notes *.mno via a button

• Receive assets:

  • standardized notes (P2ID, P2IDR) could be executed directly or after a short confirmation by the user
  • complex and custom notes (SWAP, custom note scripts), should be executed only after showing the user what happens to the account if executed. The Rust client already has this feature
  • importing notes, when private notes are used, the user should be able to import notes *.mno via a button

• Proving:

  • all wallet transactions should be local (client-side) proofs

  • if possible, the wallet should use the WebGPU implementation from miden-gpu

    (I am not sure how fast proving will be, but if it is more than 5s, even with WebGPU, we should add another feature here: The ability to delegate proving)

• UX:

  • the wallet should show all tokens by their name (Miden should provide a token mapping)
  • like in MetaMask or Coinbase wallet, the user should be able to expand the view

Features cool to have (we can spec those out if necessary)

• Show account's storage
• Show account's code
• Private P2P network (maybe WebRTC) to send private note data to contacts
• Delegate proving

Underlying requirements to the Miden client, base, or Miden VM

Please let us know.

Current design

Figma files (https://www.figma.com/design/JFMGH5tN9cW4UUY0O9Ewmu/Miden-Wallet-0.1?node-id=9420-22495&t=FOfkaM6YS93IDToB-0).

[bobbinth]

Great writeup!

the wallet should be able to connect to the faucet (https://testnet.miden.io/) and mint tokens. Ideally, minting and consumption should only be one click even though it is two transactions

It would be interesting to discuss how this will work. For example, I wonder if this could be as simple as registering MIME types for Miden notes and then when a given page produces files with this type, the wallet can somehow intercept them and import the notes.

If this methodology works, we could try to do something similar for transaction requests - e.g.,:

1. The user interacts with the page (in some arbitrary way) and clicks something.
2. At this point, the page generates a transaction request file.
3. The wallet catches this file and kicks off a workflow to fulfill the transaction request (we have something similar in Rust CLI).
4. The user either accepts or rejects the resulting transaction.
5. The result of the action is somehow communicated back to the page.

[julian-demox]

Hi @Dominik1999

Thanks again for typing this up. Here's our understanding and goal for where the Wallet will be by Devcon:

• Sync
  • Public
    • Sync, provide UI for notes, consume button
• Send
  • Public
    • Ability to configure:
      • An address
      • The amount of the asset
      • Recall height
• Receive
  • Public
    • Show a list of notes that are available for user to consume, provide consume button
    • There will be a list of all the notes you can consume. This list will also include any note that was P2IDR
    • If block height hasn't been hit, then we display some sort of error if the user tries to consume
    • If it has been hit, then user can recall
    • Once the note has been consumed, remove from the list
• Sign up flow
  • No seed phrase, users will set a password
  • There will be no account import / export mechanism for Devcon

We'll have an updated Figma by EOW. Please let us know if we can provide clarity on any of the points!

[julian-demox]

Spoke with @Dominik1999 , testnet miden-node will be merged to main in two weeks. In the meantime we are working with the latest version of miden-node at any given time to ensure maximal compatibility come Devcon

[julian-demox]

Latest figma: https://www.figma.com/design/fOiMxomwT3G12gfrrmSTVy/Miden-Wallet---WIP?node-id=9420-22495&node-type=canvas

[bobbinth]

Looks great! Thank you! A couple of minor questions/comments:

Home screen

In the "Home" screen, I think the below is meant to be a list of assets rather than accounts, right?

If so, I'm not sure it is relevant whether the asset was minted by a public or non public faucet. At the same time, the asset ticker (i.e., "MIDEN") should probably be the main piece of info and maybe it is the one that should be in bold font.

Recall height

One the screen where we specify recall height "How maybe blocks?" should probably be "How many blocks?"

In the future, this should probably be a default setting for the wallet which applies applies automatically during sending (but the user has the option to turn it off).

Claiming notes

When claiming notes, I'd probably change "Waiting for claim" to "Ready to claim" to make it clear that the notes are ready to be consumed. It would also be great to have an option to "Claim all" or something like that - but maybe that's for the future.

Also for the future, it would be great to have a setting to claim notes automatically (i.e., without user actions). There could be a number of ways to configure this - e.g., automatically claim notes with MIDEN asset if the amount is under some threshold.

Transaction history

This is also for the future, but would be great to be able to view transaction history for an account (e.g., which notes were sent out and which notes have been received).

[DevStrategist]

@bobbinth Good Catch. We have updated the Figma with your recommendations. Please let me know if you have any other feedback.

[Dominik1999]

Looks great indeed. I am looking forward to the first iteration!

Just a couple of questions:

Token Mapping:

Do you use the same token mapping as the Rust client?

Recall height:

When you prompt the user to type in a recall height, does the user know the current block height or is the field to type the number of blocks?

If the latter, maybe show in the second screen also not the recall height (absolute block number), but the number util the block height is reached?

Whitelist receiving:

As also Bobbin mentioned, in the future, it would be cool to have a whitelist of addresses. Notes from those addresses I don't need to claim but this happens automatically.

Delegated Proving:

Outside of the Figma design questions, we should get delegated proving into the wallet for DevCon. So, as a default for now, all wallets should not create the proof in the browser itself but use a dedicated machine.