Signalite has four money flows that partner apps must understand. The important distinction is that the user-facing vault flow is on HyperEVM, while yield generation depends on keeper-mediated strategy operations.
Partner apps should never ask users to send assets directly to a strategy address. User deposits and claims go through the sHLP vault flow.
Deposit and batching
What changes after each step
| Step | Asset movement | User-facing state | API source |
|---|
| User deposits | USDC moves from user to vault | User receives sHLP | POST /api/v1/actions/deposit/quote |
| Vault buffers | USDC remains in vault until batching | Share price should include buffered USDC | GET /api/v1/vault |
| Keeper batches | Vault USDC moves to strategy path | Product remains liquid through sHLP | GET /api/v1/health |
| Strategy allocates | Funds become HLP exposure | NAV reflects backing through proof buckets | GET /api/v1/vault |
Instant redeem
Instant redeem uses the vault’s free USDC buffer. It does not require an HLP unwind.
Use this path when the requested exit fits the buffer and the user does not need a min-assets-out floor.
Queued redeem
Queued redeem is used when the exit is larger than the instant buffer or when the user wants a min-assets-out floor.
Cancel path
Receive-network path
The vault claim settles USDC on HyperEVM. Other receive networks are a second bridge step.
Partner implementation rule
Use the API to determine which flow applies:
| User wants | Preferred flow |
|---|
| Deposit USDC | Deposit quote, approval requirement, deposit transaction |
| Exit within available buffer | Instant redeem quote |
| Exit above buffer | Queued redeem quote |
| Pending request | Show cancel if cancelable |
| Claimable request | Show claim as primary action |
| USDC on another chain | Claim first, then bridge |
