Docs / Using Lethe
Delayed sends
Timing is the easiest way to link a deposit to a send. If 5 HYPE goes in and 5 HYPE comes out a minute later, nobody needs to break any cryptography to guess. Delayed sends fix that.
How it works
Pick Within 1 hour or Within 6 hours under Send time. Your browser makes the proof now and hands it to the relayer, which checks it and holds it. It then submits the send at a random moment inside the window you chose.
Good to know
- You can close the page. Once it's scheduled, the relayer does the rest.
- Checked up front. A bad proof fails when you schedule, not hours later.
- Nothing lost if it fails. If a send can't go out, for example because the pool moved on too far, it's marked failed and your balance stays where it was.
- Same fee. A delayed send costs the same as an instant one.
From code
The SDK and API accept any delay from 60 seconds to 6 hours.
const id = await lethe.send({ to: "0x…", amount: parseEther("1"), delay: 6 * 3600 });
await lethe.scheduled(id); // { status: "scheduled" }, later "sent" with a hashIndependent project, not affiliated with Elysium or Kinetiq. · X · Telegram