BITCOIN BLAKE2B

Connect with
Paperclip.

Add Paperclip as a Lightning peer. Start with a connection, then manage channels from your own node.

EXPERIMENTAL SOFTWARE · RISK OF LOSS

Only use funds you’re willing to lose.

Paperclip’s Blake2b Lightning software is currently experimental. Bugs, incompatibilities or other failures could cause a permanent loss of funds.

For testing, only deposit or commit to channels amounts you are willing to lose entirely. Do not use this service to store savings or funds you depend on.

Required software & feature bits

Paperclip runs privkeyio Core Lightning v26.06.8-blake2b.5. Connect using a compatible XBT build of either implementation below. Both must support the required handshake and unified-signature rules.

The requirements below apply to both implementations; the CLN version number is not an LND version requirement.

Bit 512 — option_blake2b: mandatory in the init handshake and advertised in our node announcement. Peers must understand mandatory bit 512. Older Blake2b releases and SHA256 nodes do not support the required protocol. Advertising a feature does not independently verify a peer's chain.
Bit 515 — option_unified_sigs: advertises unified-signature capability in init. New channels require the corresponding mandatory channel-type bit 514.
SIGHASH_UNIFIED: new unified channels use the replay-protected signature digest, with SIGHASH_ALL | SIGHASH_UNIFIED encoded as 0x21.

The feature pairs 512/513 and 514/515 are proposed for BOLT 9. This release cannot connect to v26.06.7-blake2b.4 or older Blake2b releases. A feature declaration is a compatibility check, not proof of a peer’s chain or honesty.

Ordering a Large channel? Enable wumbo first.

The Large package is 25,000,000 sats (0.25 XBT). Channels above 16,777,215 sats require both nodes to advertise large-channel support, also called wumbo. This applies to public and private channels. Starter and Standard are below this threshold.

LND / Paul Lamb’s implementation

Enable large channels in your node app’s settings, or add this option to your LND configuration:

protocol.wumbo-channels=true

Restart LND after saving, then reconnect to Paperclip so the new capability is negotiated. If your node has a separate maximum channel-size setting, allow at least 25,000,000 sats.

Core Lightning (CLN)

Modern CLN enables large channels by default. For older or customized builds that require an explicit setting, enable large-channels according to that build’s documentation, restart, and reconnect. Check the negotiated capability rather than relying only on a settings label.

Complete this before requesting a Large quote or paying. If you already paid and your order is in manual review, enable the setting and contact Paperclip with your existing order reference. Do not pay again.

References: LND large-channel support · CLN configuration.

OPTION 1 · CLEARNET

Connect using our domain

Copy the complete address below into your Lightning dashboard.

02bfcaa8328a89aa03ef55b3b810dc0dc43ee6df1e8d4cc8badb219ba303063389@lightning.paperclippool.xyz:9735

Use a Lightning node compatible with Bitcoin Blake2b. No Paperclip account or password is needed.

Using a dashboard or wallet

Open your node’s peer manager
In your compatible Lightning dashboard or wallet, go to Peers or Connections, then choose Add peer or Connect peer.
Paste the peer address
Use the full address above. If your interface asks for separate fields, enter:
Node public key
02bfcaa8328a89aa03ef55b3b810dc0dc43ee6df1e8d4cc8badb219ba303063389
Host
lightning.paperclippool.xyz
Port
9735
Connect and confirm
Select Connect. Paperclip should appear in your connected peers. Connecting does not open a channel or move funds.

Using a command-line interface

Use the peer-connect command provided by your implementation with the public key, host and port above. Command names and configuration differ between implementations.

OPTION 2 · TOR

Connect over Tor

Use this Tor v3 peer address to connect without public DNS or a direct clearnet connection to Paperclip. It reaches the same Lightning node, with the same public key and feature requirements.

02bfcaa8328a89aa03ef55b3b810dc0dc43ee6df1e8d4cc8badb219ba303063389@zsrixvdofis6b5ti6qtoexltczqnmfxhymfi4ykrotverzskd7ch54ad.onion:9735

Your Lightning node must have a working Tor SOCKS proxy configured. Paste the full address into its peer manager. Configure a Tor SOCKS proxy using the documentation for your implementation.

Confirm either connection

Check the peer list in your dashboard, API or command-line interface and confirm that Paperclip is connected.

Before opening a channel

Verify that both nodes use compatible Bitcoin Blake2b software. A peer connection alone does not establish chain compatibility. Fund new channels only with coins received after Blake2b activation (height 961,640). Transactions signed with unified sighash are not replayable on SHA-256 Bitcoin, including when they spend pre-activation coins. This protection applies to the transaction signed with unified sighash; a funding transaction signed without it needs separate replay protection. Existing channels carry over with their stored channel-type feature number migrated during the database upgrade; the upgraded database cannot be opened by the old release. Coinbase-funded channels and pre-activation channel gossip are rejected. An older counterparty must upgrade before it can reconnect or cooperatively close. Channel funding is a separate action and requires funds on your node.

Trouble connecting?

For clearnet, check that your node can resolve lightning.paperclippool.xyz and make outbound TCP connections on port 9735. For Tor, check that your Tor service is ready, your Lightning node can reach its SOCKS proxy, and you used the complete onion hostname on port 9735. For either connection, use the complete public key and check your node’s connection logs. An unsupported-feature error means the peer software needs upgrading; opening a firewall port will not fix a protocol mismatch.

Connect withPaperclip.