A controlled environment for onchain development.
Create the conditions your application needs. Iterate quickly. Reset when you need to. Move from an idea to a verified implementation without waiting on live network conditions.
Everything between an idea and a verified implementation.
Change the environment.
Not the outcome.
NOME makes experimentation repeatable. Define a condition, run it, inspect the result, reset, and try again.
- DEFINEDeclare accounts, assets, and starting state.
- RUNExecute transactions and contract calls.
- INSPECTRead state diffs, events, and traces.
- RESETReturn to any snapshot instantly.
- REPEATSame input, same outcome. Every time.
Built around how onchain systems actually behave.
NOME models the primitives your application depends on. Nothing is approximated away, so what you observe in an environment is what you should expect from the chain.
Accounts
Externally owned and contract accounts with balances, nonces, and roles you define explicitly.
account { address, balance, nonce, code? }Assets
Native and contract-defined assets with decimals, supply, and holders modeled as first-class state.
asset { standard, decimals, supply, holders[] }Transactions
Signed or environment-authorized transactions with realistic gas accounting, ordering, and receipts.
tx { from, to, value, data, gas, nonce }Contract interactions
Deploy, call, and trace contracts with full call stacks, reverts, and return data.
call { target, selector, args[], trace }State changes
Every write is captured as a structured diff you can inspect, compare, and roll back.
diff { slot, before, after, origin }Events
Emitted logs are indexed, decoded, and queryable across the full history of an environment.
event { signature, topics[], data, block }Network conditions
Block time, base fee, reorg depth, and latency are parameters, not accidents.
network { blockTime, baseFee, reorgDepth }
Reproducibility matters.
Reliable development requires environments that can be understood, repeated, and inspected. NOME is designed around deterministic workflows, explicit state, and observable outcomes.
Read the MethodologyInfrastructure should disappear into the workflow.
The best developer infrastructure does not compete for attention. It gives builders more control, fewer constraints, and a faster path from idea to execution.
Read the Manifesto