LIVE FIREWALL · NO ACCOUNT · FORGE IT YOURSELF

Don't trust us. Try to forge it.

The Fidacy payment firewall authorizes a payment against a signed mandate, issues a short-lived Ed25519 grant, and writes a hash-chained, append-only proof. Run it live below, then verify and tamper with it in your own browser, against Fidacy's public key, with no account.

1 · RUN A PAYMENT THROUGH THE FIREWALL
{{ s.name }} {{ s.note }}
{{ s.expect }} run →
2 · THE GRANT — POST /v1/firewall/authorize

pick a payment to run it through the live firewall▋
→ payment received · {{ runningName }}
→ checking the signed mandate…
→ firewall deciding▋
{{ verdictLabel }} {{ latency }}ms
{{ reason }}
{{ grantLine1 }}
{{ grantLine2 }}
3 · THE PROOF — HASH-CHAINED, APPEND-ONLY

Now try to rewrite history.

Every decision above was appended to this chain — each entry is SHA-256 hashed in your browser over its content plus the previous hash. Tamper with one and watch every link after it break.

audit.chain · sha-256 · computed in your browser

run a payment above — every verdict lands here as a chained entry
{{ e.statusIcon }} #{{ e.seq }} {{ e.label }} {{ e.verdict }} prev {{ e.prevShort }} {{ e.hashShort }}
✕ chain broken — the recomputed hash of the tampered entry no longer matches what the next entry recorded. Every link after it fails. This is what an auditor sees.
4 · BEYOND TAMPER-EVIDENT

Even we can't rewrite it.

The hash chain above proves no record can be edited without the chain breaking. But the signing keys exist, so a determined operator could in principle regenerate the whole chain from scratch. That is why Fidacy commits the chain's head to Bitcoin, a public ledger no single party controls. Rewriting the history would mean rewriting Bitcoin.

LIVE ANCHOR STATE
chain head : {{ headShort }}
committed via OP_RETURN → Bitcoin block 959,661
next anchor : under 60 minutes
demo state — the live page reads the public anchor record

No private key, no valid grant. That is the whole point: the executor never moves money without a grant it can verify against Fidacy's public key, and any retroactive edit to the audit log breaks the chain.

Verify it in your own terminal →