Abstract
Collapse is a protocol for making stablecoin balances productive by default without sacrificing instant usability. It introduces a new financial primitive for stablecoin-native businesses: Point of Transfer Execution.
Rather than separating wallets, treasury, and yield into distinct systems, the protocol collapses them into a single capital layer where balances remain allocated to yield-bearing instruments until the precise moment liquidity is required. At transfer or redemption, the protocol sources or creates stablecoin liquidity just in time, using a combination of NAV-based convertibility, short-duration credit facilities, and programmable asset routing.
The result is a treasury system where capital is continuously productive, liquidity is dynamically provisioned, and users no longer face a trade-off between earning yield and maintaining operational flexibility.
This litepaper outlines the protocol's motivation, design principles, architecture, operational flow, and key risk considerations.
1. Motivation
Stablecoins have become core infrastructure for payments, trading, treasury, FX, and internet-native financial applications. They move globally, settle continuously, and increasingly sit at the center of business operations.
Yet the way stablecoin balances are managed still reflects an older financial model.
Today, firms typically:
- hold stablecoins in wallets for availability
- move excess balances into separate yield products
- pre-fund liquidity across venues and workflows
- manually decide what remains liquid versus productive
This creates structural inefficiency. Operational balances remain idle not because they lack utility, but because liquidity must be preserved in advance.
As stablecoins become the default balance sheet asset for FX platforms, PSPs, exchanges, wallets, and intent-based systems, this design becomes increasingly costly. What is needed is not a better yield product layered on top of wallets, but a protocol designed from the ground up for balances that must simultaneously earn, settle, and move.
2. Protocol Overview
Collapse is a treasury protocol that enables:
- continuous yield on stablecoin balances
- instant liquidity at the point of use
- deterministic conversion between yield-bearing assets and settlement stablecoins
- programmable treasury orchestration for stablecoin-native applications
At its core, the protocol treats yield-bearing collateral and spendable stablecoins not as separate states, but as interchangeable forms of the same monetary base.
This is achieved through a design we describe as:
Point of Transfer Execution
Capital remains in productive form by default and only converts into settlement-ready stablecoins when a transfer, payment, or withdrawal is initiated.
3. Core Design Principles
3.1 Yield by Default
All eligible balances should be productive from the moment they enter the system. Yield is not an opt-in feature or a separate account action. It is the base state of capital.
3.2 Just-in-Time Liquidity
Liquidity should not be warehoused unnecessarily. Stablecoins for settlement should be sourced only when required, reducing idle balances and improving capital efficiency.
3.3 NAV-Based Convertibility
For cash-equivalent assets such as tokenized Treasury bills or money market fund exposures, price discovery is unnecessary. Convertibility should occur at deterministic, NAV-based pricing, subject to defined fees or adjustments.
3.4 Operational Abstraction
End users and applications should experience a simple balance that is both productive and usable. Credit intermediation, unwind coordination, and settlement mechanics should be abstracted at the protocol layer.
3.5 Institutional Compatibility
The protocol is designed for operational use cases and must support permissioned assets, credit relationships, legal segregation, and configurable risk parameters.
4. Basic Concepts
Market Wallet
A unified account structure combining:
- a transactional wallet
- a yield-bearing reserve layer
Funds held in a Market Wallet are productive by default and available for transfer through point-of-transfer liquidity provisioning.
Yield Layer
The reserve allocation layer where deposited stablecoins are routed into eligible yield-bearing instruments, such as tokenized T-Bills, money market fund exposures, or issuer-integrated yield-bearing stablecoins.
Settlement Stablecoin
The liquid stablecoin delivered to the destination wallet, merchant, exchange, or payment rail at the moment of transfer.
Liquidity Provider / Credit Facility
A broker, issuer, or delegated liquidity source that advances settlement liquidity while underlying reserve assets unwind or redeem.
Point of Transfer Execution
The protocol event in which a transfer request triggers:
- pricing and validation
- liquidity sourcing
- stablecoin delivery
- collateral unwind and repayment
5. Protocol Architecture
The protocol architecture is modular and consists of the following core components:
5.1 Account
The Account Module manages user balances, deposit records, entitlement to yield, and instructions for outgoing transfers. It represents the user-facing balance layer and coordinates interaction between reserve assets and settlement execution.
Key roles:
- accept user deposits
- maintain balance ledger
- track productive reserve allocation
- initiate transfer or withdrawal instructions
5.2 Reserve Allocation
The Reserve Allocation Module routes deposited stablecoins into approved yield-bearing instruments. It tracks allocation state, accrued yield, maturity profile, and redemption pathways.
Key roles:
- allocate deposits into tokenized T-Bills / MMFs / yield-bearing stablecoins
- maintain reserve composition
- track accrued yield
- manage unwind requests
5.3 Liquidity Execution
The Liquidity Execution Module is responsible for producing spendable stablecoin liquidity when transfers are initiated. It coordinates with approved liquidity providers, brokers, or protocol-integrated issuers to satisfy outgoing requests.
Key roles:
- quote transfer output
- source just-in-time liquidity
- route settlement stablecoins
- reconcile transfer completion against reserve unwind
5.4 Repo / Credit Coordination
This module supports the protocol's short-duration liquidity model by coordinating collateral pledging, borrowing, repayment, and collateral release.
Conceptually, this module enables a stablecoin repo loop:
- pledge yield-bearing collateral
- borrow stablecoins for a short duration
- satisfy operational transfer
- unwind collateral / repay stablecoins plus fee
- restore productive reserve position
Key roles:
- manage temporary liquidity borrow
- track facility terms and fees
- coordinate collateral claims
- settle post-unwind obligations
5.5 Pricing and NAV
This module determines conversion values between productive reserve assets and settlement stablecoins. For eligible cash-equivalent assets, pricing is based on NAV or par-value logic, optionally adjusted for fees, spread, or risk parameters.
Key roles:
- fetch NAV / price references
- apply conversion logic
- incorporate liquidity fees and execution costs
- ensure deterministic transfer output
5.6 Risk and Control
The Risk and Control Module enforces protocol-level limits and guardrails. It ensures that reserve allocation, liquidity usage, and transfer activity remain within configured parameters.
Key roles:
- per-account and per-asset limits
- approved asset and venue lists
- liquidity buffer thresholds
- pause / emergency controls
- facility exposure management
6. Protocol Flow
6.1 Deposit and Allocation
Users deposit stablecoins into the protocol. Rather than remaining idle in a wallet, these balances are routed into the reserve allocation layer and begin earning immediately.
6.2 Yield Accrual
Yield accrues continuously to the balance holder based on the underlying reserve asset. The balance remains fully visible to the user as a single usable account balance.
6.3 Transfer Initiation
When a payment, transfer, redemption, or withdrawal is requested, the protocol calculates the required settlement amount and initiates Point of Transfer Execution.
6.4 Liquidity Sourcing
The protocol either:
- sources stablecoins from an integrated liquidity provider or credit facility, or
- converts reserve assets via a NAV-based liquidity rail
6.5 Reserve Unwind and Reconciliation
Underlying yield-bearing assets are redeemed or unwound according to their settlement cycle. The proceeds are used to repay any advanced liquidity plus fees. Remaining yield accrues to the account holder or is split according to protocol rules.
7. Stablecoin Repo Loop
A core design pattern within the protocol is the short-duration stablecoin repo loop.
Flow
- The protocol pledges eligible yield-bearing collateral
- A liquidity provider advances stablecoins against that collateral
- Stablecoins are used for payments, withdrawals, or transfers
- The protocol repays the stablecoins plus a borrow fee
- The collateral is reclaimed, along with restored rights to underlying yield
This model allows productive assets to remain the base state of capital while still enabling immediate liquidity for operational flows.
The protocol therefore does not rely on:
- pre-funded stablecoin pools
- permanently idle treasury balances
- manual treasury toggling between earning and holding
Instead, it uses time-bounded liquidity transformation.
8. Why This Design Matters
Traditional wallet infrastructure assumes balances must remain idle to remain useful.
Traditional yield products assume capital must become less useful in order to earn.
Collapse rejects both assumptions.
It treats stablecoin treasury as a system where:
- capital is operational
- capital is productive
- and capital can be transformed at the exact moment it is required
This is especially important for:
- PSPs
- FX platforms
- wallets
- exchanges
- stablecoin-native businesses
- intent and execution layers
As these systems scale, pre-positioned liquidity becomes increasingly expensive. A protocol that makes balances productive until the point of transfer creates a structurally better model.
9. Risk Factors and Mitigation
9.1 Liquidity Timing Risk
Underlying reserve assets may unwind on delayed settlement cycles while users expect immediate transfers.
Mitigation:
- approved broker / credit facilities
- configurable liquidity buffers
- per-asset redemption windows
- conservative facility sizing
9.2 Pricing and NAV Risk
Incorrect pricing of reserve assets may cause transfer mismatches or under-collateralized liquidity events.
Mitigation:
- multiple data sources
- conservative NAV adjustments
- asset eligibility criteria
- execution spread controls
9.3 Counterparty and Facility Risk
Reliance on external brokers, issuers, or liquidity providers introduces counterparty risk.
Mitigation:
- approved counterparties only
- exposure limits
- legal segregation where applicable
- diversified facility sources
9.4 Operational and Routing Risk
Failures in routing, redemption coordination, or settlement reconciliation may impact protocol performance.
Mitigation:
- modular execution design
- transaction monitoring
- fallback rails
- pause and recovery controls
9.5 Regulatory and Permissioning Risk
Yield-bearing reserve assets and issuance/redemption pathways may require permissions, onboarding, or jurisdiction-specific controls.
Mitigation:
- support for permissioned integrations
- configurable asset whitelists
- modular issuer and provider adapters
- institution-first deployment model
10. Conclusion
Collapse introduces a new primitive for stablecoin-native financial infrastructure: Point of Transfer Execution.
Instead of treating yield, liquidity, and wallets as separate systems, it collapses them into a unified protocol where balances remain productive by default and liquidity is created exactly when needed.
The result is a more capital-efficient architecture for stablecoin treasury one better suited to the realities of real-time payments, FX, internet-native finance, and always-on global operations.
In the long run, stablecoins should not sit idle simply to remain usable.
They should earn until the moment they move.