ERC20-like token
Used as a local/static shape for deterministic artifact and drift checks.
Fixture harness
Local benchmark shapes for review-surface drift.
Fixtures give ArkheionX stable protocol shapes to test against. They are not real protocol audits. They are local/static benchmark inputs for deterministic artifact checks.
Purpose
Why fixtures exist.
A security review tool needs regression checks. If a tool claims to preserve review context, it should be able to regenerate known artifact shapes and detect when output changes unexpectedly.
The fixture harness exists to support that discipline: local inputs, expected snapshots, source fingerprints, and visible drift.
Fixture categories
Nine protocol shapes used for local review context.
Lending vault
Used as a local/static shape for deterministic artifact and drift checks.
Staking rewards
Used as a local/static shape for deterministic artifact and drift checks.
AMM swap
Used as a local/static shape for deterministic artifact and drift checks.
Oracle-dependent vault
Used as a local/static shape for deterministic artifact and drift checks.
Upgradeable proxy
Used as a local/static shape for deterministic artifact and drift checks.
Bridge message
Used as a local/static shape for deterministic artifact and drift checks.
Liquidation engine
Used as a local/static shape for deterministic artifact and drift checks.
Governance timelock
Used as a local/static shape for deterministic artifact and drift checks.
What the harness tracks
Inputs, outputs, and drift.
Fixture source Local benchmark input
Fingerprint Deterministic source identifier
Snapshot Expected review artifact output
Drift Difference between expected and regenerated output
Limitations
Fixtures are not safety proofs.
A passing fixture check does not prove a protocol is safe. It only supports confidence that the tool is producing expected deterministic artifact shapes for known local inputs.
Read safety model