TITAN FORTRESS the evidence layer
between signal and execution
Audit chain · Bitcoin anchoring

Verify a Titan decision against Bitcoin.

Titan records why each signal was forwarded or blocked, then commits a daily fingerprint of those records to Bitcoin. This page recomputes the decision path from a proof bundle and stops at the anchored fingerprint.

01

Proof scope

Checks

  • Decision bytes. The recorded fields hash to the supplied chain leaf.
  • Merkle path. The leaf folds to the account root and then to the aggregate root.
  • Anchor target. The aggregate fingerprint is the value submitted to OpenTimestamps.

Does not check

  • Decision quality. A bad input can still produce a valid record.
  • Input provenance. This proof starts at the recorded decision row.
  • Broker execution. A valid receipt is not proof of a placed or filled order.

Scope: record integrity only. Decision quality, input provenance, and broker execution are outside this proof.

02

Bundle verifier

Paste an exported proof bundle. The verifier recomputes the chain-leaf hash, walks the account and aggregate Merkle paths, and rebuilds the fingerprint Titan submitted to OpenTimestamps. Any mismatch fails.

Verified span: decision row fields → aggregate fingerprint. Bitcoin boundary: this page does not inspect Bitcoin. OpenTimestamps proof and block links show where the fingerprint landed.

Self-test · not a Titan anchor.
Checks SHA-256, production hash fixtures, a synthetic two-tier Merkle walk, and tamper failures. Exported decisions: “Paste proof bundle.”

03

A recorded decision, anchored to Bitcoin

Recorded AAPL decision · montes account · no order placedRecorded · on-chain

On 2026-03-23, Titan evaluated an AAPL buy signal for the montes account and recorded it as ignored. No order was placed. The decision commitment was later anchored to Bitcoin.

This is a V1 receipt: it binds the recorded decision, not a broker account type. It makes no claim about whether the account was live or paper, and it does not prove that a broker order was placed or filled, that money moved, or that the strategy was profitable; nothing was executed.

Decision
97b984dfe2124a73a2cd1518791e9b3a
Account
montes
Evaluated
2026-03-23 (UTC)
Submitted to OpenTimestamps
2026-05-10 18:34:15 UTC
Anchored in Bitcoin
≈ 10 minutes later, via independent calendar servers

The aggregate root for that day landed in these Bitcoin blocks. Open any block and compare the commitment there.

Internal-path check: export this bundle with python -m titan.audit_chain_verify 97b984df… --emit-bundle and paste it above. Expected aggregate fingerprint: b926e6….

04

Verification depth

Show the Bitcoin-side checks
1

Calendar check

OpenTimestamps calendars report which Bitcoin block committed the fingerprint.

2

Explorer check

mempool.space, blockstream.info, or another explorer can inspect the block commitment.

3

Node check

Run ots verify --bitcoin-node … against the downloaded proof and a local Bitcoin node.

The commitment is the same at every rung. Higher rungs remove third-party views of Bitcoin.