┌──────────┐ │ DEPOSIT │ └────┬─────┘
LOCK ANY EVM ASSET
Native currency and standard ERC‑20 support, with exact wallet approvals visible before execution.
[ VAULT 0 ] LOCATING ACCESS CHANNEL... VERIFYING CLIENT INTEGRITY... MOUNTING RESTRICTED INTERFACE...
██╗ ██╗ █████╗ ██╗ ██╗██╗ ████████╗ ██████╗ ██║ ██║██╔══██╗██║ ██║██║ ╚══██╔══╝ ██╔═████╗ ██║ ██║███████║██║ ██║██║ ██║ ██║██╔██║ ╚██╗ ██╔╝██╔══██║██║ ██║██║ ██║ ████╔╝██║ ╚████╔╝ ██║ ██║╚██████╔╝███████╗██║ ╚██████╔╝
Deploy a transparent vault protocol, lock native assets or ERC‑20 tokens, define up to five recipients and release funds automatically under immutable onchain rules.
Vault 0 does not manufacture returns. It enforces time, ownership and distribution logic without giving the operator a hidden withdrawal path.
┌──────────┐ │ DEPOSIT │ └────┬─────┘
Native currency and standard ERC‑20 support, with exact wallet approvals visible before execution.
00:00:00 │ ▼
Unlock timestamps are written onchain and cannot be shortened by the protocol owner.
100% ├─ 50% ├─ 30% └─ 20%
Split released assets among one to five addresses with shares that must total exactly 100%.
ADMIN ╳ FUNDS
The owner can update a capped protocol fee, but cannot seize or prematurely release user vaults.
Every transaction follows a visible and verifiable route.
The connected wallet deposits assets directly into the deployed contract. Vault 0 never requests a private key.
Vault 0 locks fungible LP tokens and ERC-721 concentrated-liquidity positions without taking custody keys or inventing yield.
ERC-20 LP locks require approval + lock. ERC-721 positions require one NFT approval to the locker, then the lock transaction.
Deploy a permission-addressed Vault 0 hook through CREATE2. The hook observes every swap and binds the pool to a fixed 2.00% fee policy. Pool initialization stays gated until the opening price is reviewed.
The browser never receives a private key. Address mining is performed locally; deployment transactions are signed only inside your wallet.
Connect the deployed hook profile to calculate a guarded opening price.
Initialization creates the pool but does not deposit funds or approve tokens. The reference price is fetched immediately before signature and expires after 90 seconds.
The connected user supplies both assets. Vault 0 never advances capital. The wizard requests only the approvals required by Permit2 and the official Uniswap v4 PositionManager.
[vault0] public liquidity gateway standby...
[vault0] waiting for wallet handshake...
This release deploys a real Uniswap v4 beforeSwap/afterSwap telemetry hook with valid address flags. The 80/15/5 split is stored as protocol policy; automatic fee extraction is intentionally not enabled before an independent audit.
Created vaults and vaults where your wallet is a recipient.
Inspect any Vault 0 channel directly from its numeric onchain ID.
Deploy the factory, load an existing address or update capped fee settings from the owner wallet.
Compilation occurs inside the included Vercel serverless function. The resulting deployment is signed by the connected wallet, never by the website.
✓ Hold native and ERC‑20 assets
✓ Enforce future unlock timestamps
✓ Route funds to declared recipients
✓ Apply a publicly readable capped fee
× Early owner withdrawals
× Hidden recipient replacement
× Arbitrary admin fund recovery
× Guaranteed or fabricated yield
Production use with significant funds still requires an independent smart-contract audit. “Functional” does not mean “risk-free.”