Ghost Pay
Fast, private Bitcoin payments. Lock once, send freely, settle anytime.
Overview
Ghost Pay is a Layer 2 payment system built on Bitcoin. Unlike Lightning, it doesn't require managing channels, finding routes, or worrying about liquidity. The mental model is simpler:
Fees
Ghost Pay charges a flat 0.1% fee on payments. This fee is split between the Treasury and Node Reward Pool using the same control decay ratio as the mining pool fee. After ossification, 100% of Ghost Pay fees go to the Node Reward Pool.
How It Works
Locking Funds
To use Ghost Pay, you first lock Bitcoin into a vault. This is a special Bitcoin transaction that:
- Commits your funds to the Ghost Pay system
- Creates a UTXO that can only be spent according to vault rules
- Defines your maximum spending capacity
The locking transaction is a standard Bitcoin transaction — it confirms on L1 like any other.
Sending Payments
Once locked, you can send payments instantly:
- You create a payment to a Ghost address
- The payment is signed with multi-party signatures
- The payment is recorded in a microblock
- The microblock is anchored to Bitcoin via a commitment
Payments confirm in ~10 seconds. The recipient can spend immediately.
Receiving Payments
Receiving is even simpler:
- Share your Ghost address (or generate a stealth address)
- Payments arrive automatically
- You can receive even while offline
- Claim payments when you reconnect
Settlement
When you want to move funds back to regular Bitcoin:
- Request a settlement
- The vault closes with a Bitcoin transaction
- Your funds appear at your Bitcoin address
Settlement takes ~10 minutes (one Bitcoin confirmation).
Ghost Pay vs Lightning
Ghost Pay and Lightning solve the same problem differently:
| Feature | Lightning | Ghost Pay |
|---|---|---|
| Channels | Required (open/close) | Not needed |
| Routing | Find path through network | Direct to recipient |
| Inbound Liquidity | Required to receive | Not needed |
| Online Requirement | Must be online to receive | Receive while offline |
| Payment Failures | Common (routing issues) | Rare (direct path) |
| Privacy | Limited (onion routing) | Strong (stealth addresses) |
| Max Payment | Limited by channel | Limited by vault |
| Complexity | High | Low |
Vault Channels
Vaults are the core primitive of Ghost Pay. A vault is a programmable Bitcoin UTXO with specific spending rules.
Vault Structure
Vault {
capacity: 1.0 BTC // Maximum funds
balance: 0.75 BTC // Current balance
owner: pubkey // Your public key
state_root: hash // Merkle root of state
spend_paths: [
cooperative_close, // Both parties agree
unilateral_close, // Timeout + proof
penalty // Fraud detected
]
}Vault Types
- Personal Vault — Single-owner, for spending
- Shared Vault — Multi-party, for business/escrow
- Merchant Vault — Optimized for receiving many payments
QTxIn / QTxOut
Ghost Pay uses structured transaction descriptors:
- QTxOut — Describes a vault's on-chain representation
- QTxIn — Describes how a vault can be spent
These allow full reconstruction of vault state from on-chain data.
Multi-Party Signatures
Ghost Pay uses multi-party signing to ensure state integrity:
- All parties must agree to state transitions
- No "half-signed" or inconsistent states are possible
- Revocation is cryptographically enforced
- Based on secp256k1 ECDSA signatures
How It Works
- Sender proposes a payment
- All affected parties sign the new state
- Old state is cryptographically revoked
- New state becomes the only valid state
If anyone tries to publish an old state, the penalty path activates and they lose funds.
Privacy Features
Ghost Pay is private by default:
Settlement
Ghost Pay uses BUDS-tagged commitments to anchor state to Bitcoin:
Anchoring Methods
- segOP (if adopted) — Structured TLV lanes in segregated data
- OP_RETURN — Fallback using standard OP_RETURN outputs
Microblocks
Ghost Pay batches many payments into microblocks:
- Microblocks are off-chain state transitions
- Many microblocks are summarized into a single commitment
- Commitments anchor to Bitcoin periodically
- Full state can be reconstructed from Archive nodes
Settlement Types
| Type | Time | Use Case |
|---|---|---|
| Cooperative Close | ~10 minutes | Normal settlement, all parties agree |
| Unilateral Close | ~1 week | Counterparty unresponsive |
| Penalty Close | Immediate | Fraud detected (old state published) |
Development Status
Ghost Pay is currently in development. The roadmap:
| Phase | Status | Description |
|---|---|---|
| Specification | Complete | Protocol design finalized |
| Reference Implementation | In Progress | Core libraries being built |
| Testnet | Planned | Testing on Bitcoin testnet |
| Mainnet | Future | Production launch |
Ghost Core and Ghost Pool launch first. Ghost Pay follows once the node network is established.