Lightning Network Routing

Coming soon. This feature is built and on the AERE roadmap, its on-chain contracts are not yet deployed. Actions are disabled until launch.

Send AERE through a router using a shared hashlock. The router opens a paired HTLC to the recipient with a shorter timeout. Recipient reveals the preimage to claim; the router uses the same preimage to pull from your HTLC. Atomic, if the recipient never claims, both HTLCs refund.

Active router

Address,
Fee,
Max forward (per route),
Liquidity,
Active routes,
I want to SEND
I want to RECEIVE

Send routed payment

Step 1 · Get the recipient's hashlock

Ask the recipient to switch to "I want to RECEIVE" above and send you their hashlock. They keep the preimage private.

Step 2 · Open in-HTLC to router

,

Step 3 · Ask router to forward

,

Step 4 · Tell the recipient the out-HTLC id

Send them the out-HTLC id from step 3. They'll claim it with their preimage. The router automatically pulls your in-HTLC after they claim.

,

Receive routed payment

Step 1 · Generate a fresh preimage

Keep the preimage private. Send only the hashlock to the sender.

,

Step 2 · Send the hashlock to the sender

Copy the hashlock above and send it to whoever's paying you (any messenger). They give it to the router along with your address.

Step 3 · Wait for the sender to share the out-HTLC id, then claim

,

How the routing works

  Sender                     Router                     Recipient
    │   open in-HTLC, lock X     │                            │
    │   hashlock=H, timeout=T+δ  │                            │
    ├──────────────────────────▶ │                            │
    │                            │   open out-HTLC, lock X-fee│
    │                            │   hashlock=H, timeout=T    │
    │                            ├──────────────────────────▶ │
    │                            │       reveal preimage,     │
    │                            │       claim X-fee          │
    │                            │ ◀──────────────────────────┤
    │   router uses preimage     │                            │
    │   to claim X from in-HTLC  │                            │
    │ ◀──────────────────────────┤                            │
    

If the recipient never claims, both HTLCs eventually refund. The router's outgoing timeout is shorter than the incoming, guaranteeing the router can always pull the in-HTLC after the recipient claims out, even if the recipient stalls until the very last second.