Mainnet evidence
Everything here can be checked on the explorer.
Hashes below come from files saved in the repository's evidence folder. Refused transactions are real reverted transactions, shown because the refusal is the point.
Deployed contract
- Verified source on the explorer
- Open contract code
- Deployment block
- 12,009,160
- Deposit cap per account
- 5 QUSDC (5,000,000 base units)
The explorer reports the source as verified. Its optimizer field reads "false" although the project compiled with the optimizer on; verification passed regardless and the difference is unexplained.
Deployment and smoke test
Seven transactions run immediately after deployment: the happy path plus the two refusals.
Contract deployment
TurnpikeAllowance, deposit cap 5 QUSDC
Passed (succeeded)
Source file: deployment.json
Full demo sequence on mainnet
Allowed, over-cap, replay, revoke, restore and withdraw, driven through the real gateway and middleware.
Allowed payment (agent through the gateway)
Delivered live block data after confirmations
Passed (succeeded)
Source file: M4_mainnet_demo.jsonOver-cap payment
CapExceeded, broadcast with a fixed gas limit
Refused (reverted on-chain)
Source file: M4_mainnet_demo.jsonOwner revokes the agent
The next agent payment was refused with NotOwnerAgent (refused at submission, so it has no transaction)
Passed (succeeded)
Source file: M4_mainnet_demo.jsonOwner withdraws 1,000 base units
Withdrawal works while the owner controls the account
Passed (succeeded)
Source file: M4_mainnet_demo.jsonMiddleware against mainnet: paid call
Receipt in 5.13 s; gateway showed 202 pending, then 200
Passed (succeeded)
Source file: M3_mainnet_integration.json
Hosted gateway runs
Run through the public gateway after it was deployed, including a purchase made with the agent SDK.
Agent SDK buys from the hosted gateway
examples/node-agent with @turnspike-qie/client: quote, pay, 2 confirmations, delivered in 15 s; rerun with the same key replayed without paying. 92,159 gas
Passed (succeeded)
Source file: M8_sdk_mainnet.mdHardened gateway: allowed call
Solved puzzle, paid, pending, delivered
Passed (succeeded)
Source file: M7_live_demo.jsonHardened gateway: replay refused
RequestAlreadyUsed
Refused (reverted on-chain)
Source file: M7_live_demo.jsonHardened gateway: over-cap refused
CapExceeded
Refused (reverted on-chain)
Source file: M7_live_demo.jsonLive site: allowed call
Run through the public gateway
Passed (succeeded)
Source file: M5_live_demo_run.txtLive site: replay refused
RequestAlreadyUsed
Refused (reverted on-chain)
Source file: M5_live_demo_run.txt
Tests that were actually run
Outputs are saved in the repository.
Contract tests (TEST-C01 to C13, SEC-008 ABI check, token-conservation fuzz)
15 passing; contract line coverage 100%, branch 87.5%
Middleware, gateway and demo-guard tests (protocol, security, retention, reconciliation, fenced leases, response fidelity, request binding, demo quotas, paid endpoints)
47 passing on a local chain, including a real process crash and restart, concurrent redemption, chain reconciliation of an unredeemed payment, a handler slower than its lease, binary responses, a simulated reorg and storage failures
Agent client SDK (@turnspike-qie/client) against the real middleware and contract
16 passing: trusted payment, replay without second payment, price ceiling, untrusted merchant and origin, wrong network, low balance, paused, revoked, unlisted merchant, no gas, dry run, decline, expiry, gateway down after payment, crash between broadcast and journal write, unconfirmed transaction, delayed gateway, state change before broadcast
CLI (turnspike) on a local chain
10 passing: usage and exit codes, init without secrets, account inspect, probe, refusal without confirmation, dry run, pay and verify, policy refusals, wrong password, doctor
Two-sided example on built packages (seller middleware and agent client)
END-TO-END OK: paid, replayed without second charge, invalid input refused with 400, price ceiling held
Middleware against the deployed mainnet contract
Paid call delivered; same proof replayed from the store; on-chain replay refused
Static analysis (Slither 0.11.6) and dependency audit
No High or Medium findings in project code; 0 runtime-dependency vulnerabilities (52 advisories in dev tooling). Not an audit.
Block observation on QIE (94 consecutive blocks, two RPCs)
No block hash changed and both RPCs agreed. This does not prove finality.
Wallet app in a browser against the real contract on a local chain-1990 node (mock wallet)
Approve, deposit, policy, merchant, pause, withdraw, revoke, wallet rejection, no-gas, wrong network, account change, disconnect, history: all behaved as specified. Not tested with QIE Wallet or MetaMask
Lighthouse on the Vercel production site (mobile profile)
Home: performance 92, accessibility 100, best practices 100, SEO 100. Playground: 90, 100, 100, 100
Read-only mainnet simulations of two refusals
MerchantNotAllowed and NotOwnerAgent returned by the deployed contract (eth_call)
Restart persistence on the hosted gateway
Delivered count unchanged after a machine restart
Usage
Live from the gateway database. No external adoption is claimed beyond what these counters show.
- Calls delivered
- All paid calls this gateway has delivered
- From addresses the operator controls
- The project's own test wallets
- From other addresses
- Counted only if the payer is not in the operator's list
- Paid but undelivered over 24 h
- No automatic refund in this version
Not yet verified
- Independent bytecode comparison for the deployed contract (the explorer reports the source as verified).
- Why reverted calls are charged gas: receipts show exactly 50% of the gas limit in all 5 samples (a hypothesis, not a confirmed rule; see M6_gas_and_qusdc.md).
- Chain finality: no reorg was observed over 94 blocks, which does not establish finality.
- Who holds QUSDC mint and burn roles.
- The web app has been driven with a mock wallet against a local chain, not with QIE Wallet, MetaMask or a mobile wallet, and no transaction has been sent from the UI to mainnet.
- The public demo is protected by quotas, proof of work and a gas floor, but the demo agent holds a small funded key on the gateway; if it runs out of gas the demo pauses until topped up.
- No external user or merchant has used Turnspike yet. Every mainnet transaction above is from project-operated wallets; the usage counters below show whatever the gateway records.
- The npm packages (@turnspike-qie/middleware, client, cli 0.1.0) were installed and run from a clean folder by the project, not yet by an independent developer.