Paperclip
Paperclip Lightning

BITCOIN LIGHTNING · XBT

Your node.
More possibilities.

Connect to Paperclip. Add incoming capacity.
Keep control of your funds.

Compatible XBT builds of Core Lightning and LND.

MAKE THE CONNECTION

Add Paperclip as a peer.

In your node’s peer manager, choose Add peer and paste this address.

Clearnet · port 9735
02bfcaa8328a89aa03ef55b3b810dc0dc43ee6df1e8d4cc8badb219ba303063389@lightning.paperclip-xbt.xyz:9735

Connecting is free. It doesn’t open a channel or move funds.

Prefer Tor?

Configure a Tor SOCKS proxy on your node, then use this address for the same Paperclip node.

02bfcaa8328a89aa03ef55b3b810dc0dc43ee6df1e8d4cc8badb219ba303063389@zsrixvdofis6b5ti6qtoexltczqnmfxhymfi4ykrotverzskd7ch54ad.onion:9735
RECEIVE MORE

Incoming capacity

Choose a channel. We provide the liquidity.

EXPLORE

The network

See public nodes and the channels connecting them.

CHECK IN

Node status

Check Paperclip’s latest published status.

WHEN YOU NEED THE DETAILS

A little setup goes a long way.

Which node software can I use?

Use a compatible XBT build of privkeyio Core Lightning or Paul Lamb’s LND. Standard SHA-256 Bitcoin Lightning nodes cannot connect to this network.

Both implementations must support the same chain and required features. A successful peer connection alone does not verify chain compatibility.

Ordering a Large channel? Enable wumbo.

Large provides 25,000,000 sats (0.25 XBT). Channels above 16,777,215 sats require large-channel support on both nodes, whether public or private.

LND

Enable large channels in your node app, or add this to your LND configuration:

protocol.wumbo-channels=true

Restart LND, then reconnect to Paperclip. If you have a separate channel-size limit, allow at least 25,000,000 sats.

Core Lightning

Modern CLN enables large channels by default. For customized builds, check your build’s configuration and negotiated capabilities.

Already paid? Keep your order reference and contact Paperclip. Do not pay again.

Protocol compatibility & funding

Peers must understand mandatory feature bit 512 (option_blake2b). Bit 515 advertises unified signatures; new channels use channel-type bit 514.

Unified signatures use SIGHASH_ALL | SIGHASH_UNIFIED (0x21) for replay protection. That protection applies to the transaction signed with it. Funding transactions signed without unified sighash need separate replay protection.

Verify chain compatibility and replay protection before funding a channel. Channel funding is a separate action from connecting a peer.

Trouble connecting?

For clearnet, check DNS for lightning.paperclip-xbt.xyz and outbound TCP port 9735. For Tor, confirm your Tor service and SOCKS proxy are ready.

Use the full address and check your node’s logs. An unsupported-feature error needs compatible node software; changing firewall settings won’t fix it.