The model assembles the case. The operators decide.
A treasury officer asks whether a proposed transfer fits the contract. The model gathers signed context for the people holding the keys—then gets out of the authorization path.
Give the signers enough context to say yes—or stop the transfer.
The LLM is asked to examine one proposed Bitcoin transfer. It resolves the destination against a deterministic contract, places the amount inside the vault’s recorded history, identifies the valid signing paths, and prepares the evidence for each officer.
That output is decision support, not approval. Red, Blue, and the HSM policy remain independent of the model. The officers should inspect the evidence, challenge the explanation, and refuse the request when the case does not hold.
Establishes the facts.
Address enrollment, contract identity, completed history, threshold policy, and signed bytes are checked without model judgment.
Builds the context.
Organizes the ranges, dates, outputs, and signing paths so each key holder can see what deserves attention.
Validate and decide.
Review the signed information, verify destination and policy, question the explanation, then authorize or reject with their own keys.
Know the context arrived intact.
The signature shows that the information matches the bytes issued by TrackBTC. It does not prove the transfer is safe; that judgment stays with the operators.
- Review
- TX-084 / context-v1
- Signed by
- TrackBTC Evidence Key 03
- Fingerprint
- 9e71…c42a
- Integrity
- Signature valid
Unlock with your YubiKey.
Enrolled operators use a registered hardware key to open the signed facts and model explanation before they decide.
Product preview · No credential is requested herevalidate transfer TX-084 and brief the eligible key holders[01] CONTRACT Destination bc1q…7m2 is enrolled in deterministic contract DC-17. [02] HISTORY The vault has 84 recorded outgoing transfers. Amounts range from 8 to 16 BTC; median 11.8 BTC; average 12.1 BTC. Proposed amount: 12.42 BTC. Nearest prior amounts: 12.38 BTC on 28 Aug 2026 and 12.51 BTC on 19 Jul 2026. [03] TRANSACTION SHAPE Vault before: 18.750231 BTC. One destination output sends 12.42 BTC. One change output returns 6.329984 BTC to an address previously used by this vault. Fee: 0.000247 BTC at 14.8 sat/vB versus a 13.9 sat/vB historical average. Vault after transfer and fee: 6.329984 BTC. [04] THRESHOLD Valid path: (RED OR BLUE) + HSM1. Previous execution used RED + HSM1. Both human-key paths remain valid. The brief does not select the signer. [05] OPERATOR DECISION Evidence is ready for inspection. This is not approval. The selected human key holder and HSM1 operator must validate the destination, amount, fee, outputs, and signed fingerprint before authorizing.
- Minimum
- 8 BTC
- Median
- 11.8 BTC
- Average
- 12.1 BTC
- Proposed
- 12.42 BTC
- Maximum
- 16 BTC
Previous execution: RED + HSM1 · This brief does not select the signer.
Destination is enrolled; amount position, outputs, fee, and change history are shown above. Independently verify every fact before signing with HSM1.
You remain a valid signer under the contract. The previous execution used RED + HSM1; that history does not select the signer for this transfer.
Context should travel with receipts. Authority should stay with the keys.
The useful model does not make the decision. It makes evidence easier to inspect, uncertainty visible, and accountable operators able to validate the case themselves.