FAQ

Is this audited?

No. Coalesce has not undergone a third-party security audit. It's early-stage and testing in public, so treat it accordingly.

Is the source code public?

Not yet. Binaries are distributed via coalesce-releases, the only public Coalesce repo, and it ships binaries only. Using Coalesce today means trusting that the published binary matches its claimed behavior. Source will be made public in the future.

Is this on mainnet?

No. Coalesce runs on Bitcoin signet, not mainnet. Don't route real funds through it.

Who can move my funds?

Nobody unilaterally. Every cluster is protected by a dealerless-keygen threshold key: funds stay safe as long as more than two-thirds of members are honest, and a single honest node can always recover its own money. See Concepts: Safety Model.

What happens if my node crashes?

Restart it. Your local state (balances, keys, config) is already saved to disk, so run just picks back up where you left off. Separately, on every startup your node also re-checks whether the cluster is still open on-chain, even if it missed something while it was down, and reports the final payouts itself if it finds a recognized close. See Guides: Recovering After Being Offline.

How many on-chain transactions does it take to open a cluster of N people?

One. Every member runs dfund independently, but all of those contributions are inputs to a single joint funding transaction, so a cluster of any size N opens with exactly one on-chain transaction, not one per pair and not one per member. See Concepts: Clusters.

Can a payment reach someone outside my cluster?

Yes, by hopping through however many shared members separate the two clusters, however many that turns out to be. This is already built and running internally but still being tested, so there's no CLI command for it yet. See Concepts: Clusters.

What if a peer goes offline during keygen or funding?

keygen and dfund re-announce for a while, so a briefly-dropped peer usually catches up on its own. If there's no progress for a couple of minutes, Ctrl-C every node and retry. See Guides: A Peer Dropping During Keygen or Funding.