Rust Sdk Patterns

Cargo.toml for notes: See increment-note/Cargo.toml for the required miden deps, cross-component dependencies, wit deps, and project-kind = "note-script".

Transaction Script (#[tx_script])

One-off logic executed in the context of an account. Used for initialization, admin operations, etc.

#![no_std]
#![feature(alloc_error_handler)]
use miden::*;
use crate::bindings::Account;

#[tx_script]
fn run(_arg: Word, account: &mut Account) {
    account.initialize();
}

Cargo.toml: Same as account but with project-kind = "tx-script".

Storage Types

Storage keys are always Word (4 Felts). Use Word::from_u64_unchecked(a, b, c, d) or Word::from([f0, f1, f2, f3]).

Native Function Modules

Asset Handling

Fungible asset Word layout: [amount, 0, faucet_suffix, faucet_prefix]

// Access asset amount
let amount = asset.inner[0];

// Add asset to account vault
native_account::add_asset(asset);

// Remove asset from account vault
native_account::remove_asset(asset.clone());

P2ID Output Note Creation

To send assets to another account, create a P2ID (Pay-to-ID) output note:

fn create_p2id_note(&mut self, serial_num: Word, asset: &Asset,
                     recipient_id: AccountId, tag: Felt, note_type: Felt) {
    let tag = Tag::from(tag);
    let note_type = NoteType::from(note_type);
    let script_root = Self::p2id_note_root(); // Hardcoded P2ID script digest

    // P2ID inputs: [suffix, prefix] of recipient
    let recipient = Recipient::compute(serial_num, script_root,
        vec![recipient_id.suffix, recipient_id.prefix]);

    let note_idx = output_note::create(tag, note_type, recipient);
    native_account::remove_asset(asset.clone());
    output_note::add_asset(asset.clone(), note_idx);
}

Note Inputs

Notes receive data via inputs (Vec<Felt>), accessed with active_note::get_inputs():

let inputs = active_note::get_inputs();
// Parse: Asset = inputs[0..4], serial_num = inputs[4..8], tag = inputs[8], type = inputs[9]
let asset = Asset::new(Word::from([inputs[0], inputs[1], inputs[2], inputs[3]]));
let serial_num = Word::from([inputs[4], inputs[5], inputs[6], inputs[7]]);

Cross-Component Dependencies

To call another component's methods from a note or tx script, two Cargo.toml sections are needed. See increment-note/Cargo.toml for a working example showing both [package.metadata.miden.dependencies] and [package.metadata.component.target.dependencies].

Then import the bindings in your Rust code. See increment-note/src/lib.rs line 13 for the import pattern: use crate::bindings::miden::target_component::target_component;

Common Type Conversions

// Felt from integer
let f = felt!(42);
let f = Felt::new(42);
let f = Felt::from_u32(42);
let f = Felt::from_u64_unchecked(42);

// Word from Felts
let w = Word::from([f0, f1, f2, f3]);
let w = Word::from_u64_unchecked(0, 0, 0, 1);
let w = Word::new([f0, f1, f2, f3]);

// Felt to u64 (for comparisons and arithmetic safety)
let n: u64 = f.as_u64();

No-std Requirements

Every contract file must start with #![no_std] and #![feature(alloc_error_handler)]. See any contract in contracts/ for the pattern.

If you need heap allocation (Vec, String, etc.):

extern crate alloc;
use alloc::vec::Vec;

Validation Checklist

• #![no_std] and #![feature(alloc_error_handler)] at top of every contract
• crate-type = ["cdylib"] in Cargo.toml
• Correct project-kind in [package.metadata.miden]
• Cross-component deps in both [package.metadata.miden.dependencies] and [package.metadata.component.target.dependencies]
• Felt arithmetic validated before subtraction (see rust-sdk-pitfalls skill)
• Felt comparisons use .as_u64() (see rust-sdk-pitfalls skill)