Transparent ledger, private receipt
Every output is public; BIP-352 keeps them from linking back to one reused address.
Asset focus
Built around privacy, without flattening different protocols into one story.
₿
Bitcoin
The payment rail.
ColdHarbor's sending and receiving interface is built around BIP-352 Silent Payments, with destination validation, fee review, local signing, and network status. Privacy here comes from not reusing an address, not from obscuring the chain.
- Payments
- Send and receive
- Address model
- BIP-352
- Approval
- Local signing
- Receive
- A reusable Silent Payment code; senders derive unique taproot outputs.
- Send
- Paste or scan a code, review amount and fee, authorize local signing, await acceptance.
- Confirmation
- Pending and confirmed states come from network authority, shown explicitly.
- Privacy model
- Address-reuse avoidance via BIP-352, not mixing or obfuscation.
M
Monero
A distinct privacy asset.
Monero remains separate from the Bitcoin payment flow. Its privacy is protocol-native— ring signatures, stealth addresses, and confidential amounts—so it is held and described on its own terms, never as a Silent Payment.
- Position
- Privacy asset
- Protocol
- Monero native
- Silent Payments
- Not applicable
Why keep them separate
One portfolio does not mean one protocol.
Collapsing distinct chains into a single "send anything" abstraction hides exactly the details that matter for privacy. ColdHarbor names the chain, method, and network state at the moment they apply.
Opaque ledger by construction
Amounts and destinations are hidden at the protocol level, with a different threat model.
CPU-mined, cannot be shut down
A native proof-of-work coin. Self-custody dbl1 addresses; keys and signing stay on the device.
No false equivalence
The interface never implies a Bitcoin privacy technique applies to another asset.