<aside> 📚
A curated library of institutional resources, guides, and collateral for BitSafe's products and services.
</aside>
Institutional-grade wrapped Bitcoin on Canton
<aside>
A concise overview of CBTC: what it is, how it works on Canton, and where it fits for institutional users
</aside>
<aside>
What developers can build on CBTC, how Featured App rewards flow, and where to find the Quick Start, SDKs, API reference, and testnet guide.
</aside>
<aside>
Earn Canton rewards by leveraging high-frequency CBTC trading strategies
</aside>
<aside>
Why trading firms choose CBTC on Canton: MEV-protected settlement, recommended pairs, live venue integrations, and profit share programs.
</aside>
<aside>
CBTC Integrations: Wallets, DEXes & Lending →
Every wallet, DEX, and lending platform with a confirmed CBTC integration, plus the LP and yield programs that route through CBTC pairs
</aside>
Decentralized Party, wallets, and apps
<aside>
Decentralized Party for App Developers →
What Decentralized Party enables on Canton and how app developers can integrate it into product flows
</aside>
Build in Canton
<aside>
Canton DeFi Ecosystem: Wallets, DEXes & Apps →
A landscape map of the Canton DeFi ecosystem with a focus on the CBTC user and liquidity stack
</aside>
<aside>
Canton DeFi Ecosystem for Trading Firms →
Trading-firm oriented overview of venues, integrations, and operational considerations on Canton
</aside>
How BitSafe builds — internal engineering deep dives
BitSafe's AI agent fleet — architecture deep dives
<aside>
NanoClaw — Part 1: Building a Company-Wide AI Assistant →
Architecture, security, and self-improvement patterns behind BitSafe's company-wide AI assistant
</aside>
<aside>
NanoClaw — Part 2: The Architecture →
How BitSafe's fleet-style AI agent system uses persistent memory, scheduled task queues, and continuous business context to act as a force multiplier on the team
</aside>
<aside>
NanoClaw — Part 3: The Autonomous Engine →
Inside NanoClaw's autonomous engine: the cron-driven operating loops, CI/CD that ships its own code, ARQ + swarms, three-layer cost telemetry, and the observability surface that lets the system run itself.
</aside>
<aside>
NanoClaw — Part 4: The Substrate →
Case study of BitSafe's bot substrate — Notion as the operational OS, ~28 SQLite read-mirrors, on-demand code corpus, knowledge graph, MCP tool surface, and Google Secret Manager. The leverage isn't in the model; it's in what the model can read and act on.
</aside>
<aside>
Why Not Just Use the Claude App? Same Brain, Different Body →
Same brain, different body: why a company or agency gets more from an owned NanoClaw + Notion AI OS than the native Claude app alone — rented model vs. owned context, sessions vs. state, and operations vs. output.
</aside>
<aside>
The Invisible Seam: How Our Workspace AI and Our Autonomous Agent Hand Off Work →
How BitSafe's workspace AI (the brain) and autonomous agent (the reach) hand off work — the workspace-first routing rule, the two-way handoff, and the lessons learned at the seam.
</aside>
<aside>
Measuring an AI OS, Honestly — What We Track, and What We Refuse to Claim →
How we measure an internal AI system of ~60 agents without faking ROI — adoption inputs, a five-stage maturity ladder rolling into an AI Adoption Index, and cost as the one number we trust.
</aside>
Four-part series on building Notion as a company OS
<aside>
Part 1: Notion as the Company OS →
How BitSafe rebuilt the company itself so AI could use it — turning Notion from a wiki into a structured substrate that agents can act on
</aside>
<aside>
The schema, relations, and database design patterns that make BitSafe's Notion workspace agent-ready — Pillars, Projects, Tasks, and the CRM spine
</aside>
<aside>
Part 3: Agents, Automations, and the AI Layer →
How Notion AI, Claude, and NanoClaw divide labor across the BitSafe AI stack — custom agents, AI-powered SOPs, autofill, and the MCP layer that connects them
</aside>
<aside>
</aside>