Skip to main content
Direct Vault managers qualify on track record, not a challenge. Here’s what’s required and how to apply.

​
The four pillars

1

Track record

6 months minimum continuous history · $50,000+ realized PnL · max drawdown under 15% trailing 6 months · Sharpe > 1.0 or comparable.
2

Identity

KYC for individuals, KYB for entities. Source-of-funds attestation required for entity applicants.
3

Strategy disclosure

What you trade, time horizon, leverage approach, and risk parameters.
4

Manager commitment

A 5% skin-in-the-game stake (of expected initial TVL), locked 3 months minimum, publicly visible on-chain.

​
Eligibility at a glance

RequirementValue
Verifiable trading history6 months minimum, continuous
Track record importRead-only API key OR cryptographically signed snapshot
Realized PnL$50,000+ over the verifiable period
Max drawdownUnder 15% trailing 6 months
Risk-adjusted metricSharpe > 1.0 or comparable
Identity checkKYC (individuals) · KYB (entities)
Geographic eligibilityUS retail, UK retail, sanctioned territories excluded

​
Application process

1

Apply online

Submit track record, strategy, and identity documents at hyro.network.
2

Admin review (1–2 weeks)

Track-record verification and strategy assessment.
3

KYC / KYB (1–2 weeks, parallel)

Processed by a qualified third-party provider.
4

Strategy interview (~1 hour)

Video call with the Head of Trading or a designated reviewer.
5

Decision

Final approval or structured feedback.
Typical total: 3–5 weeks from application to vault opening.

​
By applicant type

The framework adapts to four classes; eligibility is the same, but documentation and review depth scale with entity complexity:
TypeAdditional requirements
Individual tradersPersonal KYC, personal track record, personal stake
Funds, partnerships, RIAsKYB; entity as manager; named principals attested; fund-structure docs
Algorithmic trading desksKYB + optional code review for senior TVL tiers; algo logic disclosed at a high level
Market makersKYB + inventory-transparency commitment

​
Backtest disclosure

Backtests are optional and LP-facing only. They’re displayed alongside live performance so LPs can compare your stated framework against live results — but they’re never used for protocol enforcement. Markets change and strategies deviate from backtests; outperforming or underperforming a backtest never triggers enforcement. Decisions are based on live performance and the on-chain risk limits you set.

Next: configure your vault

Every parameter you control at creation.