Lightning: SeqLN
SeqLN is a fork of Core Lightning that adds the Sequentia network. One binary runs Lightning on Bitcoin, on Liquid and on Sequentia; the network is chosen with --network.
On Sequentia it adds what the chain makes possible: channels denominated in any issued asset, routing and payments that know which asset they carry, and a safety layer built on Bitcoin-anchored finality.
What it adds to Lightning
Channels in any asset. A channel is opened in one asset: a dollar stablecoin, gold, the Sequence token. Commitments, HTLCs, closes and fees are all handled in that asset.
lightning-cli fundchannel <node id> <amount> asset=<asset id>Invoices that name their asset. An invoice says which asset it is to be paid in, and the payee refuses a payment in any other.
Routing that respects assets. Gossip records each channel’s asset. A payment is routed only over channels of its asset, and a node forwards each payment in the asset it arrived in. Nothing is silently converted at par.
Quoted conversion. A node that holds channels in two assets can convert a payment between them: it signs a quote (amount in, amount out, expiry) for one payment, takes the incoming payment in one asset and forwards it in the other, and both settle or both fail. The rate is the node’s own.
Fees in any asset. On-chain fees for opening and closing channels are sized through the node’s own price list. See The open fee market.
Why Lightning on a sidechain is safe here
A Lightning node must know when a transaction is settled for good. On most chains that means waiting for several blocks.
On Sequentia a certified block is displaced only if its Bitcoin anchor is reorganised. SeqLN is built around that:
- confirmations are counted in certified blocks, and one is enough;
- timelocks are sized in clock time at the chain’s sixty-second spacing;
- a channel is announced to the network only after its funding block’s Bitcoin anchor is buried.
Go deeperDetails of the anchor-aware layer
- Sequentia block headers carry a Bitcoin anchor (height and hash); SeqLN parses them and recomputes block hashes that match the live chain byte for byte.
- On Sequentia networks the node re-walks the chain from the start on every restart, so a Bitcoin-anchor reorganisation of any depth can never leave it in an inconsistent state.
- On-chain addresses share Bitcoin’s
tb1format; invoices use a distinct prefix (lntsqt...) so they cannot be confused with Bitcoin invoices.
The precise file-level change list is in the repository’s doc/sequentia-fork.md.
Swaps over Lightning
Because the same binary runs on both chains, a node operator can run SeqLN on Sequentia and on Bitcoin side by side. That is the basis for trades that settle in seconds: an asset on Sequentia Lightning against bitcoin on Bitcoin Lightning, both legs locked to the same secret. SeqDEX offers this as one of its settlement routes. See Swaps and SeqDEX.
Fulmen
Fulmen is a desktop wallet for SeqLN, for Linux and Windows. It ships with a bundled node: install one thing, point it at a Sequentia node, and you have Lightning on Sequentia with no manual setup. It is non-custodial: the Lightning node runs on your machine and its keys never leave it.
It shows what makes SeqLN different: which asset each channel carries, balances per asset on-chain and in channels, and invoices in a chosen asset. It can also run a second node on Bitcoin testnet4 beside the Sequentia one.
Where Lightning fits
Lightning needs liquidity on both sides of a channel before it can route anything, so it suits assets that are heavily traded: bitcoin, and the main stablecoins. For everything else, on-chain transfers on Sequentia are cheap and final in seconds, and Arca offers instant payments without channels.
In the wallets’ user mode you never choose: the wallet picks the route.
Read further
- seqln README: building, and running against the testnet
- Instant bitcoin: Ark and Lightning