Skip to content

Tech Stack References

See also: Stakeholders overview for a summary by relationship type.

Status: CURRENT
Last verified: 2026-02-12
Purpose: Condensed reference for the COOWN agent swarm — WHO we work with, WHERE their docs live, and WHAT role they play for us.

How to Use This Document

This document provides quick reference to all technology providers, integration partners, protocols, and tools supporting the COOWN platform. Each entry includes: - Primary and documentation domains - Role in COOWN's architecture - Key documentation links (verified accessible) - SDK/library package names where applicable - Important notes for developers

For detailed integration patterns, see the relevant Technical Architecture documents in product-services/technical-architecture/.

Blockchain / Core Platform

DFINITY / Internet Computer (internetcomputer.org, docs.internetcomputer.org)

Role in COOWN: Primary blockchain infrastructure hosting all COOWN backend canisters and frontend assets; provides decentralized compute, storage, and web-speed transaction processing.

Key docs: - https://internetcomputer.org — Main website and ecosystem overview - https://docs.internetcomputer.org — Developer documentation and tutorials - https://docs.internetcomputer.org/motoko/home — Motoko language guide - https://internetcomputer.org/how-it-works/chain-key-technology/ — Chain Key cryptography explained - https://docs.internetcomputer.org/references/ic-interface-spec — Internet Computer interface specification

SDK/Libraries: @dfinity/agent, @dfinity/candid, @dfinity/principal (npm packages)

Notes: ICP provides ~1000 TPS, sub-second finality, on-chain storage at ~$0.50/GB/year; COOWN uses ~10-20 canisters across main and beta environments.

Related docs: canister-configurations.md, system-architecture.md

Motoko Language (internetcomputer.org/docs/motoko, sdk.dfinity.org)

Role in COOWN: Primary smart contract development language for COOWN backend canisters; domain-specific language designed for safe, secure ICP canister development.

Key docs: - https://docs.internetcomputer.org/motoko/home — Language guide and reference - https://internetcomputer.org/docs/current/motoko/main/motoko-introduction — Introduction to Motoko - https://internetcomputer.org/docs/current/motoko/main/base/ — Base library reference - https://m7sm4-2iaaa-aaaab-qabra-cai.ic0.app/ — Motoko Playground (in-browser IDE)

SDK/Libraries: Part of dfx SDK; no separate package installation required

Notes: Actor model with orthogonal persistence (state automatically saved); asynchronous message passing between canisters.

ICRC Token Standards (docs.internetcomputer.org)

Role in COOWN: Standardized token interfaces for fungible tokens on ICP; COOWN uses ICRC-1 and ICRC-2 for token operations including future $COOWN token.

Key docs: - https://docs.internetcomputer.org/developer-docs/defi/tokens/token-standards — Token standards overview - https://github.com/dfinity/ICRC-1 — ICRC-1 specification (fungible token standard) - https://github.com/dfinity/ICRC/blob/main/ICRCs/ICRC-2/ICRC-2.md — ICRC-2 specification (approve/transfer-from) - https://dashboard.internetcomputer.org/sns — SNS DAO governance tokens

SDK/Libraries: @dfinity/ledger-icrc (npm)

Notes: ICRC-2 extends ICRC-1 with approval mechanisms similar to ERC-20; used for $COOWN tokenomics.

Related docs: tokenomics.md

CycleOps (cycleops.dev)

Role in COOWN: Canister cycle management and monitoring service; automatically tops up canister cycles and sends low-balance alerts to operations email.

Key docs: - https://cycleops.dev — Main platform and dashboard - https://cycleops.dev/docs — Documentation (⚠️ verify URL if 404, try main domain)

SDK/Libraries: Web-based dashboard; no SDK required

Notes: Critical for preventing canister out-of-cycles errors; monitors all COOWN canisters listed in canister-configurations.md.

Threshold ECDSA / Chain Key Signing (docs.internetcomputer.org)

Role in COOWN: Enables ICP canisters to securely sign transactions for external blockchains (Bitcoin, Ethereum, Base) without exposing private keys; powers COOWN's cross-chain functionality.

Key docs: - https://internetcomputer.org/how-it-works/threshold-ecdsa-signing/ — Chain Key technology overview - https://internetcomputer.org/docs/current/developer-docs/integrations/t-ecdsa/ — Threshold ECDSA developer guide - https://internetcomputer.org/docs/current/developer-docs/integrations/bitcoin/ — Bitcoin integration via threshold signatures - https://internetcomputer.org/docs/current/developer-docs/defi/chain-fusion/ — Chain Fusion overview

SDK/Libraries: Built into ICP runtime; accessed via system API

Notes: COOWN's sign_backend canister (duunm-hyaaa-aaaap-an4nq-cai) uses threshold ECDSA for USDC/EVM operations.

Internet Identity (identity.ic0.app, internetcomputer.org)

Role in COOWN: Decentralized authentication system using WebAuthn passkeys; provides secure, privacy-preserving user login without passwords or email addresses.

Key docs: - https://identity.ic0.app — Internet Identity authentication frontend - https://internetcomputer.org/internet-identity — Overview and features - https://internetcomputer.org/docs/current/developer-docs/integrations/internet-identity/ — Integration guide for developers - https://github.com/dfinity/internet-identity — Open-source repository

SDK/Libraries: @dfinity/auth-client (npm)

Notes: User private keys never leave device; biometric authentication via Face ID/Touch ID; COOWN plans integration for future releases.

Payments & Stablecoins

Monerium (monerium.com, monerium.dev)

Role in COOWN: Licensed e-money institution (EMI) providing IBAN accounts, SEPA Instant payments, EURe stablecoin (1:1 EUR-backed), and KYC/KYB services for COOWN fiat on/off-ramp.

Key docs: - https://monerium.com — Main website and product overview - https://monerium.dev — Developer portal - https://monerium.dev/api-docs/v2 — API v2 documentation - https://monerium.dev/docs/getting-started/create-app — Integration quickstart - https://github.com/monerium/ — Open-source SDKs and examples

SDK/Libraries: @monerium/sdk (npm)

Notes: EURe = EUR-backed stablecoin on Ethereum/Polygon; requires API key; COOWN integration handles account creation, SEPA transfers, KYC workflows. Monerium operates under EU EMI license.

Related docs: system-architecture.md § Key Integrations

Circle (circle.com, developers.circle.com)

Role in COOWN: Issuer of USDC stablecoin (USD-pegged, 1:1 reserves); provides APIs for programmable wallets and cross-chain USDC transfers.

Key docs: - https://circle.com — Main website and regulatory information - https://developers.circle.com — Developer documentation hub - https://developers.circle.com/wallets/dev-controlled/create-your-first-wallet — Developer-controlled wallets quickstart - https://developers.circle.com/bridge-kit — Bridge Kit for cross-chain USDC transfers - https://developers.circle.com/api-reference/wallets/developer-controlled-wallets/create-wallet-set — Wallet creation API reference

SDK/Libraries: @circle-fin/circle-sdk (npm), Web3 Services SDKs

Notes: USDC is fully reserved and regulated; Circle recently achieved MiCA compliance in EU; COOWN uses USDC for USD liquidity.

Gnosis Pay (gnosispay.com, docs.gnosispay.com)

Role in COOWN: VISA debit card program (physical + virtual cards) enabling crypto-to-fiat spending at point of sale; provides API for card issuance and management.

Key docs: - https://gnosispay.com — Main website and product overview - https://docs.gnosispay.com — API documentation and integration guide - https://docs.gnosispay.com/api-reference/intro — API reference introduction - https://my.gnosispay.com/ — Gnosis Pay web application - https://github.com/gnosispay/ — Open-source repositories (⚠️ verify availability)

SDK/Libraries: RESTful API; SDKs available via GitHub

Notes: Self-custodial cards backed by Safe Smart Accounts; supports SEPA, Pix, Apple/Google Pay; COOWN integration planned for user spending functionality.

Digital Assets & Tokens

Bitcoin (bitcoin.org)

Role in COOWN: Underlying asset for ckBTC (chain-key Bitcoin on ICP); COOWN supports BTC via ICP's native Bitcoin integration.

Key docs: - https://bitcoin.org — Official Bitcoin project website - https://bitcoin.org/en/developer-documentation — Developer documentation - https://bitcoin.org/en/bitcoin-core/ — Bitcoin Core (reference implementation) - https://github.com/bitcoin/bitcoin — Bitcoin Core repository

SDK/Libraries: N/A for COOWN (uses ICP Bitcoin integration)

Notes: BTC integration via ICP threshold ECDSA; COOWN uses ckBTC (1:1 BTC-backed token on ICP) for Bitcoin operations.

ckBTC (docs.internetcomputer.org)

Role in COOWN: Chain-key Bitcoin token on Internet Computer; 1:1 backed by BTC held by ICP protocol via threshold ECDSA; enables fast, low-cost Bitcoin transactions.

Key docs: - https://internetcomputer.org/docs/current/developer-docs/multi-chain/bitcoin/ckbtc/ — ckBTC overview - https://internetcomputer.org/docs/current/developer-docs/multi-chain/bitcoin/using-btc/bitcoin-how-it-works — Bitcoin integration technical details - https://dashboard.internetcomputer.org/bitcoin — ckBTC dashboard and statistics - https://github.com/dfinity/ic/tree/master/rs/bitcoin — ICP Bitcoin integration source code

SDK/Libraries: @dfinity/ledger-icp (npm), ICRC-1 compatible

Notes: ckBTC transactions settle in ~1-2 seconds (vs. 10+ minutes for BTC mainnet); no bridge fees; COOWN supports ckBTC in wallets.

GLDT / Gold DAO (gldt.org)

Role in COOWN: Gold-backed digital token on ICP; each GLDT represents ownership of physical gold stored in vaults; provides gold exposure for COOWN users.

Key docs: - https://gldt.org — Main website - https://dashboard.internetcomputer.org/sns/tw2vt-hqaaa-aaaaq-aacbq-cai — GLDT SNS DAO dashboard - https://github.com/GoldDAO — Gold DAO GitHub organization (⚠️ verify availability)

SDK/Libraries: ICRC-1/ICRC-2 compatible token

Notes: Fully decentralized gold-backed token; governed by SNS DAO on ICP; integration status: planned for COOWN asset portfolio.

Frankencoin (frankencoin.com)

Role in COOWN: Decentralized Swiss Franc stablecoin (ZCHF symbol); tracks CHF 1:1; collateralized on-chain without central issuer.

Key docs: - https://frankencoin.com — Main website and documentation - https://frankencoin.com/positions — Active collateral positions - https://docs.frankencoin.com/ — Documentation hub (⚠️ verify URL) - https://github.com/Frankencoin-ZCHF — Open-source repository

SDK/Libraries: ERC-20 compatible token

Notes: Deployed on 8+ blockchains including Ethereum, Polygon, Base; fully transparent rule-based system; COOWN integration planned for CHF exposure.

EVM / Cross-Chain

Ethereum (ethereum.org, docs.ethers.org)

Role in COOWN: Primary EVM-compatible blockchain for stablecoin operations (EURe, USDC); COOWN interacts via ICP EVM canister using threshold ECDSA.

Key docs: - https://ethereum.org — Official Ethereum website - https://ethereum.org/en/developers/docs/ — Ethereum developer documentation - https://docs.ethers.org — Ethers.js documentation (JavaScript library) - https://docs.soliditylang.org/ — Solidity smart contract language - https://github.com/ethereum — Ethereum GitHub organization

SDK/Libraries: ethers, web3.js (npm); COOWN uses ICP's native EVM integration

Notes: COOWN's EVM canister enables direct Ethereum mainnet interactions without external bridges; used for Monerium EURe and Circle USDC operations.

Related docs: system-architecture.md § EVM Canister

Base (base.org, docs.base.org)

Role in COOWN: Coinbase Layer 2 network (Ethereum-compatible); low fees, fast finality; COOWN uses Base for cost-effective ERC-20 token operations.

Key docs: - https://base.org — Main website - https://docs.base.org — Base developer documentation - https://docs.base.org/get-started/base — Getting started guide - https://docs.base.org/base-chain/network-information/network-fees — Network fees and gas optimization - https://base.blockscout.com/ — Base blockchain explorer

SDK/Libraries: Ethereum-compatible; use ethers or web3.js

Notes: Base is EVM-compatible L2; Coinbase-backed; COOWN integration via ICP EVM canister enables direct Base chain interactions.

EVM on ICP (docs.internetcomputer.org)

Role in COOWN: ICP canister running embedded Ethereum Virtual Machine; enables direct smart contract execution on EVM chains from ICP canisters without external bridges.

Key docs: - https://internetcomputer.org/docs/current/developer-docs/multi-chain/ethereum/overview — EVM integration overview - https://internetcomputer.org/docs/current/developer-docs/multi-chain/ethereum/evm-rpc — EVM RPC canister documentation - https://internetcomputer.org/docs/current/developer-docs/defi/chain-fusion/ — Chain Fusion technology - https://github.com/internet-computer-protocol/evm-rpc-canister — EVM RPC canister source

SDK/Libraries: Accessed via Motoko/Rust canister code; no separate SDK

Notes: COOWN's sign_backend canister (Rust) uses threshold ECDSA to sign EVM transactions; no third-party bridge fees or risks.

Infrastructure

Hetzner (hetzner.com, docs.hetzner.com)

Role in COOWN: Server hosting provider for development and testing infrastructure (not production — production runs on ICP).

Key docs: - https://hetzner.com — Main website and product catalog - https://docs.hetzner.com — Documentation hub - https://docs.hetzner.com/cloud/ — Hetzner Cloud documentation - https://community.hetzner.com/ — Community forum and support

SDK/Libraries: Hetzner Cloud API (hcloud CLI tool)

Notes: Used for non-critical testing infrastructure; COOWN production runs entirely on Internet Computer.

Cloudflare (cloudflare.com, developers.cloudflare.com)

Role in COOWN: DNS management, CDN, and DDoS protection for COOWN domains; provides security layer in front of ICP-hosted frontend.

Key docs: - https://cloudflare.com — Main website - https://developers.cloudflare.com — Developer documentation - https://developers.cloudflare.com/dns/ — DNS management docs - https://developers.cloudflare.com/api/ — Cloudflare API reference - https://dash.cloudflare.com/ — Cloudflare dashboard

SDK/Libraries: Cloudflare API (RESTful); cloudflare npm package

Notes: DNS records for coown.finance and related domains managed via Cloudflare; registered at GoDaddy.

Related docs: software-inventory.md

GoDaddy (godaddy.com)

Role in COOWN: Domain registrar for COOWN domains including coown.finance and managed-trust.com.

Key docs: - https://godaddy.com — Main website (⚠️ may block automated fetch; accessible via browser) - https://developer.godaddy.com/ — API documentation - https://www.godaddy.com/help — Help center

SDK/Libraries: GoDaddy API (RESTful)

Notes: DNS managed via Cloudflare; GoDaddy used only for domain registration and renewal.

Related docs: software-inventory.md

Tailscale (tailscale.com, tailscale.com/kb)

Role in COOWN: VPN mesh network for secure internal infrastructure access; used for development team remote access to internal systems.

Key docs: - https://tailscale.com — Main website and product overview - https://tailscale.com/kb — Knowledge base and documentation - https://tailscale.com/kb/start/ — Getting started guide - https://tailscale.com/kb/api/ — Tailscale API documentation - https://login.tailscale.com/ — Tailscale admin console

SDK/Libraries: tailscale CLI tool; API client libraries available

Notes: WireGuard-based; zero-trust network access; used for secure internal communications and infrastructure management.

GitHub (github.com, docs.github.com)

Role in COOWN: Source code repository hosting, version control, CI/CD pipelines, and issue tracking for all COOWN development.

Key docs: - https://github.com — Main platform - https://docs.github.com — GitHub documentation - https://docs.github.com/en/actions — GitHub Actions (CI/CD) - https://docs.github.com/en/rest — GitHub REST API - https://github.com/coown-box — COOWN GitHub organization (⚠️ private repos)

SDK/Libraries: octokit (npm), git CLI, GitHub Actions runners

Notes: All COOWN repositories are private; CI/CD deployment to ICP canisters automated via GitHub Actions.

Related docs: software-inventory.md

Notifications & Email

OneSignal (onesignal.com, documentation.onesignal.com)

Role in COOWN: Push notifications and email delivery service for COOWN platform; handles transaction alerts, payment notifications, and marketing communications.

Key docs: - https://onesignal.com — Main website and product overview - https://documentation.onesignal.com — Documentation hub - https://documentation.onesignal.com/docs/onboarding-with-onesignal — Getting started - https://documentation.onesignal.com/reference/api-overview — API reference - https://dashboard.onesignal.com/ — OneSignal dashboard

SDK/Libraries: onesignal-node (npm), Web Push SDK, mobile SDKs

Notes: Supports push notifications (web/mobile), email, SMS, in-app messaging; used for real-time transaction notifications and user engagement.

Related docs: software-inventory.md

Compliance & Regulatory

PolyReg (polyreg.ch)

Role in COOWN: Swiss Self-Regulatory Organization (SRO) for anti-money laundering compliance; COOWN's PolyReg membership application enables legal operation as VASP in Switzerland.

Key docs: - https://polyreg.ch — Main website - https://polyreg.ch/de/mitgliedschaft — Membership information (German) - https://polyreg.ch/de/reglemente — Regulations and compliance framework

SDK/Libraries: N/A (regulatory body, not technical service)

Notes: PolyReg membership equivalent to VASP license in Switzerland; supervised by FINMA; COOWN application status: Q2 2026 target approval.

Related docs: coown-platform-description.md § Regulatory & Compliance

FINMA (finma.ch)

Role in COOWN: Swiss Financial Market Supervisory Authority; regulates PolyReg and oversees Swiss VASP compliance; COOWN subject to FINMA oversight via PolyReg.

Key docs: - https://finma.ch — Main website - https://finma.ch/en/finma/supervised-institutions/self-regulatory-organisations-sros/ — SRO supervision information - https://finma.ch/en/authorisation/self-regulatory-organisations-sros/ — SRO authorization guidance - https://finma.ch/en/documentation/dossier/dossier-fintech/ — FinTech and crypto guidance

SDK/Libraries: N/A (regulatory body)

Notes: FINMA = Eidgenössische Finanzmarktaufsicht (Federal Financial Market Supervisory Authority); governs Swiss financial services including crypto asset service providers.

MiCA (EU Markets in Crypto-Assets Regulation)

Role in COOWN: EU regulatory framework for crypto-assets effective 2024; governs stablecoin issuers (Monerium, Circle) and crypto service providers (COOWN as CASP).

Key docs: - https://ec.europa.eu/info/business-economy-euro/banking-and-finance/financial-markets/markets-in-crypto-assets-regulation-mica_en — Official EU MiCA page - https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32023R1114 — MiCA regulation full text - https://www.esma.europa.eu/policy-activities/crypto-assets — ESMA guidance on crypto-assets

SDK/Libraries: N/A (regulatory framework)

Notes: MiCA establishes pan-EU licensing for crypto service providers; COOWN partners (Monerium, Circle) are MiCA-compliant; COOWN monitoring MiCA compliance requirements for future EU expansion.

AI & Agent Operations

OpenClaw (docs.openclaw.ai, github.com/openclaw/openclaw)

Role in COOWN: AI agent orchestration framework powering COOWN's agent swarm (Maya, analysts, ops agents); provides session management, memory, tool routing, and multi-agent coordination.

Key docs: - https://docs.openclaw.ai — Official OpenClaw documentation - https://github.com/openclaw/openclaw — Open-source repository - https://docs.openclaw.ai/getting-started — Installation and setup guide - https://docs.openclaw.ai/agents — Agent configuration and deployment

SDK/Libraries: openclaw npm package (⚠️ verify package name if integrating)

Notes: Self-hosted gateway connecting chat apps (WhatsApp, Telegram, Discord) to AI agents; COOWN swarm uses OpenClaw for multi-agent workflows, memory management, and tool access control.

Related docs: infrastructure-ops/asset-inventory/ai-swarm/ (⚠️ create if missing)

Anthropic (anthropic.com, docs.anthropic.com)

Role in COOWN: LLM provider for Claude models (Opus, Sonnet, Haiku); primary AI backend for COOWN agent swarm reasoning and task execution.

Key docs: - https://anthropic.com — Main website and company information - https://docs.anthropic.com — Claude API documentation - https://docs.anthropic.com/en/api/getting-started — API quickstart - https://docs.anthropic.com/en/docs/about-claude/models — Model comparison and capabilities - https://console.anthropic.com/ — Anthropic developer console

SDK/Libraries: @anthropic-ai/sdk (npm)

Notes: COOWN agents use Claude Opus 4 for complex reasoning, Sonnet 4 for balanced tasks, Haiku for fast/simple operations; API key required; costs managed per token usage.

Related docs: glossary.md § Agent, Cloud Model

Frontend & Productivity

React (react.dev)

Role in COOWN: JavaScript UI library for building COOWN frontend web application; provides component-based architecture for responsive, interactive user interface.

Key docs: - https://react.dev — Official React documentation - https://react.dev/learn — React learning path and tutorials - https://react.dev/reference/react — React API reference - https://github.com/facebook/react — React source code

SDK/Libraries: react, react-dom (npm); COOWN uses React 18+

Notes: COOWN frontend (sifoc-qqaaa-aaaap-ahorq-cai) built with React; hosted on ICP canisters; uses Redux for state management and Tailwind CSS for styling.

Related docs: system-architecture.md § Frontend

Google Workspace (workspace.google.com, developers.google.com/workspace)

Role in COOWN: Email (Gmail), calendar (Google Calendar), cloud storage (Google Drive), and team collaboration for COOWN operations and internal communications.

Key docs: - https://workspace.google.com — Main website and product overview - https://developers.google.com/workspace — Developer documentation - https://developers.google.com/workspace/guides — Integration guides - https://developers.google.com/gmail/api — Gmail API reference - https://developers.google.com/calendar — Google Calendar API

SDK/Libraries: googleapis (npm), Google API Client Libraries

Notes: Domain managed-trust.com hosted on Google Workspace; service account maya@managed-trust.com used for agent operations.

Related docs: TOOLS.md § Google Workspace

Cross-References

External Provider Lists

For additional provider comparisons and alternatives, see: - Multisig wallet competitors: competitors.md

Maintenance Notes

URL Verification Protocol: All URLs in this document were verified accessible via web_fetch on 2026-02-12. If a URL becomes inaccessible: 1. Check provider's main domain for updated documentation links 2. Search provider's GitHub organization for alternative documentation 3. Mark with ⚠️ and note "verify URL" until replacement found

Update Triggers: Update this document when: - New provider/partner integration added to COOWN - Provider changes documentation URL structure - Major version changes in SDKs/APIs - Provider service discontinued or replaced - Quarterly review (align with product roadmap updates)

Ownership: Maya (🐝) + CTO Review Frequency: Quarterly or upon major platform changes Next Review: 2026-05-12

Document Control: - Version: 1.0 - Created: 2026-02-12 - Author: Maya (AI Agent - COOWN Swarm) - Approved by: Pending (CTO review required) - Classification: Internal Reference (Non-Confidential)