AnchorWatch

• Name: AnchorWatch
• URL: https://www.anchorwatch.com/
• Category: insured bitcoin custody and recovery operator / Trident vault-platform company / regulated Bitcoin insurance entity
• Tags: bitcoin-ecosystem
• Summary: AnchorWatch belongs as an entity note, not just a custody-product note. The useful question is not merely what timelocked Bitcoin vault exists? but which named operator controls the underwriting perimeter, recovery-policy design, enterprise licensing, and the script-plus-insurance package that customers inherit? The practical leverage sits where Trident spending conditions, insurer-approved operating policy, policy issuance, and enterprise deployment all meet inside one company boundary.
• What it does:
  • Operates AnchorWatch Vault custody offerings that mix customer key control, institutional co-control, and optional insurance inside one managed operating shell
  • Runs Trident, its Bitcoin-native custody platform built around multisig, timelocks, alternative recovery paths, and continuity-oriented script design
  • Sells Lloyd’s-backed Bitcoin insurance and presents coverholder status as part of the core product boundary rather than as an external sidecar
  • Licenses Trident to exchanges, advisors, banks, and other financial institutions that want to run insured or policy-shaped Bitcoin custody under their own brand or workflow
  • Packages inheritance, coercion resistance, business continuity, and compliance constraints into the same operator surface as custody setup and insurance issuance
• Key claims:
  • The homepage says AnchorWatch combines advanced Bitcoin-native vault technology with optional Lloyd’s of London insurance, which is the clearest reason not to flatten it into only a wallet or vault note
  • The homepage also groups the business into insured custody, commercial insurance, and enterprise SaaS infrastructure, which makes the company boundary more analytically useful than a single product page
  • The site says AnchorWatch is a Lloyd’s of London Coverholder authorized to write policies and publicly advertises coverage up to large per-customer and per-enterprise limits; that makes underwriting authority part of the real control surface
  • Trident materials say the platform uses advanced Bitcoin scripts so alternative spending conditions become valid after a defined timelock if a key is lost or a participant becomes unavailable, which shows recovery is encoded into the custody design rather than handled only by customer support
  • The Trident page says AnchorWatch licenses the platform to exchanges, advisors, banks, and financial institutions, which is a strong clue that the entity boundary matters beyond retail custody marketing
  • The custody-insurance page explicitly covers theft, coercion, disasters, and fraud or collusion by institutional key holders, revealing that AnchorWatch’s operating model spans technical, physical, and organizational risk under one policy shell
  • The homepage still markets a qualified-custodian path expected in 2026, which is useful as a regulatory-positioning signal even if it should not be read as completed status without fresher confirmation
• Whitepaper: No classic AnchorWatch company whitepaper is the point here. The clearest primary materials are the official homepage, Trident page, insurance overview, custody-insurance page, and the earlier primary-source capture in ../whitepapers/anchorwatch-primary-sources-2026-04-28.md.
• Sources:
  • https://www.anchorwatch.com/
  • https://www.anchorwatch.com/trident
  • https://www.anchorwatch.com/insurance
  • https://www.anchorwatch.com/insurance/custody-insurance
  • https://ldc.lloyds.com/market-directory/results?cobc=&cob=&loc=&ltti=&bro=1&cov=1&man=1&mem=1&omc=1&name=AnchorWatch

Internal linkages

• Project-layer alias: anchorwatch.
• Useful adjacent company boundary: casa for another recovery-and-continuity-heavy Bitcoin operator where the service workflow matters more than a neutral protocol story.
• Mechanism and product contrasts: bitkey and unchained.

Protocol / company boundary

• There is no especially useful standalone AnchorWatch protocol boundary doing the analytical work here.
• The meaningful surface is the company-run combination of Trident script design, recovery workflow, insurance underwriting, enterprise licensing, and compliance positioning.
• That is why AnchorWatch belongs in companies/: the practical questions are about who defines the custody model, which recovery and timelock paths are packaged, which losses are insurable, and how institutions inherit those defaults.

Control surface

• Practical leverage sits in Trident vault templates, alternative spend-path and timelock design, insurer-approved operating requirements, policy issuance and coverage scope, institutional key-holder assumptions, and enterprise licensing of the custody stack.

• The sticky dependency is not just the script. It is the company-operated package where recovery promises, underwriting terms, operational governance, and enterprise deployment all reinforce one another.

• Treat AnchorWatch as an insured-custody and recovery company first. The Bitcoin scripts matter, but the real operator boundary is the named entity deciding how those scripts, policies, and workflows reach users.

• Last reviewed: 2026-08-06 UTC