Conformance
Mostly not available yet. Last checked 2026-11-02. The canonical fixtures don’t exist. The first public check is the EVM prediction test.
An implementation conforms when it passes shared test vectors and fails closed on bad input. “It worked in our demo” doesn’t count.
What exists today
| Check | Where | Access |
|---|---|---|
| CREATE2 prediction against the Sepolia factory | This guide | Public, re-run 2026-11-02 |
| Forge and Vitest parity tests | spawn-proto dev | Private |
| Validator unit tests, 10 recorded passing | cardano-invoicing dev | Private |
| Canonical SPORE and SPAWN fixtures | Not built | None |
| End-to-end conformance artifact | Not built | None |
Required flows
The release gate for the first testnet profile covers four flows:
| Flow | Path |
|---|---|
| Send | Capability discovery, quote, authorization, execution, receipt |
| Request | Signed request, publish, resolve, pay, receipt |
| Invoice | Signed invoice with a chosen fee payer, resolve, quote, pay, settled state |
| Off-network invoice | Recipient with no Dial account opens a link, verifies, pays and reloads without double settlement |
Required negative cases
Each one must fail with no external effect:
- Tampered amount, fee payer or command set
- Wrong issuer or bad signature
- Expired or revoked object
- Stale current-state data
- Duplicate or replayed payment
- Quote expiry or fee change
- Commitment mismatch
- Wrong predicted address
- Cache or service loss, which must not change what counts as true
Deployment vectors
Each deterministic strategy needs CI-checked vectors with these fields:
factory, inputSalt, effectiveSalt, initCodeHash, predictedAddressChanging the salt, the init code or the factory must change the result, and the tests have to prove it.
Evidence
A conformance run produces a machine-readable artifact with object references, content hashes, quote and route IDs, fee breakdown, execution evidence, the receipt and the final state, with secrets redacted.
Explore invoicing: Programmable Invoicing