BTC basis trade POC — personas and the path to settlement

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.

Personas mapped 16 11 demand-side (joint working doc) · 5 Ascend-side (this page)
Short side5hedge fund → corporate treasury
Long side6structured issuer → retail
Ascend side53 participants · 2 operators
Path steps7registration → default
01

The trade and the layer

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.

Institutional custody
BTC stays with the custodian · asset-ownership claim issued · omnibus accounts where reserve tiers require them
Ascend — clearing layer
claims · margin account · haircut and LTV policy · reserve bound to account activity · credit and rehypothecation by tier
Monolith — venue
perpetual opened against the margin account · onchain position receipt · funding settled through the clearing layer

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.

02

Persona map

Sixteen personas across three groups. Demand-side one-liners condense the joint working doc; Ascend-side personas are developed in section 04.

IdPersonaPriorityWhat unblocks them
Short side — idle-BTC holders (joint working doc)
S1Multi-strategy hedge fundNear-termRuns the trade on listed futures today; wants 24/7 funding capture and both legs margined as one position.
S2Individual BTC whaleNear-termPassive yield without selling or leaving institutional custody.
S3Family officeNear-termClean yield with no DeFi exposure, no OTC credit line, no custody change.
S4Public BTC minerMedium-termEarn or borrow against treasury instead of selling production to cover operating costs.
S5Corporate treasuryLater / scaleAuditable yield on an idle treasury without selling and without disclosure risk.
Long side — the other side of the perpetual (joint working doc)
L1Structured-product issuer / hedging deskNear-termA regulated onshore venue to hedge issued BTC-linked products at size.
L2Levered directional fundNear-termPortfolio-margined leveraged long without offshore venue and withdrawal risk.
L3Market maker / basis arbitrageurDay oneFair-ordered, low-latency depth; takes the long side whenever the perpetual trades cheap.
L4Asset manager, synthetic longMedium-termBTC exposure without a spot custody relationship.
L5High-frequency traderTo developDeterministic sequencing, direct connectivity, high throughput; card not yet developed in the working doc.
L6Retail directionalFCM-dependentRegulated onshore perpetual access through a carried FCM account.
Ascend side — custody, credit, clearing (this contribution)
A1Balance-sheet / liquidity partnerDay oneStandardized secured lending against custody-verified collateral: one integration, many counterparties.
A2Institutional custodianDay oneKeeps the asset and adds a yield story; the custody model is unchanged.
A3FCMLater / scaleCarries retail accounts; this persona decides the retail path's viability.
A4Clearing and risk operationsOperatorMargin calls, liquidation, default management, and the audit trail a regulator inspects.
A5Compliance and claimsOperatorOne onboarding, three claim species, revocation that propagates.
03

The path through Ascend

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.

  1. 01

    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.

  2. 02

    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.

  3. 03

    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.

  4. 04

    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.

  5. 05

    Position

    The perpetual opens at the venue against the margin account, and the venue issues an onchain receipt of the position.

  6. 06

    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.

  7. 07

    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.

04

Ascend-side personas

Three participants who join the network with their own economics, and two operators whose workflows are what a clearing regulator inspects.

A1

Balance-sheet / liquidity partner

Day one
Who

A trading firm or credit desk providing stablecoin liquidity to the credit leg. The POC does not run without one.

Role in the stack

Funds drawdowns against pledged collateral and takes the wholesale side of the credit spread — effectively the network's wholesale lender.

Economics

Spread on secured lending against over-collateralized, custody-verified BTC; materially better risk-adjusted than bilateral unsecured crypto credit.

Trust threshold

Enforceable collateral claims, transparent margining, defined seniority in the default waterfall, custodian attestation of the underlying.

A2

Institutional custodian

Day one
Who

The regulated custodian holding client BTC — already the top acquisition channel for three demand-side personas.

Role in the stack

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.

Economics

Custody fees on balances that would otherwise leave for yield venues, plus relationship-manager cross-sell — credit-as-a-service for the existing book.

Trust threshold

Clean legal separation between custody and the credit layer, operational APIs for attestation, insurance posture unchanged, a resolved connectivity path to the network.

A3

FCM

Later / scale
Who

A registered futures commission merchant willing to carry retail and non-ECP accounts for listed contracts.

Role in the stack

Carries customer accounts, runs suitability and account-level margin, aggregates retail flow into the venue, holds segregated customer funds.

Economics

Commission per contract plus interest on customer balances; needs enough projected volume to justify onboarding a novel venue.

Trust threshold

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.

Operator · policy-governed
A4

Clearing and risk operations

Role

Operates the clearing layer: per-account and per-facility health, margin calls, liquidations, the default waterfall, and the audit trail.

Jobs in the POC

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.

Why this is a persona

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.

Operator · policy-governed
A5

Compliance and claims

Role

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.

Jobs in the POC

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.

Why this is a persona

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.

05

Open items

What the joint workstream should settle next. One decision, eight items.

Decision — viability scoping and account tiers
The persona set is broader than the POC's economics support: two cards (miner, corporate treasury) list "no rehypothecation" as a trust threshold while the yield mechanics assume rehypothecation, and several others differ from the stated custody premise. Proposed resolution in two moves. First, scope to viable users: each demand-side card states whether it can rehypothecate and how it meets custody, and a persona that can do neither moves to a later phase rather than diluting the POC cast. Second, price the two account tiers separately: segregated — no rehypothecation, custody-preserving, lower yield — and rehype-enabled, with the leverage loop bounded by concentration caps.
  1. Premise line. "Every persona is fully KYC'd and holds BTC within an institutional custodian" no longer holds across the cast — the ETF variant, the synthetic long, and retail all differ. Soften to "fully KYC'd; custody arrangements vary by persona."
  2. Table and card drift. The high-frequency trader appears in the summary table with no detailed card, and the retail row reads "not targeted onshore" while its card describes a viable onshore path. Reconcile both.
  3. Path fields. "Path: TBD" in the whale and family-office scenarios — replaced by the shared seven-step path in section 03, referenced from each scenario rather than duplicated.
  4. Scenario coverage. Three personas carry full scenarios (trigger, entry, objection, exit condition — a strong format); the rest have none. Extend by priority tier.
  5. FCM and membership model. State whether the FCM is a POC-phase conversation or deferred, and take the membership-model decision alongside it: direct members or FCM-carried accounts, retail in scope or ECP-only. The choice sets the segregation regime, leverage caps, and the onboarding perimeter.
  6. Eligibility precision. The family-office card reuses the individual ECP threshold; family offices typically qualify as entities, so the binding constraint differs.
  7. Product economics to settle. The clearing-fee split with the venue, how the default resources are funded and by whom, and the instrument any skin-in-the-game is held in. Routed to the economics workstream; the persona cast above is where each question attaches.
  8. Default-path enforceability across the venue boundary. Recovery on the venue leg depends on close-out and claim arrangements agreed with the venue: who instructs position close-out in a default, and how the clearing layer's claim is perfected. A legal and integration item rather than engineering, and an input to the tier pricing above.
Manny E. Reimi
Author Manny E. Reimi CPO, Ascend · manny@ascend.gl
Dennis O'Connell
Author Dennis O'Connell CEO & CTO, Ascend · dennis@ascend.gl
v0.5.1 · 2026-07-21
Working draft for the joint persona and economics workstream. For discussion; not an offer or solicitation.