A Permissioned Institutional Platform
Arcus combines Fireblocks MPC custody with a verification-first operating model. Key lifecycle events—origination, repayment, liquidation—are anchored to Bitcoin Layer 1 for immutable evidence, while access is governed by KYC/KYB. Our mandate is principal preservation, operational clarity, and consistent, market-driven outcomes.
Proof of Operations
Lifecycle events are immutably evidenced via OP_RETURN on Bitcoin L1.
Client onboarding, policy configuration, and loan creation.
Hash of event fields anchored on-chain for verification.
Interest accruals settled, partial or full prepayment permitted.
Disciplined process with conservative thresholds and penalties.
Risk Studio
Explore hypothetical drawdowns and see indicative effects on collateralization. This illustration simplifies model behavior for demonstration.
Policy Parameters
Initial BTC LTV ~60%, liquidation threshold ~75%. Fees include 2% origination, 5% liquidation, and 1% performance. Partial, automated liquidations may be employed to preserve principal.
Institutional Product Suite
Yield Accounts • Over-Collateralized Credit • Lending-as-a-Service API
Yield Accounts
Permissioned pools with market-driven rates and custom reporting.
Credit
Flexible liquidity against BTC with conservative LTVs.
LaaS API
Versioned REST, mTLS, RBAC, and dedicated integration support.
Compliance & Jurisdictions
Operating posture is aligned with a Cayman VASP framework with US expansion planning for appropriate licensing. Access is permissioned and designed to support institutional requirements for auditability.
Regulatory map / regions placeholder
Leadership & Governance
Coverage-led service model with accountability and clear decision rights.
Partners & Integrations
Frequently Asked Questions
Who is the platform for?
Family offices, institutional allocators, and enterprise partners seeking Bitcoin-native yield and credit in a permissioned environment.
How are assets secured?
Custody is administered via Fireblocks MPC. Administrative actions are governed by a policy engine with multi-party approvals.
How is transparency provided?
We anchor hashes of key lifecycle events to Bitcoin Layer 1 via OP_RETURN for immutable, external verification.
Begin the Conversation
Request an NDA for the data room or schedule a management presentation.