0xMiden/protocol

Split `$kernel::account` into sub modules

Open

#2,146 opened on Dec 8, 2025

View on GitHub
 (4 comments) (1 reaction) (0 assignees)Rust (139 forks)github user discovery
good first issuekernels

Repository metrics

Stars
 (123 stars)
PR merge metrics
 (Avg merge 5d 11h) (110 merged PRs in 30d)

Description

We should refactor $kernel::account module into sub modules.

this file has become pretty huge - we should probably split this up into multiple files - e.g.,:

  • asm/kernel/transaction/lib/account/mod.masm
  • asm/kernel/transaction/lib/account/code.masm
  • asm/kernel/transaction/lib/account/storage.masm
  • asm/kernel/transaction/lib/account/vault.masm
  • maybe something else?

Originally posted by @bobbinth in https://github.com/0xMiden/miden-base/pull/2025#discussion_r2596181154

All storage related procedures can go into storage.masm, vault-related ones in vault.masm and code-related ones in code.masm. The other procedures working with account and storage commitment, nonce, data loading during prologue can probably stay in mod.masm.

This makes sense to do after #2025 at the earliest, though even better after the account procedure info follow-up was done, since this will again touch a bunch of account internals.

Contributor guide

Research direction
Review the current `$kernel::account` module structure and split it into `mod.masm`, `code.masm`, `storage.masm`, and `vault.masm` as suggested. Ensure all procedures are correctly categorized and imports are updated.
Tech stack
rust
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30