Controlled 0.1 STRK reservation
The operator stage succeeded on-chain. Supplier collection remains pending because wallet note preparation has not passed its release gates.
- Mandate
0x1- Reservation
0x45cc6c11…ecf2bb2b- Reserve transaction
0x3b2d1c01…abb703a9- State
- Open · uncollected
Deployment identifiers
- Vault
0x641ca5237870312273ed2cd693372ee49e103d5c585af6185324f3662e15227- Class
0x3c85f692be0a2280bc85fc9802019121a8b52ef4de0db9273c3806f7355ce14- Pool
0x40337b1af3c663e86e333bab5a4b28da8d4652a15a69beee2b677776ffe812a- Deployment account
0x3f3cc7727c66634967621dc8d4697f1bfd6c29f81757496a4783bf5c90deb89
ROLE WORKSPACES
Move through the real flow
EVIDENCE BOUNDARY
What the chain proves now
Verified Matching VowVault class, pool, mandate funding, and reservation receipt.
Pending No supplier collection or note credit is claimed. Wallet compatibility and audit also remain open.
ADVERSARIAL CHECKS
Falsify the enforcement story
T-005Signature cannot move to another amount, request, root, or mandate.
T-002Proof cannot raise a cap or substitute the approved supplier.
T-003Reservations cannot exceed the available funded budget.
T-004Expiry never rearms a consumed permission.
T-011Only the pinned pool may settle a reservation.
Run npm run verify:vault to confirm the deployed ABI has no generic drain, arbitrary external-call, root-replacement or upgrade entrypoint.
REVIEW MATERIAL
Inspect or challenge the system
The logged-out verifier signs nothing, requests no wallet and submits nothing. It rejects unrelated successful STRK20 transactions.