Bounded carry, not generic yield
V4 Submission · Drift-Native · USDC-Denominated
Market imbalance
converted
into controlled carry
Ranger Basis Guard Vault harvests Drift-native carry while keeping exposure near delta-neutral and preserving liquidity for fast deleveraging. Designed for allocator trust — understandable, operationally realistic, verifiable.
8%
DD Stop
15%
Max Position
2.5×
Margin Buffer
3
Sleeves
Sleeve A
Drift Carry Sleeve
Hedged borrow/lend + perp funding & basis trades
55%
Sleeve B
Reserve Lending
Lower-complexity yield, stabilize portfolio
30%
Sleeve C
Idle USDC Buffer
Margin top-ups, deleveraging, withdrawal readiness
15%
Net PnL =formula
funding incomeSleeve A core
+ basis captureSleeve A edge
+ reserve yieldSleeve B income
− trading fees − borrow costs
− slippage − unwind costs
01 — SYSTEM ARCHITECTURE
Three-Sleeve Design
System Architecture
The vault uses three sleeves. Sleeve A is the Drift carry sleeve — hedged borrow/lend plus perp funding or basis trades when carry, liquidity, and margin conditions are favorable. Sleeve B is the reserve lending sleeve — lower-complexity yield positions intended to stabilize the portfolio and provide liquid capital for rebalancing. Sleeve C is the idle USDC buffer — exists specifically for margin top-ups, controlled deleveraging, and withdrawal readiness.
Sleeve A — Active Carry
Drift Carry Sleeve
Executes hedged borrow/lend plus perp funding or basis trades when carry, liquidity, and margin conditions are favorable.
Perp funding harvesting
Basis trade capture
Delta-neutral hedge
Net carry ≥ threshold
Active position monitoring
⇄
Sleeve B — Reserve
Reserve Lending Sleeve
Holds lower-complexity yield positions intended to stabilize the portfolio and provide liquid capital for rebalancing operations.
Stable yield positions
Rebalancing liquidity
Portfolio stabilizer
Lower complexity
Receives from Sleeve A exits
⇄
Sleeve C — Buffer
Idle USDC Buffer
Exists specifically for margin top-ups, controlled deleveraging, and withdrawal readiness. First source for redemptions.
Margin top-up reserve
Withdrawal priority #1
Emergency deleverage fund
Policy floor maintained
Always liquid USDC
Capital Flow
USDC
Deposit
Deposit
Depositor
→
Vault
Treasury
Treasury
Central pool
→
Allocation
Controller
Controller
Policy engine
→
Drift
Adapter
Adapter
Execution
→
Hedged
Position
Position
Sleeve A
→
Real-Time
Monitor
Monitor
Continuous
→
Reduce/
Exit/Hold
Exit/Hold
Decision
Withdrawal priority: Sleeve C first, then Sleeve B, then controlled unwind of Sleeve A. Reallocations are event-driven. Avoid churn.
02 — EXECUTION MECHANICS
State Machine
Execution State Machine
The strategy is not "always on." Its edge exists only when economics and safety are both present. The default action under uncertainty is to do less, not more.
IDLE
No active risk
signal detected
CANDIDATE
Scoring
all gates pass
ADMITTED
Approved
position opens
ACTIVE
Live & monitored
deterioration
REDUCE
Size down
exit trigger
EXIT
Close position
capital parked
SAFE STATE
USDC + reserve
IDLE
No active carry trade. The system monitors signals continuously. Capital is parked in USDC and reserve sleeves. This is the default condition — the baseline, not a failure mode.
Signal Logic — Admission Gates
A trade qualifies only if all four gates pass. Any single rejection blocks entry.
GATE 1
Net Carry Threshold
expected_net_carry > entry_threshold
Expected annualized net carry must exceed the entry threshold after fees and slippage. Gross carry is insufficient — execution costs must be accounted for before admission.
if ≤ threshold: reject entry
GATE 2
Liquidity Sufficiency
liquidity_score ≥ min_liquidity
Market depth must be sufficient for both entry and exit. A trade that can be entered but not exited cleanly is not a trade — it is a trap. Liquidity is measured for both legs independently.
if insufficient depth: reject entry
GATE 3
Margin Buffer Policy
projected_margin_buffer ≥ min_margin_buffer
Post-trade margin must remain above policy. The internal margin buffer target is at least 2.5× liquidation distance on admitted carry trades. This is a hard floor, not a soft guideline.
if margin insufficient: reject entry
GATE 4
Stress Test Clearance
stressed_drawdown ≤ max_drawdown_budget
A stress test must show expected drawdown within the portfolio risk budget. The scenario tests for volatility spike, funding collapse, and liquidity deterioration simultaneously before any capital is deployed.
if stressed DD exceeds budget: reject entry
Execution Pseudo-Code
// Entry evaluation
if expected_net_carry <= entry_threshold: reject
if liquidity_score < min_liquidity: reject
if projected_margin_buffer < min_margin_buffer: reject
if stressed_drawdown > max_drawdown_budget: reject
open_hedged_position()
// Live monitoring loop
while position_active:
update_funding() | update_basis() | update_margin() | update_liquidity()
if oracle_failure or margin_policy_breach:
trigger_kill_switch()
break
if net_carry < exit_threshold or liquidity_score < continuation_min:
close_position()
break
if volatility_above_throttle:
reduce_position()
The strategy is not "always on." Its edge exists only when economics and safety are both present. The default action under uncertainty is to do less, not more.
03 — RISK FRAMEWORK
Capital Preservation First
Risk Framework
The system is designed to minimize permanent impairment and avoid disqualification-style blowups. Capital preservation dominates yield maximization.
8%
Portfolio Drawdown Stop
Hard floor. Triggers full position review and potential safe-state migration.
15%
Max Single-Position Gross Exposure
% of portfolio capital. No single trade can exceed this regardless of signal strength.
40%
Maximum Venue Concentration
No single venue, protocol, or counterparty may hold more than 40% of total exposure.
2.5×
Target Internal Margin Buffer
Minimum 2.5× liquidation distance on all admitted carry trades. Hard policy floor.
Primary Controls
Position Caps
Hard size limits per instrument and per strategy type. Cannot be overridden.
Venue Caps
Concentration limits per protocol. Prevents single-venue failure from impacting full portfolio.
Volatility Throttle
When vol spikes beyond policy: scale down Sleeve A, raise carry thresholds for new entries, increase idle buffer target.
Liquidity Filter
New trades blocked when exit capacity falls below policy. Existing trades reduced gradually when book depth deteriorates.
Correlation Check
Position correlation analysis prevents concentration risk across seemingly independent trades.
Internal Margin Floor
Real-time margin distance monitoring. Reduction triggered before policy breach, not after.
Event-Driven Rebalancing
Reallocations triggered by conditions, not schedule. Avoids routine churn that increases execution costs.
Kill Switch
Oracle inconsistency, margin policy breach, or operator trigger forces immediate safe-state migration.
Trust Boundary — When the Strategy Stops Working
The strategy can fail economically if carry remains absent for extended periods or if liquidity becomes persistently inadequate. In those conditions, the correct behavior is not to reach for yield — it is to preserve capital and wait. A strategy deserves capital only if it tells the truth about how it can stop working.
Failure Modes and Stress Scenarios
Four scenarios. Each has an explicit system response. The design goal is graceful degradation rather than forced heroics.
Scenario 1
Volatility Spike
Vol spikes beyond policy
→
Scale down Sleeve A
→
Raise carry thresholds
→
Hedge intact · DD controlled
Hedge remains intact. Exposure is cut. Drawdown stays controlled. New entries are blocked until vol returns within policy. The hedge does not unwind — it is maintained throughout.
Outcome: hedge intact; exposure cut; drawdown controlled
Scenario 2
Funding Collapse
Carry below exit threshold
→
Continuation threshold fails
→
Position closed early
→
Opportunity abandoned
The edge no longer compensates for execution and liquidation risk. The system exits because the continuation threshold fails — not because of a loss event. Abandoning the trade cleanly is the correct outcome.
Outcome: continuation threshold fails; position closed early; opportunity abandoned
Scenario 3
Liquidity Shock
Book depth falls below policy
→
Block new entries
→
Gradual staged reductions
→
Avoid forced exits
New entries are blocked immediately. Active positions are reduced gradually to avoid forcing exits into thin markets. Avoiding forced exits into illiquid order books is the primary objective — gradual beats immediate.
Outcome: new entries blocked; active positions reduced gradually
Scenario 4
Oracle Inconsistency
Oracle integrity check fails
→
Kill switch triggers
→
Freeze new risk
→
Capital → safe state
Oracle inconsistency triggers the kill switch immediately. No position sizing or carry decisions can be made on unreliable price data. Capital returns to safe state — Sleeve C USDC and reserve lending — until oracle integrity is restored.
Outcome: kill switch triggers; capital returns to safe state
04 — PNL FORMULA
Performance Measurement
PnL Formula
Net performance equals realized funding income plus basis realization plus reserve-sleeve yield minus fees, slippage, and other execution costs.
funding income
+
basis capture
+
reserve yield
− trading fees − borrow costs − slippage − unwind costs
= Net PnL
− trading fees − borrow costs − slippage − unwind costs
= Net PnL
Funding Income
Perp funding rate payments collected from the short leg when positive carry persists. Primary edge of Sleeve A.
Basis Capture
Convergence of futures premium to spot. Locked at trade entry. Annualized yield = (F−S)/S × 365/DTE.
Reserve Yield
Sleeve B lower-complexity lending income. Stabilizes total return during low-carry periods.
Execution Costs
Trading fees + borrow costs + slippage on entry/exit + unwind costs. Must be modeled before admission.
05 — PROOF & VERIFICATION
Independently Checkable
Proof & Verification
Every material claim should be independently checkable. Here is the verification path: the repository, the proof methodology, the wallet schema, the position lifecycle, and the PnL formula. Every material claim is traceable to code, policy, or onchain evidence.
Judge Verification Path — 5 Steps
1
Inspect Vault Address & Manager Wallet
Confirm vault address and manager wallet are published. All subsequent evidence links to these addresses. Nothing operates off-schema.
2
Review Position Lifecycle Log
Entry, reductions, and exits for each position. Trade ID, asset, entry time, entry reason, entry transaction, reductions array, exit transaction, and notes.
3
Match Actions to Onchain Transactions
Every material action — entry, reduction, exit — has a corresponding transaction hash. Cross-reference lifecycle log against onchain explorer.
4
Recompute PnL Using Published Formula
Apply the published formula (funding income + basis capture + reserve yield − fees − borrow − slippage − unwind) to disclosed position data. Reconcile against reported performance.
5
Check Exposures Against Sizing Rules
Verify reported exposures obey the published sizing and concentration rules: 15% max position, 40% max venue, 2.5× margin buffer maintained throughout each position lifecycle.
Proof Schema (JSON Template)
// Proof_Schema.json — replace placeholders with live data
{
"vault_address": "[replace_with_real_vault_address]",
"manager_wallet": "[replace_with_real_manager_wallet]",
"positions": [{
"trade_id": "example-trade-001",
"asset": "SOL-PERP",
"entry_time": "YYYY-MM-DDTHH:MM:SSZ",
"entry_reason": "annualized net carry above threshold",
"entry_tx": "[replace_with_tx_hash]",
"reductions": [],
"exit_tx": "[replace_with_tx_hash]",
"notes": "replace with real onchain details"
}],
"pnl_formula": "funding income + basis capture + reserve yield - trading fees - borrow costs - slippage - unwind costs"
}
This package provides a complete verification method and proof schema, but not fabricated live performance. Any real submission should replace example placeholders with actual addresses, transactions, and screenshots generated during the hackathon window.
06 — FAILURE ANALYSIS
Failure Boundary
When the Strategy Stops Working
The strategy can fail as an income strategy if positive carry disappears for long periods, if liquidity stays weak enough to make orderly hedging uneconomic, or if venue or oracle integrity degrades. Those states do not justify stretching for yield.
Failure Mode 1
Extended Carry Absence
Response: reserve-oriented posture + wait
Positive carry disappears for extended periods. The vault contracts toward reserve-oriented posture, maintains withdrawability, and waits for economics to improve. No yield-stretching in adverse regimes.
Failure Mode 2
Persistent Liquidity Inadequacy
Response: block entries + gradual reduction
Liquidity stays weak enough to make orderly hedging uneconomic. New trades are blocked. Active positions are reduced gradually. Forced exits are avoided at all cost — an orderly small loss beats a catastrophic fast one.
Failure Mode 3
Venue or Oracle Integrity Degradation
Response: kill switch + safe state immediately
Oracle inconsistency or venue integrity questions trigger immediate kill switch. Capital moves to safe state. Operations do not resume until integrity is independently confirmed and restored.
Failure Mode 4
Structural Regime Change
Response: reserve posture + materially lower risk
Long period of flat or negative funding — structural regime change, not cyclical. Correct response is to push vault into reserve-oriented posture with materially lower risk. Capital preservation is the objective in this regime.
Recovery Model
In adverse regimes, the system should contract toward reserve-oriented posture, maintain withdrawability, and wait for the economics to improve. The design goal is graceful degradation rather than forced heroics. The vault does not attempt to recover losses through elevated risk-taking.
"A strategy deserves capital only if it tells the truth about how it can stop working."
— Failure Analysis · Ranger Basis Guard Vault V4
07 — ALLOCATOR PITCH
Why Capital Should Be Allocated
Seeding Case
The strategy is understandable, bounded, and verifiable. It is designed to be run, monitored, and unwound by an actual operator.
1
Understandable
Three sleeves. Clear capital flow. State machine execution. An allocator can read this package and understand where their capital is, how it is positioned, and how it will be handled under adverse conditions.
2
Bounded
Hard limits on position size, venue concentration, and drawdown. 2.5× margin buffer policy. Kill switch. The risk surface is explicitly defined and enforced — not advisory.
3
Verifiable
Five-step judge verification path. Published proof schema. Every material claim is traceable to code, policy, or onchain evidence. Nothing lives only in the narrative.
4
Scalable Architecture
The reserve sleeve and buffer sleeve improve capacity management because they reduce the need for all capital to remain in the highest-complexity trade at all times. Capacity still depends on venue liquidity and borrow availability, but the structure is more scalable than an all-in carry loop.
5
Risk-Adjusted Objective
The objective is not to maximize raw return. It is to capture acceptable carry while avoiding ruinous tail outcomes. This is a system for allocators who have experienced what yield-maximization-without-risk-discipline actually produces.
6
Operational Readiness
The package includes a runbook, a monitoring model, a proof model, and a code skeleton. That pushes the submission closer to an investable system than a hackathon-only concept.
Operational Readiness Classification
The package includes a runbook, a monitoring model, a proof model, and a code skeleton — closer to an investable system than a hackathon-only concept.
ENDERS V4 Audit Summary
V4 — Gaps Patched
The submission is highly competitive because it is clear, risk-first, and easy to verify. V4 patches the identified gaps:
✓Edge Persistence: Durability model for carry added — explains how and when the edge holds across regimes.
✓Mechanical Execution Depth: State machine view of execution — IDLE through SAFE_STATE with explicit transition conditions.
✓Explicit Failure Boundaries: Four failure modes with specific responses. The trust boundary is named and honest.
✓Memory Hook: Bounded carry, not generic yield — consistent framing throughout all materials.
Assumptions & Compliance
Aligned to USDC base asset by design. Any fixed APY floor, strict mandatory USDC-only rule, or mandatory rolling three-month tenor should be treated as assumptions unless confirmed directly by organizers. Policy thresholds in this package are illustrative build parameters for the submission narrative. Production deployment would require venue-specific testing, simulation, and review.
08 — DEMO SCRIPT
3-Minute Demo
Demo Script — V4
Full timestamped presentation script. Every line is designed to communicate: value in 5 seconds, proof in 10, trust throughout.
0:00 – 0:20
The problem with generic yield products. Most yield products optimize for headline APY, not survivability. That creates hidden risk and makes them difficult to trust with real capital.
0:20 – 0:45
Introduce Ranger Basis Guard Vault. Ranger Basis Guard Vault is a USDC-denominated managed vault designed to convert market imbalance into controlled carry. It harvests Drift-native carry while keeping exposure near delta-neutral and preserving liquidity for fast deleveraging.
0:45 – 1:15
Three-sleeve architecture. The vault uses three sleeves: a Drift carry sleeve, a reserve lending sleeve, and an idle USDC buffer. This architecture lets the strategy generate yield while keeping capital available for margin support, orderly rebalancing, and withdrawals.
1:15 – 1:45
Lead with risk — the differentiator. We lead with risk. Positions are capped, concentrations are capped, margin must remain comfortably above liquidation policy, and a kill switch forces the system into a safe state if oracle integrity, liquidity, or liquidation risk breaks policy.
1:45 – 2:20
Show the verification path. Here is the verification path: the repository, the proof methodology, the wallet schema, the position lifecycle, and the PnL formula. Every material claim is traceable to code, policy, or onchain evidence.
2:20 – 3:00
Close on the memory hook. This is not a generic yield router. It is a bounded-carry system built for allocator trust. It is understandable, operationally realistic, and designed for real capital deployment. Ranger Basis Guard Vault: bounded carry, not generic yield.
09 — PRODUCTION RUNBOOK
Daily Operating Model
Production Runbook
Daily Operations
Review funding, basis, liquidity, concentration, and margin at defined intervals
Confirm active positions still clear continuation thresholds
Verify idle USDC buffer remains above policy floor
Review monitoring alerts and escalation queue
Rebalance Process
Reallocations are event-driven — not scheduled
When carry decays or reserve needs rise: reduce Sleeve A, restore B or C
When conditions improve and all admission gates pass: redeploy carefully into Sleeve A
Avoid churn — execution costs accumulate on unnecessary activity
Manager Responsibilities
Enforce policy — no exceptions without documented rationale
Approve parameter updates through governance process
Review monitoring alerts and sign off on major rebalances
Maintain audit logs of all material decisions
Ensure proofs and disclosures remain accurate
Live Trade Walkthrough
Positive annualized funding spread appears on SOL-PERP
Engine allocates up to 10% of portfolio capital to opportunity
Constructs hedged position with spot or borrow offset by perp short
Targets net delta near zero — admitted only if margin buffer + stressed DD pass
Monitors funding decay, liquidity, volatility, and margin continuously
If funding falls below continuation threshold: unwind, capital returns to buffer/reserve
⚠ Emergency Procedures
If oracle checks fail, if margin buffer approaches policy breach, or if liquidity deteriorates rapidly:
1.Freeze new risk — no new position entries under any circumstances
2.Reduce active positions according to priority: liquidation risk first, then concentration, then size
3.Move capital to buffer and reserve sleeves — Sleeve C first priority
4.Preserve withdrawability — depositor exit must remain available throughout
10 — LIVE CALCULATOR
Sleeve A — Live Rebalancer
Delta-Neutral Position Calculator
Live delta exposure, hedge ratio, funding yield, and rebalancing triggers for Sleeve A positions. All calculations execute in real time.
Position Parameters
NET DELTA EXPOSURE (Δ$/NAV)
0.0%
Dollar Delta Ratio
−15%−5%0+5%+15%
●
Position within threshold — no action required
Dollar Delta
$0
Net directional exposure
Hedge Ratio
0.000
Target: 1.000
Funding APR
0.00%
Annualized 8h × 1095
Rebal Required
0.00
Perp units to adjust
Spot Notional
$0
Long spot value
8h Funding PnL
$0
Per settlement period
Rebalancing Event Log
--:--:--Rebalancer initialized — Sleeve A position tracking active
11 — AI ARCHITECTURE GENERATOR
Vault System Builder
Generate Vault Architecture
Configure parameters and generate a complete vault system specification using the Ranger Basis Guard framework.
Vault Parameters
// Vault architecture will generate here...
// Configure parameters and click Build Architecture