If you go silent, risk still responds.
Metrada monitors a trader’s activity deadline. If the user is absent, it safely reduces leverage or opens a preset hedge without granting the automation permission to withdraw funds or change markets.
The pulse
slows down.
Keep scrolling and the heartbeat fades. Each shape dims and drifts as the trader's deadline approaches. No check-in means no one is watching the position — but Metrada never sleeps.
The safety net deploys.
The shapes reassemble — a parachute forms from emergency orders. Each hedge preset, each leverage reduction verified. Move your cursor through it and watch the safety net flex.
Safe landing,
risk managed.
The shapes float downward like a parachute landing — positions hedged, leverage reduced, but no unauthorized withdrawals made. If you go silent, risk still responds.
Frequently Asked Questions
Everything you need to know about the non-custodial architecture, inactivity thresholds, hedge mechanisms, and cryptographic proofs.
Mathematically and architecturally impossible. Metrada operates via scoped session keys restricted exclusively to verified perpetual trading functions: openHedgePosition() and reduceLeverage(). The on-chain smart contract invariant guarantees that any transaction attempting to invoke transfer(), withdraw(), or change vault ownership reverts instantly. Your underlying funds remain under your sovereign control at all times.
Metrada listens for cryptographic heartbeat check-ins generated by your trading interactions (browser session, terminal commands, or SDK daemon). If no check-in is received within your chosen deadline window (e.g., 6h, 12h, 24h, or 48h), the dead-man switch activates. The pulse field slows down to signal inactivity, and sentinel nodes prepare emergency rescue routing.
You retain 100% control of your positions. Because the automated response is non-custodial, you can choose to keep the delta-neutral hedge open, unwind it with a single signed transaction, or rebalance your leverage without any lockup periods, unlock fees, or custodial approvals.
Hedge orders are dispatched through private RPC relays (Flashbots Protect on Ethereum/Arbitrum and Jito on Solana) rather than public mempools. Large positions utilize a dynamic Time-Weighted Average Price (TWAP) execution schedule with a strict 0.25% hard slippage limit, guaranteeing that bots cannot front-run or sandwich your emergency hedge.
Metrada supports EVM perpetual ecosystems on Arbitrum One, Base, and Optimism (integrating with GMX v2, Hyperliquid, Synthetix v3, and Vertex), as well as Solana SVM perpetual platforms (including Drift Protocol, Jupiter Perps, and Zeta Markets).
Zero subscription fees. Arming the dead-man switch and keeping it active requires only standard blockchain network gas to record the initialization. If you remain active, you pay nothing. A modest 0.05% keeper bounty is only compensated to decentralized relayer keepers if an emergency rescue execution is successfully executed on-chain.
We recommend selecting a comfortable inactivity threshold (e.g., 24h or 48h) to accommodate normal sleep and short trips. Additionally, Metrada supports secondary notification relays: when 75% of your deadline has elapsed, optional alerts (via Telegram bot or SMS) ping you so you can check in with one tap before any hedge action triggers.
Yes. The core contracts and session key delegation modules have been audited by Trail of Bits and OpenZeppelin with zero critical vulnerabilities found. The invariant testing suite mathematically asserts that no permission path can result in fund extraction or unauthorized liquidation. Audit reports and formal proofs are available in our technical documentation.
Metrada employs an on-chain DAO governance framework utilizing token-weighted voting and quadratic conviction voting for core parameter tuning—such as whitelisting new perpetual DEX routers, setting default de-risking stepdown rates, and adjusting keeper execution bounties. Proposals undergo a mandatory 5-day community Request For Comments (RFC) period, followed by a 72-hour on-chain voting window and an enforced 48-hour timelock before execution. A decentralized 7-of-11 Security Council can enact emergency circuit breakers solely to pause integrations during critical upstream DEX vulnerabilities.
To protect the protocol from malicious flash-loan takeovers and Sybil attacks, submitting an on-chain governance proposal requires holding or being delegated a minimum threshold of 0.5% of total voting supply with a 7-day pre-voting lockup. For a vote to be legally ratified by the protocol, a minimum quorum of 4% of circulating voting power must participate, and proposals modifying critical safety constants require a supermajority of > 66.7% affirmative votes. Historical block-height snapshotting guarantees that temporary flash-borrowed voting power is rejected.
Have more technical questions?
Explore full smart contract architecture, SDK code samples, and verification proofs.