Cowrie Research

opentrade

4 min read

OpenTrade

  • Name: OpenTrade
  • URL: https://www.opentrade.io/
  • Category: stablecoin-yield and treasury-management company / tokenized-credit and legal-structuring operator / white-label yield infrastructure company
  • Tags: ethereum-ecosystem avalanche-ecosystem
  • Summary: OpenTrade belongs in companies/, not mainly projects/, because the durable dependency is a named operator-and-entity stack that develops the platform, controls onboarding and wallet whitelisting, chooses which borrower and legal structure sit behind the yield products, and packages banks, custodians, broker/dealers, and compliance vendors into one company-shaped shell. The useful question is not just what vault or tokenized-yield product exists? but which named operator controls admission, legal architecture, borrower approval, product packaging, and the offchain institutions that make the platform work?
  • What it does:
    • Builds and operates a stablecoin-yield and treasury-management platform used by fintechs, exchanges, wallets, custodians, and treasury operators
    • Packages white-labeled and embedded yield products rather than only one direct-investment vehicle
    • Develops and maintains the OpenTrade platform, web app, and blockchain protocol through Open Trade Technology Ltd., which the docs explicitly name as the platform provider
    • Runs an onboarding path that requires KYC/AML/CFT review, master-agreement execution, and whitelisting of supported wallets before users can interact with the platform
    • Frames the legal operating shell around OpenTrade SPC as the currently approved borrower, OpenTrade Foundation as the sole shareholder preserving bankruptcy remoteness, and a broader network of external banks, broker/dealers, custodians, and trustees
    • Exposes API and protocol packaging so downstream partners can embed treasury and yield products inside their own apps and workflows
  • Key claims:
    • The homepage says fintechs use OpenTrade to power stablecoin yield products for their customers and to manage treasuries, which is a company-and-partner-distribution framing rather than a standalone vault note
    • The docs welcome page says OpenTrade combines blockchain infrastructure, a legal framework, and regulated financial institutions, which is the cleanest first-party signal that the company boundary matters separately from any one product
    • The key-parties docs explicitly name Open Trade Technology Ltd. as the platform provider responsible for the platform, web app, and blockchain protocol
    • The same key-parties docs say OpenTrade SPC is currently the only approved borrower for the Treasury Management Product, while OpenTrade Foundation is the sole shareholder used to keep the SPC bankruptcy remote
    • The key-parties page also makes the surrounding operator map unusually legible by naming Five Sigma Finance as investment advisor, Vantru as security trustee, Circle for USDC custody and mint/redeem access, plus the regulated banks, broker/dealers, custodians, legal counsel, and KYC/compliance vendors wrapped into the stack
    • The legal docs say the stablecoin-yield products use secured lending to a bankruptcy-remote Cayman SPC operated by an independent board and an FCA-regulated investment firm, which means the legal shell is part of the product, not incidental back-office detail
    • The onboarding docs say access requires KYC/AML/CFT screening, execution of the Master Lending Agreement, and wallet whitelisting, while the eligibility docs say retail users are not eligible; this makes admission and user-type gating part of the operator boundary
  • Whitepaper: No standalone company whitepaper is the artifact that matters here. The useful primary materials are OpenTrade’s homepage, docs welcome page, legal and key-party pages, onboarding materials, and the focused source capture in ../whitepapers/opentrade-company-primary-sources-2026-08-09.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • opentrade is intentionally only an alias now because the prior note had already become a company/operator analysis rather than a clean protocol or product-mechanism note.
  • The durable control surface sits with OpenTrade as a named operator-and-entity map: platform development, onboarding, wallet whitelisting, borrower approval, legal-structure selection, and the packaging of banks / custodians / broker/dealers / trustees do not reduce cleanly to one ERC-4626-style vault or one tokenized-credit product.
  • Keep lower-layer protocol questions on the Perimeter / ERC-4626 lineage or on specific asset/product notes when needed; use this note when the real question is who controls admission, structure, and the easiest operating path around the stack.

Control surface

  • Practical authority sits in partner and lender onboarding, KYC/AML/CFT and sanctions workflow, wallet whitelisting, approved-borrower selection, legal-structure maintenance, product-menu curation, supported stablecoin and network packaging, and the company-chosen banking / custody / broker / trustee relationships that make the system marketable.

  • The sticky dependency is operational rather than purely contractual: users and partners depend on OpenTrade to keep the borrower and legal shell intact, maintain the integration and whitelist workflow, coordinate the offchain institutions, and preserve the compliance posture that gives the onchain wrappers meaning.

  • Read OpenTrade as a company-run treasury and yield operating shell first. The real choke points are the named operator, approved entities, and workflow gates around the products, not the existence of one more onchain yield wrapper.

  • Last reviewed: 2026-08-09 UTC

Graph View

Backlinks