Running live on Bitcoin signet.
Not a simulation.
Coalesce runs across a real multi-node cluster on signet today. Below is a representative session against that cluster: bootstrap, keygen, fund, send, checkpoint.
01 / Inside the Cluster
One shared UTXO. Every payment stays off-chain until checkpoint.
Five members share one cluster. Any two members can pay each other at any time, with no separate on-chain transaction per payment; the next checkpoint locks all of them in together.
$ coalesce-node bootstrap -dir ./me -addr 1.2.3.4:9000 \ -peers "1.2.3.4:9000,5.6.7.8:9001,9.10.11.12:9002" \ -wallet mysignetwallet -enforce✓ identity bundles exchanged over authenticated connections✓ cluster running (3 members, quorum 2) > keygen✓ group key generated distributed-ly, no full key held anywhere✓ node restarted, share loaded > dfund 5000000✓ funding tx broadcast on signet✓ all members funded, cluster open > send bob 250000✓ sent, pending checkpoint > balcluster: 3 members quorum: 2 status: openyou: 4,750,000 sats bob: 250,000 sats > propose✓ checkpoint finalized, payments locked inPayments settle concurrently between any pair, neighbors or not, none waiting on the others; the next checkpoint locks all of them in together.
- One shared cluster, no per-relationship channels
- Multiple payments settle concurrently, none blocking another
- Off-chain until the next checkpoint locks everyone in
02 / Beyond One Cluster · Testing in Progress
Clusters aren't islands.
Coalesce isn't just many separate clusters sitting side by side. A payment can reach a member of any other cluster by hopping through however many shared members actually separate them, one hop for a neighboring cluster, several for a distant one: it's a network of clusters, not a set of isolated groups. This is already built and running internally; it's still being tested, so there's no command for it in the CLI reference yet.
- Reaches any member, hopping through shared members between clusters
- Each cluster credits a hop only once it has proof it landed
- No shared bottleneck across the whole route
Several payments settling concurrently between any pair of clusters, each hopping through however many shared members separate them; which pairs are transacting changes over time.
The bug tracker is open.
For a security-sensitive project, an open bug tracker is a credibility signal, not a weakness. We log issues as we find them, including the embarrassing ones.
View open issues →Signet, not mainnet.
Coalesce is early: running on Bitcoin signet, not audited, not production-ready. Don't route real funds through it yet. Distribution is binary-only for now, and source will be published in the future.