A Lightning channel opens with an on-chain funding transaction whose channel output, in BOLT 3, pays to a 2-of-2 multisignature script built from the two peers' funding public keys, ordered lexicographically, so it can only be spent with both peers' signatures.
Sources and checks
T1BOLT 3, Bitcoin Transaction and Script FormatsBOLT, says this directly
2 <pubkey1> <pubkey2> 2 OP_CHECKMULTISIG
Transactions, Funding Transaction Output, read 2026-11-20
T1BOLT 3, Bitcoin Transaction and Script FormatsBOLT, says this directly
is the lexicographically lesser of the two `funding_pubkey` in compressed format
Transactions, Funding Transaction Output, read 2026-11-20
T1BOLT 2, Peer Protocol for Channel ManagementBOLT, background
This is the first step toward creating the funding transaction and both versions of the commitment transaction.
Channel Establishment v1, the open_channel Message, read 2026-11-20
lightning/bolts at 191462825a contains this text in 03-transactions.md, and still does on the default branch.
Run it yourself
git clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:03-transactions.md | grep -nF '2 <pubkey1> <pubkey2> 2 OP_CHECKMULTISIG'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3, code 1/1
History
Nothing is edited silently; every revision keeps what it replaced.
- 20 Nov 2026, 17:27 UTCblock 976,759
Published Revision 1, run 2026-11-20-seed-lightning