This repository contains the Miden client, which provides a way to execute and prove transactions, facilitating the interaction with the Miden rollup.
The Miden client is still under heavy development and the project can be considered to be in an alpha stage. Many features are yet to be implemented and there is a number of limitations which we will lift in the near future.
The Miden client currently consists of two components:
miden-clientlibrary, which can be used by other project to programmatically interact with the Miden rollup.miden-clientbinary which is a wrapper around the library exposing its functionality via a simple command-line interface (CLI).
The client's main responsibility is to maintain a partial view of the blockchain which allows for locally executing and proving transactions. It keeps a local store of various entities that periodically get updated by communicating with the node.
Before you can build and run the Miden client CLI, you'll need to make sure you have Rust installed. Miden client v0.1 requires Rust version 1.75 or later.
You can then choose to run the client CLI using cargo, or install it on your system. In order to install it, you can run:
cargo install --path .This will install the miden-client binary in your PATH, at ~/.cargo/bin/miden-client.
For testing, the following way of installing is recommended:
cargo install --features testing --path .The testing feature allows mainly for faster account creation. When using the the client CLI alongside a locally-running node, you will want to make sure the node is installed/executed with the testing feature as well, as some validations can fail if the settings do not match up both on the client and the node.
Additionally, the client supports another feature: The concurrent flag enables optimizations that will result in faster transaction execution and proving.
After installing the client, you can use it by running miden-client. In order to get more information about available CLI commands you can run miden-client --help.
The CLI can be configured through a TOML file (miden-client.toml). This file is expected to be located in the directory from where you are running the CLI. This is useful for connecting to a specific node when developing with the client, for example.
In the configuration file, you will find a section for defining the node's endpoint and the store's filename. By default, the node will run on localhost:57291, so the example file defines this as the RPC endpoint.
- This guide assumes a basic understanding of the Miden rollup, as it deals with some of its main concepts, such as Notes, Accounts, and Transactions. A good place to learn about these concepts is the Polygon Miden Documentation.
- It also assumes that you have set up a Miden Node that can perform a basic local transaction.
- Currently, the client allows for submitting locally-proven transactions to the Miden node. The simplest way to test the client is by generating accounts via the genesis file.
- For this example, we will make use of 1 faucet account and 2 regular wallet accounts, so you should set your node's
tomlconfig file accordingly. We will refer to these accounts as having IDsregular account ID Aandregular account ID Bin order differentiate them. - Once the account files have been generated, make sure the node is running. If the node has some stored state from previous tests and usage, you might have to clear its database (
miden-store.sqlite3). - The client should be configured to use the running node's socket as its endpoint as explained in the previous section.
- For this example, we will make use of 1 faucet account and 2 regular wallet accounts, so you should set your node's
In order to execute transactions and change the account's states, you will first want to import the generated account information by running miden-client account import:
miden-client account import <path-to-accounts-directory>/*.macThe client will then import all account-related data generated by the node (stored as *.mac files), and insert them in the local store. The accounts directory should be the one generated by the node when running the make-genesis command. You can now list the imported accounts by running:
miden-client account listAs briefly mentioned in the Overview section, the client needs to periodically query the node to receive updates about entities that might be important in order to run transactions. The way to do so is by running the sync command:
miden-client syncRunning this command will update local data up to the chain tip. This is needed in order to execute and prove any transaction.
Since we have now synced our local view of the blockchain and have account information, we are ready to execute and submit tranasctions. For a first test, we are going to mint a fungible asset for a regular account.
miden-client tx new mint <regular-account-ID-A> <faucet-account-id> 1000This will execute, prove and submit a transaction that mints assets to the node. The account that executes this transaction will be the faucet as was defined in the node's configuration file. In this case, it is minting 1000 fungible tokens to <regular-account-ID-A>.
This will add a transaction and an output note (containing the minted asset) to the local store in order to track their lifecycles. You can display them by running miden-client tx list and miden-client input-notes list respectively. If you do so, you will notice that they do not show a commit height even though they were submitted to the operator. This is because our local view of the network has not yet been updated. After updating it with a sync, you should see the height at which the transaction and the note containing the asset were committed. This will allow us to prove transactions that make use of this note, as we can compute valid proofs that state that the note exists in the blockchain.
After creating the note with the minted asset, the regular account can now consume it and add the tokens to its vault. You can do this the following way:
miden-client tx new consume-note <regular-account-ID-A> <input-note-ID>This will consume the input note identified by its ID, which you can get by listing them as explained in the previous step. You will now be able to see the asset in the account's vault by running:
miden-client account show <regular-account-ID-A> -vSome of the tokens we minted can now be transferred to our second regular account. To do so, you can run:
miden-client sync # Make sure we have an updated view of the state
miden-client tx new p2id <regular-account-ID-A> <regular-account-ID-B> <faucet-account-ID> 50 # Transfers 50 tokens to account ID BThis will generate a Pay-to-ID (P2ID) note containing 50 assets, transferred from one regular account to the other. If we sync, we can now make use of the note and consume it for the receiving account:
miden-client sync # Make sure we have an updated view of the state
miden-client tx new consume-note <regular-account-ID-B> # Consume the noteThat's it! You will now be able to see 950 fungible tokens in the first regular account, and 50 tokens in the remaining regular account:
miden-client account show <regular-account-ID-B> -v # Show account B's vault assets (50 fungible tokens)
miden-client account show <regular-account-ID-A> -v # Show account A's vault assets (950 fungible tokens)All state is maintained in store.sqlite3, located in the same directory where the client binary is. In case it needs to be cleared, the file can be deleted; it will later be created again when any command is executed.
This crate has both unit tests (which can be run with cargo test) and integration tests. For more info on integration tests, refer to the integration testing document
This project is MIT licensed.