MUSECHAIN CONTRACT AUDIT TOOL

Deterministic State-Diff for Zero-Value Muse Calls

Inspect how your smart contract storage shifts before and after any write call. Sample live variables with POST /v1/read, execute zero-gas agent calls with POST /v1/call, and verify delta changes with cryptographic precision.

⚡ Zero-Value Guarantee: Calls carry exactly 0 ETH. No private keys, gas fees, or passwords requested. Muses act through network-sponsored MuseCall accounts.

DiffMuse state diff interface visualization

Load Office Presets:

1. Contract Target & Verification

Verified on MuseScan

Contract Address (solc 0.8.28):

Contract Name: OfficeCounterLog

Compiler / Status: Solc 0.8.28 · ABI Verified

Explorer Link: View on MuseScan ↗

2. Read Sampler & Action Definition

POST /v1/read + /v1/call

Read Functions to Sample Before & After (JSON array or comma list):

Queried simultaneously via POST /v1/read at block height T0 and T1.

Write Action Method:

Arguments (JSON array):

Telemetry: Pre-Call vs Post-Call Storage Delta

Awaiting execution run...

Pre-Call State (T₀)

POST /v1/read

No pre-call sample loaded.

Click "Run State-Diff" or choose a preset to inspect initial variables.

Write Action & Events

POST /v1/call

No write transaction executed.

Calls carry 0 ETH. Network signs and relays on L3.

Post-Call State (T₁)

POST /v1/read

No post-call sample loaded.

Storage changes will highlight here in lime green delta boxes.

Musechain Zero-Value State-Diff Protocol

1. Free Read Queries

Each tracked accessor is called concurrently via POST /v1/read without spending gas. Responses are keyed to the contract's verified ABI definitions.

2. Zero-Value Call Account

Muses do not deploy raw private keys. Writes are routed through POST /v1/call, where the muse's factory-minted MuseCallAccount acts as msg.sender.

3. Atomic Non-Mutating Failure

If an assertion, custom error, or require condition fails, the EVM reverts. DiffMuse strictly preserves pre-state and marks the diff null to prevent ghost state displays.