TrackBTC + CWOS
Shadow-Mode
Shadow-Mode
Pilot.
Evaluate one Bitcoin workflow in your environment. Historical replay followed by live shadow evaluation, with findings recorded for comparison.
The pilot does not block transactions or change signing decisions.
Operator outreachFrom a finding
From a finding
to a conversation.
We are actively contacting operators where we have found anomalies or incidents.
The pilot brings those findings into the operator’s own wallet context and agreed workflow, with historical replay, local shadow evaluation and a weekly review.
Pilot proposal
One agreed scope.
One agreed scope.
Clear success criteria.
| Term | Proposal |
|---|---|
| Scope | One agreed Bitcoin workflow: withdrawal batches, treasury movements or internal wallet routing. One customer environment. |
| Duration | Six weeks from successful activation of shadow mode. |
| Pilot fee | Agreed before kickoff and payable at kickoff. Fully credited toward the first annual production contract if signed within 30 days of pilot completion. |
| Operating mode | Historical replay followed by live shadow evaluation. Findings are recorded for comparison; the pilot does not block transactions or change signing decisions. |
| Customer participation | A named technical owner, access to the agreed local transaction feed and wallet context, and a weekly review session. |
| Data handling | Transactions, private wallet context and policies remain within the customer environment. Any results or metrics shared externally are agreed in advance. |
| Deliverables | Prospect-specific Bitcoin dossier, historical replay findings, local shadow-mode evaluation and a final results report. |
| Success criteria | Agreed before activation: detection of selected anomaly cases, acceptable review burden, evaluation performance and reproducible evidence. |
| Support | Integration assistance and weekly reviews during agreed business hours. Additional workflows or environments require a separate scope. |
| Completion | A final review determines whether to proceed to production, agree a paid extension or conclude the pilot. No automatic renewal or production enforcement. |
| Ownership and publicity | Each party retains its existing technology and data. No exclusivity. Naming the customer or publishing a case study requires written agreement. |
Start the conversation
Bring one workflow.
Bring one workflow.
Define the evaluation.
Contact us to discuss the workflow, environment and anomaly cases you want to evaluate.
pilot@trackbtc.bot