Status
Completed
Triangle Capacity
SAT 1,500,000
1.5M SAT / 0.015 BTC / ~$1,290
Spaces Available
None
All 3 spaces are filled
Channel Duration
12 months or more
Open at least till: July 02, 2027
Participant Restrictions
Channels
2 channels
Minimum number of channels
Capacity
220,000 SAT
Minimum total channel capacity
Connection
Tor
Only nodes with a Tor address can join
Additional Rules
I’m initiating a Lightning channel triangulation initiative with a focus on robust, minimal-latency, and policy-consistent routing. I’m seeking peers who prioritise network health and long-term stability.
My configured parameters (fixed and steadfast):
- Base fee: 2 sats
- Fee rate: 0.001% (10⁻⁵)
- CLTV delta: 40 blocks
- Max HTLC: 1,500,000 sats
- Min HTLC: 1 sat
Operational commitments:
- Uptime stability: ≥ 99.5% (allowing up to 3 hours of essential downtime per month for maintenance or network events)
- Channel longevity: A minimum 12-month commitment to ensure meaningful routing utility and network contribution
- Routing policy: Strict adherence to the above parameters, maintaining steady fees and collaborative consistency
I operate with a long-term vision, contributing to network resilience and prioritising steady, reliable routing. My goal is to contribute to a resilient, well-configured mesh — where channels remain active, predictable, and fair for all participants.
Peer Availability and Communication:
To maintain optimal network health and channel liquidity, I highly value peers who keep their nodes consistently online and responsive. I appreciate partners who maintain steady uptime and engage in prompt, clear communication. This proactive approach allows us to keep our channels healthy and cooperative. Should a node experience extended downtime, I welcome open dialogue to find a mutually beneficial solution, ensuring our routing paths remain reliable and efficient for the entire network.
Open to mutual channel openings with nodes that share similar operational rigour.
Note: I prefer privacy-preserving channels and support Tor/LNURL for secure coordination.
Description
This is a Bitcoin Lightning Network liquidity swap agreement, designed to help LN node operators generate both outgoing and incoming liquidity, increase connectivity and decentralization of the network.
Agreement ID: 24300 was created on July 01, 2026 by Benevolent_Path_0.
What to Do Next?
Node
Channel Open Reported
A reported opening to B
Node
Channel Open Reported
B reported opening to C
Node
Channel Open Reported
C reported opening to A
Activity Log
-
System recorded the current state during historical backfill.
Snapshot at backfill time; earlier actions and their dates are unknown.
September 13, 2026 at 03:32:57 UTC
Trashed: No
Swap setup status: Setup completed
Rebalance node: Not set
Rebalance completed: No
Rebalance dismissed: Yes
Tor: Yes
Prime: No
Private: No
Capacity (sats): 1500000
Clearnet: No
Duration (months): 12
Platform: any
Rebalance: No
Description: I’m initiating a Lightning channel triangulation initiative with a focus on robust, minimal-latency, and policy-consistent routing. I’m seeking peers who prioritise network health and long-term stability. My configured parameters (fixed and steadfast): - Base fee: 2 sats - Fee rate: 0.001% (10⁻⁵) - CLTV delta: 40 blocks - Max HTLC: 1,500,000 sats - Min HTLC: 1 sat Operational commitments: - Uptime stability: ≥ 99.5% (allowing up to 3 hours of essential downtime per month for maintenance or network events) - Channel longevity: A minimum 12-month commitment to ensure meaningful routing utility and network contribution - Routing policy: Strict adherence to the above parameters, maintaining steady fees and collaborative consistency I operate with a long-term vision, contributing to network resilience and prioritising steady, reliable routing. My goal is to contribute to a resilient, well-configured mesh — where channels remain active, predictable, and fair for all participants. Peer Availability and Communication: To maintain optimal network health and channel liquidity, I highly value peers who keep their nodes consistently online and responsive. I appreciate partners who maintain steady uptime and engage in prompt, clear communication. This proactive approach allows us to keep our channels healthy and cooperative. Should a node experience extended downtime, I welcome open dialogue to find a mutually beneficial solution, ensuring our routing paths remain reliable and efficient for the entire network. Open to mutual channel openings with nodes that share similar operational rigour. Note: I prefer privacy-preserving channels and support Tor/LNURL for secure coordination.
Positions: 3
Minimum capacity (sats): 220000
Min channels: 2
Participants at backfill time:
Benevolent_Path_0 (A) — completed
ZozoMG (B) — completed
Elind (C) — completed
-
System reconstructed channel opening from the swap's saved start date.
Reconstructed from saved data. Names reflect profiles at backfill time.
July 2, 2026 at 19:23:47 UTC
-
System reconstructed Elind (C) joining the swap from the application's saved creation date.
Reconstructed from saved data. Names reflect profiles at backfill time.
July 2, 2026 at 19:23:47 UTC
-
System reconstructed ZozoMG (B) joining the swap from the application's saved creation date.
Reconstructed from saved data. Names reflect profiles at backfill time.
July 1, 2026 at 09:36:10 UTC
-
System reconstructed Benevolent_Path_0 (A) joining the swap from the application's saved creation date.
Reconstructed from saved data. Names reflect profiles at backfill time.
July 1, 2026 at 08:40:37 UTC
-
System reconstructed swap creation by Benevolent_Path_0 from the saved creation date.
Reconstructed from saved data. Names reflect profiles at backfill time.
July 1, 2026 at 08:40:37 UTC
Comments
Sorry, once the Liquidity Swap is full, only participants of this swap can read or post comments.