Privacy

Why settling a cluster's shared state to Bitcoin isn't the same as recording every payment inside it.

Bitcoin provides transparent, verifiable settlement, but every transaction written to the blockchain becomes part of a permanent public history.

Coalesce takes a different approach: payments between members can occur within a shared, multi-party Bitcoin channel without creating a separate Bitcoin transaction for every payment. Instead of moving Bitcoin on-chain every time two members transact, Coalesce maintains a shared state between the members and settles that state to Bitcoin when required.

One shared settlement layer

A cluster is formed by multiple members around a shared Bitcoin funding output. Members can then transfer value between one another while the funds remain within that shared structure. An internal payment such as A -> C: 0.5 BTC does not necessarily create a Bitcoin transaction, so the blockchain doesn't receive a separate permanent record saying that A paid C.

What Bitcoin sees

The blockchain primarily sees the lifecycle of the shared settlement structure: funding, then whatever internal payments happen inside it, then final settlement. The individual transfers occur within the cluster's state rather than becoming individual Bitcoin transactions.

The core distinction

Bitcoin records the settlement of the shared state, not necessarily every payment that occurred within that state.

Why the multi-party structure matters

A traditional bilateral channel represents a relationship between two members. Coalesce extends that to multiple members within a single shared settlement structure, so payments like A -> B, C -> D, E -> A, and B -> C can all happen inside a five-member cluster without four separate Bitcoin transactions being created. When the cluster eventually settles, the blockchain observes the resulting settlement rather than a separate on-chain transaction for every internal transfer.

No central transaction database

Coalesce is designed without a central transaction database that records every payment made through the network. The protocol operates through distributed members and cryptographically authorized state transitions, so there's no central ledger anywhere containing a complete history like "A paid B, B paid C, C paid D...". The goal is to minimize the amount of information that needs to become permanent or centrally accumulated.

Privacy without sacrificing Bitcoin settlement

Coalesce doesn't attempt to replace Bitcoin's settlement guarantees; Bitcoin remains the underlying settlement layer. The goal is instead to separate payment activity from blockchain settlement. Members transact within the shared state, while Bitcoin ultimately secures and settles that state, preserving Bitcoin's native settlement model while reducing how much payment activity has to be permanently exposed on-chain.

What this does, and doesn't, hide

Scope of the guarantee

Coalesce prevents individual internal payments from automatically becoming individual Bitcoin transactions. It does not prevent the Bitcoin blockchain from exposing information about the funding and settlement of the shared structure itself, including transaction data, amounts, addresses, and timing. Bitcoin transactions routed through Coalesce are not untraceable.

Coalesce moves payment activity into a shared multi-party off-chain state, reducing how much individual payment information gets permanently recorded on the Bitcoin blockchain.

The result

Instead of one Bitcoin transaction per payment, the model becomes many payments settling into one shared multi-party state, which then settles to Bitcoin once. Members can transact within a shared settlement environment without turning every internal transfer into a permanent blockchain transaction. Privacy here isn't an added database feature bolted on top; it's a consequence of how the settlement structure itself is designed.