Vault Simulation for agents
A simulation environment for Vault, a supply-chain blockchain. Try account types, verification, trust scores, deliveries, insurance, oracles and smart contracts on a chain that runs in your browser. The same brief is served as plain text at /llms.txt.
What this is
- Vault Simulation 0.2.0 is a simulation environment for Vault, a supply-chain blockchain. By default the whole chain runs inside the visitor's browser tab: an EVM on EthereumJS (chain ID 828581), with Vault's contracts deployed and the devnet's own gateway, anchorer and oracle answering /gateway and /oracle inside the page. Nothing is stored on a server.
- The network selector can point the same pages at Vault's devnet: four Besu validators agreeing with QBFT (chain ID 828580), or Foundry's anvil (chain ID 31337).
- The native currency is VAU, with 18 decimals. It pays transaction fees at a fixed base fee of 1 gwei. Nothing here holds real value: every key it uses is a simulation or devnet key.
- A session (the chain's history, its contracts, records and oracle jobs) saves itself in the browser and downloads as a JSON file that replays to the same chain.
Features
- /features/account-types: Account types. Say what your wallet is: one of 31 legal forms, from LLC to DAO, plus two short tags of your own. Contracts: VaultAccounts.
- /features/verification: Verified accounts. Ask governors who hold VAU.A to confirm your account type. Two approvals add a Verified tag. Contracts: VerificationDAO, VaultGovernanceToken.
- /features/trust-score: Trust score. A score out of 100, worked out on chain from seven public facts about an account, with reviews from others. Contracts: TrustScore.
- /features/registry: Products, services and deliveries. Register a product by its barcode number, offer a service, and send a delivery to a recipient. Contracts: RealWorldRegistry.
- /features/geotracking: Geotracking. A carrier's tracking devices check a delivery in along its route. Within about 5 km of the destination it counts as arrived. Contracts: GeoTracker.
- /features/oracle-validators: Oracle validators. Stake 100 VAU to judge whether a real-world event happened. Two matching answers settle it and share the reward. Contracts: OracleValidators.
- /features/insurance: Insurance pool. Put VAU into a shared pool. A disputed delivery can claim up to 10% of it, paid only if validators judge the claim real. Contracts: InsurancePool.
- /features/moderation: Moderation. Three flags and a trust score under 30 block an account from Vault's contracts. Its deposits move to the insurance pool. Contracts: Moderation.
- /features/code-visibility: Public or private code. Publish a contract's source for everyone, or keep it encrypted and reveal it later. Public code raises the trust score. Contracts: CodeRegistry.
- /features/random: Verifiable random numbers. Ask for up to 16 random values. Anyone can recompute them from the next block's hash and check them. Contracts: RandomBeacon.
- /features/smart-contracts: Smart contracts. Write Solidity, compile it here, deploy it, then call it from a form built from its ABI. Contracts: Any Solidity contract.
- /features/supply-chain-records: Signed supply-chain records. A factory device signs a GS1 EPCIS event. Its fingerprint is anchored on chain, and anyone can verify it. Contracts: IdentityRegistry, EventAnchor.
- /features/data-oracles: Data oracles. Turn a public JSON or CSV API, such as the weather in a city, into an on-chain data feed. Contracts: FeedRegistry, DataFeed.
Developer tools
- /explorer: latest blocks and transactions, search by block number, hash or address. On Besu it also lists the validators and who proposed each block.
- /accounts: dev accounts from Foundry’s public test mnemonic, burner accounts, a faucet that sends 100 VAU, and a VAU transfer form.
- /contracts: read, write and event views generated from each contract’s ABI, including all 14 Vault contracts.
- /deploy: compile Solidity with solc 0.8.28, pick a Vault contract, or paste ABI and bytecode, then deploy.
- /records: sign an EPCIS 2.0 event with EIP-712, submit it to the gateway, and verify the anchored record from the chain.
- /oracles: turn a public JSON or CSV endpoint into DataFeed contracts, streamed or batched, and check each round against its source.
- /rpc: raw JSON-RPC requests. The simulation and anvil also mine, snapshot, revert and move time (evm_increaseTime); Vault's Besu network has no such controls.
Machine endpoints
- GET /api/health returns { status, name, version, commit, env } without auth.
- GET /api/devnet returns the local devnet’s chain, contracts and example organization, or 503 when none is running (always, on the hosted simulation).
- GET /api/artifacts returns ABIs and bytecode of the Vault contracts: the Foundry build when present, otherwise the bundle the simulation deploys.
- POST /api/compile takes { fileName, source } and returns compiled contracts and diagnostics; 20 compiles a minute per client.
- On the devnet, POST /oracle/inspect takes { url } and returns the source's format, fields and SHA-256; GET and POST /oracle/jobs list and create EIP-712 signed jobs (domain Vault Oracle v1, verifying contract FeedRegistry). In the simulation the same routes answer inside the page.
- DataFeed contracts implement Chainlink's AggregatorV3Interface (latestRoundData, getRoundData, decimals, description, version). Batch feeds add verifyReading(roundId, answer, observedAt, leafIndex, path) for RFC 6962 inclusion proofs.
- GET /_dev is the developer console. It answers 404 unless the deployment sets VAULT_DEV_CONSOLE=on, and then asks for the operator token.