Taurus primary-source snapshot
Last reviewed: 2026-04-27 UTC
Project status snapshot
- Official site: https://www.taurushq.com/
- Developer hub: https://docs.taurushq.com/
- Protect / Capital intro: https://docs.taurushq.com/protect-capital/docs/introduction
- Protect / Capital API concepts: https://docs.taurushq.com/protect-capital/reference/api-structure-and-concepts
- Explorer reference intro: https://docs.taurushq.com/explorer/reference/introduction
What the official materials say
1) Developer hub / current platform framing
- URL: https://docs.taurushq.com/
- Key takeaways:
- Taurus presents itself as modular infrastructure built for financial institutions.
- The hub groups the public product surface into Taurus-PROTECT & Taurus-CAPITAL, Taurus-EXPLORER, and Taurus-PRIME, plus separate user guides.
- This is the strongest immediate clue that Taurus should be treated as a multi-product institutional platform rather than as a single custody or tokenization product.
2) Protect / Capital introduction
- URL: https://docs.taurushq.com/protect-capital/docs/introduction
- Key takeaways:
- Taurus describes this section as its platform integration documentation and organizes it into documentation overview, user guides, API reference, and SDK.
- The page foregrounds security principles, architecture, wallet overview, API endpoints, and SDK access as the core public integration surface.
- User guides are password protected for clients, which is a useful operational hint about the enterprise nature of the product.
3) Protect / Capital API structure and concepts
- URL: https://docs.taurushq.com/protect-capital/reference/api-structure-and-concepts
- Key takeaways:
- Taurus organizes API workflows into wallets and addresses, transfers and staking, token issuance and asset servicing, Taurus Network, identity and access management, policy engine, system administration, third-party integrations, Airgap Cold HSM, and webhooks.
- The docs say many actions require governance-rule approvals and digital signatures from designated operators, which is a strong trust-boundary and segregation-of-duties clue.
- The same docs also require whitelisting before sending funds or calling smart contracts, again reinforcing that Taurus is designed around controlled institutional workflows.
4) Explorer reference intro
- URL: https://docs.taurushq.com/explorer/reference/introduction
- Key takeaways:
- Taurus-EXPLORER is framed as a blockchain node and indexing surface with both current and historical data access.
- The official coverage page lists a broad network set spanning Bitcoin, Ethereum, Solana, Cardano, Ripple, Polygon, Arbitrum, Base, Optimism, and many others, with some future coverage dates also shown.
- This is an important clue that Taurus is not only a custody/tokenization stack; it also wants to be an institutional chain-data and infrastructure provider.
5) Official website / company-level framing
- URL: https://www.taurushq.com/
- Key takeaways:
- The official site emphasizes custody, tokenization, trading, and network/infrastructure capabilities under one brand.
- Even where the marketing copy is high level, the site aligns with the developer hub’s modular, institution-first framing.
- That combined site-plus-docs picture makes Taurus best understood as digital-asset operating infrastructure for regulated or institution-style users.
Whitepaper / technical-doc status
- No canonical Taurus whitepaper or litepaper was found in this pass.
- The official docs are substantially more informative than any standalone paper for understanding current product scope, trust boundaries, and operator workflow.
- In practice, the developer hub is the strongest source of truth for this project snapshot.
Research notes
- Best current category for the library: institutional digital-asset infrastructure / custody / tokenization / trading / blockchain-data platform.
- Key categorization insight: Taurus should be treated as a modular financial-control-plane vendor spanning multiple operational layers, not as a simple custodian.
- Another useful note for future scouting: enterprise vendors that expose policy engines, whitelisting, approval signatures, HSM flows, and chain-data products in the same official docs surface are often much broader than the homepage headline suggests.