Over-collateralised RWA lendingAscend pools screened institutional cash to lend against tokenised RWA wrappers.
Security-backed credit lineAscend extends a credit line against tokenised securities wrappers to screened lenders.
Use-case decision board
This board sets the decisions that sit downstream of it: what we offer, how we go to market, and where liquidity comes from. Every use case is a pair, the compliance of the collateral by the compliance of the liquidity. Pick the pair we lead with and the rest follows. The plan that flows from it is on Roadmap & plan.
01
The board
Rows are collateral, or supply, compliance. Columns are liquidity, or demand, compliance. Read a partner's place by asking both questions, not one.
Collateral · supply compliance
Liquidity →
Collateral ↓
Collateral ↓
LOW · permissionlessDeFi bridge · Morpho, Aave v4
MID · light KYCInstitutional DeFi · Aave Horizon
HIGH · full KYCOnchain finance · Canton, Tradeweb, DTCC
HIGHtoken is the origin security · native title · exempt transaction · licensed issuer
What we built
Offshore only. A licence moves you up to HIGH demand; it does not make onshore-permissionless compliant.
Over-collateralised lendingAscend lets offshore borrowers raise permissionless liquidity against fully-compliant tokenised securities.
Repo (offshore)Ascend runs the permissioned-collateral pool; offshore cash repos the securities permissionlessly.
Cash cow
Repo (institutional)Ascend pools sanctions-screened institutional cash to finance tokenised treasuries.
Security-backed credit lineAscend extends credit against tokenised securities to a screened institutional pool.
Over-collateralised lendingAscend over-collateralises every loan and screens liquidity for sanctions and jurisdiction.
Lead
Both sides KYC, settled DvP. South Street · TradePro · PSG · Apex + BitGo. What South Street and DTCC unlock.
RepobeachheadAscend runs the permissioned pool where a broker-dealer repos tokenised treasuries against KYC’d cash.
Securities lendingAscend matches lender and borrower onchain and enforces eligibility on every loan.
Security-backed credit lineAscend lets a wealth or broker business extend credit against a client’s tokenised portfolio.
Leveraged lendingAscend enforces collateral and margin onchain so KYC’d capital can lend with leverage.
Structured products / MBSAscend tokenises the tranche as collateral and gates who can hold and finance it.
MIDprivate security or wrapper · still a securities transaction, title offchain · Denari ~300
Over-collateralised lendingAscend’s pool lends permissionless liquidity against a tokenised wrapper of a private security.
Haircut
Live, at a wrapper haircut. Open: whether broker-dealer suitability accepts wrapper title.
Onchain ADR lendingAscend lets KYC’d lenders finance a tokenised wrapper of a public security, at a haircut.
Haircut repoAscend runs the KYC’d pool that repos tokenised wrappers of public securities at a discount.
LOWeconomic-only / non-security · offshore Reg S, commodities · Tezos, Acacia
Park
A knife-fight with Morpho and Aave for liquidity.
Generic crypto lendingAscend can run a permissionless pool here, but with no compliance edge, no moat.
No taker
No US-takeable security on the collateral side. A gated lender has nothing compliant to lend against, so you would just run pure permissionless instead.
No taker
Fully-KYC’d capital exists to take securities risk under a US exemption. Offshore economic representations of non-securities give it no qualifying asset.
Lead, invest
Cash cow, harvest
Watch, locked onshore
Park
Incoherence rule. A gated lender needs a US-takeable security to lend against. No securities transaction on the collateral side (LOW) means no taker, so those cells are dead. A wrapped security (MID) is live, at a haircut. The cut is whether the transaction is a securities transaction, not gate-versus-grade. What we built sits in the one cell locked onshore; South Street and DTCC open the top-right, the only cell where Ascend solves the risk and stays the venue.
How to read the cells: each is a space to find plays, not just slot partners
A cell is not one product. Each reachable cell above lists the activities its compliance shape allows, with a plain-language line on how Ascend, as ERC-3643-native private credit on a tri-party model, would serve each. Hover any use case for what the term means and the rule that governs it. The lead cell makes the point: South Street plus DTCC is, strictly, a single use case, repo, but the same HIGH–HIGH rails carry a stack of distinct markets. Lead with one, treat the rest as expansion.
The discipline: read every reachable cell for “what activity could live here”, then let where to play rank them. It surfaces near-term plays, not just the lead: the cash-cow cell (HIGH–MID) can ship a real credit product before the full pool exists, a security-backed line of credit or securities-lending desk on native collateral funded by light-KYC institutional liquidity. A play the board finds, not a partner we already hold.
Licences cover specific functions, not all of these: each broker-dealer registration names the activities it may clear. Confirm scope per use case with counsel before slotting.
02
How to read the two axes
Collateral / supply, to what degree is it a securities transaction
HIGHThe token is the origin security, issued onchain-native by a licensed issuer in an exempt transaction (Reg D, Reg A+) or registered. Unambiguously a securities transaction, native title.
MIDA private security, or a wrapper of a public security (Denari). Still a securities transaction, but title sits offchain with a custodian, so the token is an economic claim, an onchain ADR. The securities test says yes; the title-authority test says wrapper.
LOWAn economic-only representation: the crypto asset is a non-security, offshore (Reg S) economic representations or commodities such as uranium. Not a securities transaction.
Liquidity / demand, how compliant is the cash and who may bring it
HIGHFull KYC, broker-dealer-intermediated, dealing in dollars or dollar-equivalents. Identity enforced onchain via ONCHAINID / ERC-3643, the enforcement mechanism rather than the tier itself.
MIDLight KYC: a sanctions and jurisdiction screen at the door, not accreditation or suitability (Aave Horizon). Cash is a KYC’d stablecoin such as USDC.
LOWPermissionless, no KYC: a sanctions and geoblock floor only (Morpho, Aave v4). Cash is crypto or a non-KYC stablecoin, wrapped BTC / ETH or Tether.
Primitive: to what degree is the transaction a securities transaction? If it triggers the securities rules in any form, Reg D, Reg S, a wrapper, a warrant, it needs the controls (KYC, suitability). A second, orthogonal question sets title risk: does the token carry native legal title, or is it a wrapper claiming a share held offchain?
Licence legend. Products are the securities. Businesses are the licensed entities that can transact (South Street, TradePro; PSG’s ADGM and HK licences). Software is Ascend, which operates on top of a licensed business, never as the registrant itself. The licensed business is the key that unlocks the onshore cells, and that business can be us: the deal to operate through a FINRA-registered broker-dealer is agreed with TradePro (80/20), with the change-of-control registration subject to FINRA approval (Rule 1017), in progress. Once cleared, the HIGH band shifts from a licence we rent to rails we own.
03
Where to play
Build for HIGH–HIGH, then walk the demand axis left as the market allows. The collateral side stays HIGH because it is securities.
Low moat, feeds another venue
High moat, Ascend is the venue
Higher upside
Question marks, decide
HIGH–LOW (what we built; keep as offshore optionality) and the Denari row.
Stars, invest
HIGH–HIGH onchain finance (South Street + DTCC). Lead here.
Steadier
Dogs, park
LOW–LOW pure DeFi clone. A knife-fight with Morpho and Aave.
Cash cows, harvest
HIGH–MID permissioned credit + Horizon. Near-term, once live.
Supply-side compliance is where Ascend solves the risk, the real edge. The demand side is about control: own the gated pool and Ascend is the venue, with the credit facility able to intercede; leave demand permissionless and Ascend is one integration into someone else’s venue. The case for gating demand is control and moat, set apart from any single revenue line.
04
The squeeze: the cash is real, but not on DeFi
Split liquidity by source. The DeFi pool we can actually reach is small and mostly committed. The deep cash sits in the traditional system, in repo and money-market funds. The answer is not to fight for DeFi liquidity, it is to bring traditional fiat cash onchain through the broker-dealer, settled DvP, with BitGo as the cash-custody leg, not a liquidity source.
Traditional sources, off this scale entirely. US repo runs ~US$12.6T/day of exposures; US money-market funds hold ~US$7.9T. That is two orders of magnitude past the onchain pool, reachable through the broker-dealer book and DvP cash, not through DeFi. The gap is the case for HIGH–HIGH.
Bars on one scale, baseline US$100B. The DeFi set spans permissionless pools (Aave, Morpho) and the institutional onchain-credit venues (Maple, Centrifuge, Goldfinch, Horizon); even summed, the reachable onchain total is a fraction of Apex alone, and the total stablecoin market ~US$320B is mostly committed (off-scale here). Every accessible onchain venue is LOW or MID tier; the HIGH-tier cash our lead needs comes from the traditional system through the broker-dealer.
05
Guardrails
Read before slotting anything as buildable.
Onshore plus permissionless is not a compliant cell. It opens only offshore or on a licensed business. A licence unlocks onshore HIGH demand, not onshore-permissionless.
“Exempt” is not one thing. A HIGH cell names its pathway: Reg D, Reg A+, Reg S, or 144A. The wrong one re-restricts the asset downstream.
Offshore (Reg S) is a door, not a delete. It drops US registration, not the distribution and resale conditions that come with it.
“The token is the security” holds only if a registered transfer agent treats the chain as the record. Verify per issuer.
Some figures are internal or simulated; market figures are independently verified. Not production.
06
Recommendation
Lead · HIGH–HIGHBuild for high, walk it back
DecisionCommit the HIGH–HIGH band now and build the beta against it. Anchor on South Street, with our own FINRA-registered broker-dealer via TradePro (deal agreed, registration pending approval) as the structural unlock, and BitGo as the DvP cash leg.
Why highNot because we cannot run the lower tiers in parallel; the modular build makes that cheap. For focus and positioning: one engineering target, one go-to-market story, and a deliberate posture as the institutional rail behind the retail-forward DeFi projects, not in a retail knife-fight with them. The boring, high-compliance lane is the defensible one.
BuildModular: the HIGH permissioned pool subsumes the lower-tier compliance logic, so MID and LOW reuse it via adapters rather than a re-architecture. The HIGH pool is the most complex build and is still to be designed; once it exists, stepping down is cheap.
Onshore firstOnshore is the primary use case; offshore is the secondary. Dennis’s call, settling v1’s open fork. We will run both, primary and secondary, not one. The residual decision is narrower: the funding source for the onshore medium variant, KYC’d liquidity via Circle or equivalent. Hold that conversation, then decide it rather than let it drift.
NextSee Roadmap & plan for what ships at each milestone, who unlocks which cell, and what holds if the pipeline slips.
Manny E. Reimi
CPO, Ascend · [email protected]
First-pass strategy framing to structure the decision, not legal advice. Confirm the exemption, licensed entity, and transfer-agent structure per cell with counsel before building any cell.