Trigger orders
Limit, take-profit and stop-loss orders held by the ElyhypeTriggerBook contract on v3-style pools. Anyone can execute an order once its price condition holds; the minimum you set is enforced on chain; you can cancel at any time. The contract holds your deposit until the order fills, you cancel it, or it expires. It is new and has had no independent security review. Start with small amounts.
Your orders
Connect to see your orders.
Newest orders in the book
Reading…
Contract 0xca39…ce29. Read from its views every 20 seconds while this tab is open.
How an order works
- Place: you deposit the token you sell (or native HYPE where the pool holds WHYPE) and set the trigger price, the minimum you accept, an expiry, an optional time-weighted window and an optional HYPE tip. The pool must be one that its own factory confirms (Uniswap v3, Ramses v3 or CL factories on Elysium).
- Wait: the deposit stays in the contract. Nobody can move it except by the order's rules: no owner, no admin, no fee, no upgrade.
- Execute: once the pool's current tick (and, if you asked, its average over the window) is on your side of the trigger, anyone may call execute. The swap reverts unless the whole deposit is sold and at least your minimum arrives; the output goes straight to you, the tip to the executor.
- Cancel or expire: you can cancel at any time and get the deposit and tip back. After expiry anyone can close the order; the funds go to you.
What it does not protect against
- A spot price can be pushed for one transaction by anyone with capital. Your minimum is the real protection; the time-weighted window makes a one-block push useless.
- A stop-loss fills at the price when someone executes, never below your minimum. If the price falls through your minimum, the order waits (it cannot fill) until you act.
- Nobody is obliged to execute. Today anyone can run the open keeper script; a hosted keeper network is planned.
- The contract is new and has had no independent security review. Use small amounts.
Run a keeper
examples/keeper.mjs in the source reads open orders, checks each with the contract's own triggerState view, simulates execute and only then sends it, with your own key on your own machine. It earns the tips orders carry.