Complete reference for mistc — the Mist smart contract compiler, linter, deployer, and debugging toolchain.

Installation

mistc is included in the Rivellum node distribution. To compile from source:

cargo build --release -p mistc

The binary is at target/release/mistc.

Commands

mistc compile — Compile to Bundle

Runs the full compilation pipeline and outputs a deployment bundle:

mistc compile counter.mist -o counter.bundle.json

The bundle contains the VIR program, PVI graph, metadata, and code hash — everything needed for on-chain deployment.

Flags:

• -o, --output <FILE> — Output path (default: stdout)

mistc build — Full Build with All Artifacts

Compiles and writes all intermediate artifacts to a directory:

mistc build counter.mist -o build/

Produces:

build/
├── counter.bundle.json    # Full deployment bundle
├── counter.pvi.json       # Standalone PVI graph
├── counter.analysis.json  # Static analysis report
└── counter.fees.json      # Fee breakdown

Flags:

• -o, --output-dir <DIR> — Output directory (default: build/)

mistc check — Syntax Check

Parses the source and reports syntax errors without full compilation:

mistc check counter.mist

Fast feedback for syntax issues (indentation, unknown keywords, unterminated strings).

mistc lint — Full Lint

Runs parse + type check + static analysis (everything except PVI lowering):

mistc lint counter.mist

Reports type errors, conservation violations, locked funds, and other static analysis issues. Use this as your primary development feedback tool.

mistc fmt — Format Source

Reformats a Mist file with canonical indentation:

# Preview formatted output
mistc fmt counter.mist

# Format in place
mistc fmt counter.mist --write

Flags:

• -w, --write — Overwrite the source file in place

mistc fees — Fee Analysis

Shows a detailed breakdown of deployment and execution fees:

# Human-readable output
mistc fees counter.mist

# Per-function analysis
mistc fees counter.mist --function increment

# JSON output
mistc fees counter.mist --json

Flags:

• --function <NAME> — Analyze fees for a specific function
• --json — Output as JSON

Fee tiers:

mistc parse — Dump AST

Outputs the parsed AST for debugging:

mistc parse counter.mist

mistc inspect — Inspect PVI Graph

Pretty-prints the PVI graph structure from a compiled bundle:

mistc inspect counter.bundle.json

Shows node types, edges, amounts, asset types, and flow structure.

mistc explain — Error Code Explainer

Displays a detailed explanation for any Mist error code:

mistc explain MIST_E_LOCKED_FUNDS
mistc explain UVL_F002
mistc explain FEE_W_HIGH_FEE

All error codes:

mistc deploy — Deploy Contract

Deploys a compiled bundle to the network:

mistc deploy counter.bundle.json
mistc deploy counter.bundle.json --rpc https://rpc.rivellum.network

Flags:

• --rpc <URL> — RPC endpoint (default: https://rpc.rivellum.network)

mistc call — Call Contract Function

Calls a function on a deployed contract:

mistc call <contract_id> increment '[]'
mistc call <contract_id> transfer '["0xabc...", 1000]'
mistc call <contract_id> get_count '[]' --rpc https://rpc.rivellum.network

Arguments:

• <contract_id> — The deployed contract's on-chain ID
• <function_name> — Function to call
• <args_json> — JSON array of arguments

Flags:

• --rpc <URL> — RPC endpoint

mistc receipt — Fetch Execution Receipt

Retrieves and displays an execution receipt:

mistc receipt <receipt_id>
mistc receipt <receipt_id> --pvi      # Include PVI graph
mistc receipt <receipt_id> --explain  # Explain any errors

Flags:

• --rpc <URL> — RPC endpoint
• --pvi — Include PVI graph in output
• --explain — If the receipt contains an error, explain it

mistc replay — Deterministic Replay

Replays an execution from a replay bundle to verify determinism:

mistc replay replay_bundle.json

The replay re-executes the contract with the same inputs and verifies that the PVI commitment, state root, and all other commitments match. Used for auditing and dispute resolution.

mistc repro-export — Export Reproduction Bundle

Creates a self-contained bundle for reproducing a specific execution:

mistc repro-export \
    --contract my_contract.mist \
    --receipt <receipt_id> \
    --rpc https://rpc.rivellum.network \
    -o repro_bundle.json

The output contains everything needed to replay: the contract source, execution receipt, host environment parameters, and account balances.

mistc attest — Sign Bundle

Signs a bundle with a Dilithium3 post-quantum key for proof-of-origin:

mistc attest my_contract.bundle.json \
    -k my_key.pem \
    -o my_contract.attested.json

mistc verify-bundle — Verify Attestation

Verifies the Dilithium3 signature on an attested bundle:

mistc verify-bundle my_contract.attested.json

mistc init — Scaffold New Project

Creates a new Mist project directory with a starter contract:

mistc init my_project

Generates:

my_project/
├── src/
│   └── main.mist
└── mist.toml (if applicable)

mistc test — Run Tests

Runs embedded tests in the current directory:

mistc test
mistc test ./src

Typical Development Workflow

# 1. Create project
mistc init my_defi_app
cd my_defi_app

# 2. Write contract
# Edit src/main.mist

# 3. Check syntax quickly
mistc check src/main.mist

# 4. Full lint (types + static analysis)
mistc lint src/main.mist

# 5. Review fees
mistc fees src/main.mist --json

# 6. Full build
mistc build src/main.mist

# 7. Inspect PVI graph
mistc inspect build/main.bundle.json

# 8. Deploy to testnet
mistc deploy build/main.bundle.json

# 9. Call functions
mistc call <contract_id> init '[]'
mistc call <contract_id> increment '[]'

# 10. Check receipt
mistc receipt <receipt_id> --pvi --explain

RPC API Endpoints

For programmatic deployment without the CLI:

Deploy Example

curl -X POST https://rpc.rivellum.network/v1/mist/deploy \
    -H 'Content-Type: application/json' \
    -d '{
        "bytecode": "<base64_encoded_bundle_json>",
        "sender": "0x1234..."
    }'

Call Example

curl -X POST https://rpc.rivellum.network/v1/mist/call/0xcontract_id \
    -H 'Content-Type: application/json' \
    -d '{
        "function": "transfer",
        "args": ["0xrecipient...", 1000],
        "sender": "0xsender..."
    }'