See beyond your own records.
Build an operating picture from Bitcoin history and your local wallet context. Examine activity beyond your own account records.
TrackBTC + CWOS
Shadow-Mode
Shadow-Mode
Pilot.
Help your team protect customers, explain its decisions, and demonstrate its contribution. Evaluate one Bitcoin workflow over six weeks, with findings your team can check.
The pilot does not block transactions or change signing decisions.
What shadow mode meansBuild confidence in one Bitcoin workflow.
Build confidence in one Bitcoin workflow.
Review the evidence together.
Choose withdrawal batches, treasury movements, or internal wallet routing. Review findings alongside your existing work, without changing how transactions are authorized.
We agree which records and questions belong in the evaluation before activation.
- Agree the decisionDefine the workflow, required records, selected cases, and success criteria with your technical owner.
- Replay earlier activityExamine agreed historical cases using the relevant Bitcoin history and your team’s local records.
- Review alongside current workRecord findings during live shadow evaluation and discuss them in weekly reviews.
- Assess the resultsReview the evidence, performance, and work required before deciding the next step.
The six-week evaluation starts after successful activation of shadow mode. Transactions, private wallet context, and policies remain within your environment.
What your team getsFinish with results
Finish with results
your team can explain.
The operating profile, historical replay, live shadow evaluation, and final results report give your team a record it can use with colleagues and executives.
Know what your team should check next.
Review prioritized findings with supporting transactions, the evidence for each interpretation, and questions needing your team’s confirmation.
Show how your team reached its decision.
Record what was found, when it was known, how it was checked, and which decisions followed. Assess the review work against agreed criteria.
Give your team credit for verified work.
Document who initiated the work and helped validate the findings. Agree any public acknowledgment separately, after verification.
- The work your team initiatedThe question, selected workflow, participating teams, and agreed success criteria.
- The evidence your team checkedThe findings examined, supporting records, validations, and unresolved questions.
- The decisions that followedThe actions taken, reasons for those decisions, and any further review required.
- The contribution people madeThe people who led the evaluation, checked the evidence, and informed the response.
The brief records the work and its results, including cases needing further review. It helps your team explain its contribution internally.
Research collaborationHelp shape the research.
Help shape the research.
Earn credit for what you contribute.
Bring the Bitcoin questions your team needs answered. Work with us to test findings and document what your team contributed.
Research collaboration is voluntary and does not require a pilot or subscription. Explore our published research and contribution opportunities.
With verified results and written agreement, contributors can participate in joint research, a case study, or an acknowledgment of their work.
Public recognition is optional. Your team decides whether to participate and agrees what can be shared. Attribution reflects the contribution and verified results.
Private findings reviewReview a finding with us.
Review a finding with us.
Free of charge.
Teams can review relevant findings with us privately, free of charge.
No pilot or subscription is required.
hello@trackbtc.bot
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
Lead the evaluation.
Lead the evaluation.
Give your team a result it can stand behind.
Tell us which decision your team needs to make, the workflow you want to evaluate, and what useful evidence would look like.
pilot@trackbtc.bot