Per-bot smart contract
Each launched bot receives a dedicated BotVault V4 contract on HyperEVM instead of sharing one pooled vault.
Features / Bot Vaults
Controlled Test PhaseBot Vaults with per-bot onchain context.
BotVault V4 assigns each launched bot its own smart-contract context on HyperEVM. Capital, ownership, permissions and recovery remain attributable while controlled actions can reach HyperCore.
AI assists. You decide.Capabilities
Every vault has a defined identity.
Beneficiary & controller
The return destination and the authority allowed to manage the lifecycle remain separate and explicit.
Execution identity
A bound agent wallet connects the intended bot workflow to permissioned HyperCore actions.
Locked context
Bot ID, template, fee policy, beneficiary and lifecycle state remain attributable to the vault.
How it works
HyperEVM ownership. HyperCore execution.
The lifecycle treats every capital movement as a named operation that must be observed and reconciled across the contract and trading state.
Create on HyperEVM
Deploy a dedicated contract with the bot, beneficiary, controller and agent identity bound together.
Fund the vault
Move USDC into that specific contract and wait for onchain funding evidence.
Prepare HyperCore
Transfer the intended amount, establish Perps margin and reserve requirements, then verify execution readiness.
Operate and reconcile
Track orders, positions, pause, close-only, settlement and recovery against observed state.
Safeguards
Ambiguous is not success.
Pending, retryable, recovery-required and user-action-required states stay visible throughout the lifecycle.
No hidden pooling
Multiple bot flows are not presented as one undifferentiated capital balance.
Confirmation
Observed HyperEVM and HyperCore state must be reconciled before completion.
Bounded recovery
Failed or unclear transitions require a defined retry, recovery or user action.
Availability
Testing does not mean broadly released.
Controlled BotVault V4 capital canaries are active, but Bot Vaults remain Later in pricing and are not sold as a current plan entitlement.
Small monitored scope
Testing stays limited to selected users and deliberately small capital canaries.
Recovery evidence
Funding, settlement, return and incident procedures must remain observable and repeatable.
Release boundary
Broader access waits for monitoring, contract readiness and longer-run operating evidence.
Evaluation guide
Follow capital across both environments.
Bot Vault evaluation must keep contract ownership, transferred amounts, execution state and the return path attributable to one bot lifecycle.
Contract identity
Confirm the dedicated HyperEVM contract, bot identity, beneficiary, controller and bound execution identity before funding is considered ready.
Funding evidence
Match the intended USDC amount with observed contract and transfer state rather than assuming a submitted transaction completed the lifecycle.
Execution readiness
Verify the separately prepared HyperCore context, margin and operating limits before any controlled action is treated as available.
Settlement and recovery
Track close-only, settlement, return and user-action-required states until contract and trading observations reconcile.
Connected workflow