The joint working doc maps who trades: five short-side and six long-side personas. This page adds the Ascend side — the personas that custody, clear, and settle the trade — and the seven-step path every demand-side persona traverses. Prepared for the joint persona and economics workstream.
Spot BTC held in institutional custody, a short perpetual at the venue: delta-neutral, capturing the funding spread. The clearing layer in the middle is what makes both legs margin as one position — and it is the layer this page's personas inhabit.
Same-chain by design for the POC: collateral representation, stablecoin proceeds, and position receipts move on one shared permissioned network, so the liquidation path never crosses a bridge.
Sixteen personas across three groups. Demand-side one-liners condense the joint working doc; Ascend-side personas are developed in section 04.
| Id | Persona | Priority | What unblocks them |
|---|---|---|---|
| Short side — idle-BTC holders (joint working doc) | |||
| S1 | Multi-strategy hedge fund | Near-term | Runs the trade on listed futures today; wants 24/7 funding capture and both legs margined as one position. |
| S2 | Individual BTC whale | Near-term | Passive yield without selling or leaving institutional custody. |
| S3 | Family office | Near-term | Clean yield with no DeFi exposure, no OTC credit line, no custody change. |
| S4 | Public BTC miner | Medium-term | Earn or borrow against treasury instead of selling production to cover operating costs. |
| S5 | Corporate treasury | Later / scale | Auditable yield on an idle treasury without selling and without disclosure risk. |
| Long side — the other side of the perpetual (joint working doc) | |||
| L1 | Structured-product issuer / hedging desk | Near-term | A regulated onshore venue to hedge issued BTC-linked products at size. |
| L2 | Levered directional fund | Near-term | Portfolio-margined leveraged long without offshore venue and withdrawal risk. |
| L3 | Market maker / basis arbitrageur | Day one | Fair-ordered, low-latency depth; takes the long side whenever the perpetual trades cheap. |
| L4 | Asset manager, synthetic long | Medium-term | BTC exposure without a spot custody relationship. |
| L5 | High-frequency trader | To develop | Deterministic sequencing, direct connectivity, high throughput; card not yet developed in the working doc. |
| L6 | Retail directional | FCM-dependent | Regulated onshore perpetual access through a carried FCM account. |
| Ascend side — custody, credit, clearing (this contribution) | |||
| A1 | Balance-sheet / liquidity partner | Day one | Standardized secured lending against custody-verified collateral: one integration, many counterparties. |
| A2 | Institutional custodian | Day one | Keeps the asset and adds a yield story; the custody model is unchanged. |
| A3 | FCM | Later / scale | Carries retail accounts; this persona decides the retail path's viability. |
| A4 | Clearing and risk operations | Operator | Margin calls, liquidation, default management, and the audit trail a regulator inspects. |
| A5 | Compliance and claims | Operator | One onboarding, three claim species, revocation that propagates. |
The scenarios in the working doc stop at "Path: TBD." The path is the same seven steps for every persona; what varies is the entry point and which steps the client sees.
Registration and claims
One KYC, whatever the entry point — Ascend acts as clearing agent for every client. Eligibility is expressed as onchain claims: three species, each issued by a different party. Asset ownership is attested by the custodian, margin-account participation by Ascend, position-holding by the venue. The client experiences a single registration.
Custody
BTC sits in, or moves to, the institutional custodian; omnibus accounts cover the reserve tiers that require them. The tokenized-ETF variant pledges an ETF position through the tokenization credit facility instead — no BTC custody relationship at all.
Collateral onchain, same chain
The POC runs on one shared permissioned network: collateral is represented against custody attestations and stablecoin proceeds move to the venue with no bridging. Removing the bridge removes bridge risk from the liquidation path. Compliance-embedded token standards carry the claims onchain; cross-chain portability is a later option, not a POC dependency.
Margin account and portfolio margining
Collateral is pledged under haircut and LTV policy. The reserve is bound to margin-account activity and responds per policy. Both legs margin as one position — the capital-efficiency unlock most demand-side cards cite.
Position
The perpetual opens at the venue against the margin account, and the venue issues an onchain receipt of the position.
Rehypothecation and the leverage loop
Tier-dependent: the position receipt can itself be pledged back as collateral for an additional credit line, bounded by correlation and concentration caps so looping stays contained. Segregated-tier accounts opt out of this step entirely — the distinction that resolves the "no rehypothecation" trust thresholds in section 05.
Daily lifecycle, unwind, default
Mark-to-market, margin calls, and funding settlement run on a daily cycle, with reserve auto-sizing and stress-loss policy underneath. A clean exit returns BTC to custody exactly as it entered. The default path runs margin call, liquidation, and default management under the clearing rulebook, recorded with attribution.
Three participants who join the network with their own economics, and two operators whose workflows are what a clearing regulator inspects.
A trading firm or credit desk providing stablecoin liquidity to the credit leg. The POC does not run without one.
Funds drawdowns against pledged collateral and takes the wholesale side of the credit spread — effectively the network's wholesale lender.
Spread on secured lending against over-collateralized, custody-verified BTC; materially better risk-adjusted than bilateral unsecured crypto credit.
Enforceable collateral claims, transparent margining, defined seniority in the default waterfall, custodian attestation of the underlying.
The regulated custodian holding client BTC — already the top acquisition channel for three demand-side personas.
The tri-party corner: holds the asset, issues the asset-ownership claim, executes attestations, provides omnibus accounts where reserve tiers require them, and anchors the promise that BTC never leaves custody.
Custody fees on balances that would otherwise leave for yield venues, plus relationship-manager cross-sell — credit-as-a-service for the existing book.
Clean legal separation between custody and the credit layer, operational APIs for attestation, insurance posture unchanged, a resolved connectivity path to the network.
A registered futures commission merchant willing to carry retail and non-ECP accounts for listed contracts.
Carries customer accounts, runs suitability and account-level margin, aggregates retail flow into the venue, holds segregated customer funds.
Commission per contract plus interest on customer balances; needs enough projected volume to justify onboarding a novel venue.
Regulatory certainty on the clearing and venue stack, mature margining APIs, and clarity on perpetual-specific retail eligibility. The retail persona's near-term status depends on whether this conversation is opened or deferred — and the membership model itself, direct members or FCM-carried accounts, sets the segregation regime, leverage caps, and the onboarding perimeter.
Operates the clearing layer: per-account and per-facility health, margin calls, liquidations, the default waterfall, and the audit trail.
Near-real-time collateral and margin monitoring across the custodian, Ascend, and venue views; reserve policy operation; concentration-cap oversight on the leverage loop; intervention controls — pause, freeze, clawback — with full audit logging.
Clearing-license approval is substantially an evaluation of whether these workflows exist and are auditable. The POC should demonstrate the operator view, not only the client view.
Defines and operates the claims topology — providers, claim types, issuance rules — and owns the KYC handoff when clients enter via the venue or a custodian referral.
One onboarding, three claim species, each issued by a different party but experienced as a single registration; revocation that propagates, so a revoked claim gates new positions immediately; an audit trail per claim.
Every demand-side card's "fully KYC'd" premise is this persona's output. The onboarding friction that decides whether a first test allocation ever happens is owned here.
What the joint workstream should settle next. One decision, eight items.