Peach Bitcoin primary sources — 2026-05-03

Project status in this pass

• No canonical standalone Peach Bitcoin whitepaper or litepaper surfaced.
• The clearest current sources of truth in this pass were the official website content repository, the official API docs repository, and the Peach GitHub organization.
• The main peachbitcoin.com site returned a Cloudflare block to automated fetches during this pass, but the first-party website-content repo and API docs repo still exposed the core product posture.

Primary-source snapshots

1) Official website content repository

• URLs:
  • https://github.com/Peach2Peach/public-website
  • https://raw.githubusercontent.com/Peach2Peach/public-website/master/content/default/index.md
• Key excerpt:
  • The homepage content frontmatter describes Peach Bitcoin as: “Buy and sell Bitcoin peer-to-peer without KYC. Peach is a non-custodial mobile marketplace for private, anonymous Bitcoin transactions — available on iOS, Android, and APK.”
  • This matters because it is the clearest first-party statement of Peach’s user-facing positioning: no-KYC, non-custodial, peer-to-peer Bitcoin marketplace rather than broker, custody app, or simple wallet.

2) Official API docs introduction

• URLs:
  • https://docs.peachbitcoin.com/
  • https://github.com/Peach2Peach/peach-api-docs
  • https://raw.githubusercontent.com/Peach2Peach/peach-api-docs/master/source/index.html.md
• Key excerpt:
  • The docs say the Peach API has public and private endpoints.
  • Public market data is available without API credentials.
  • Private data is accessed via an auth token acquired by presenting a public key plus a signed message.
  • This is strong evidence that Peach exposes a signed-wallet-style access model rather than ordinary username-password app auth.

3) System info and payment-method metadata

• URL: https://raw.githubusercontent.com/Peach2Peach/peach-api-docs/master/source/includes/public/_system.md
• Key excerpt:
  • The GET /v1/info endpoint exposes Peach PGP key material, escrow-fee metadata, supported payment methods with supported currencies, and minimum/latest app version data.
  • The GET /v1/info/paymentMethods endpoint documents structured templates for payment rails and field requirements.
  • This matters because Peach is publishing a real trading-rail metadata surface, not just a consumer app download page.

4) Payment-method type registry

• URL: https://raw.githubusercontent.com/Peach2Peach/peach-api-docs/master/source/includes/_types.md
• Key excerpt:
  • The docs enumerate 56 payment methods in this pass, including bank-transfer variants, local wallet/payment apps, PayPal-style services, gift-card style methods, lnurl, and liquid.
  • This breadth suggests Peach is operating a payment-method discovery and normalization layer around P2P Bitcoin trading.

5) Offer discovery endpoints

• URL: https://raw.githubusercontent.com/Peach2Peach/peach-api-docs/master/source/includes/public/_offer.md
• Key excerpt:
  • Peach exposes searchable sell and buy offer endpoints with pagination, sorting rules such as bestReputation and lowestPremium, visible meansOfPayment, and escrow fields in offer responses.
  • This matters because the product is not just a wallet or bulletin board; it operates a searchable market surface with escrow-aware order metadata.

6) Private authentication flow

• URL: https://raw.githubusercontent.com/Peach2Peach/peach-api-docs/master/source/includes/private/_authentication.md
• Key excerpt:
  • The auth flow requires publicKey, message, and signature, with the docs stating the signature verifies the user owns the private key associated with the public key.
  • Tokens are valid for 60 minutes, and registration can happen automatically when obtaining access.
  • This reinforces the account model as key-based access and reputation continuity, not email/password identity.

7) Contract and escrow workflow

• URL: https://raw.githubusercontent.com/Peach2Peach/peach-api-docs/master/source/includes/private/_contract.md
• Key excerpt:
  • Contract payloads include escrow addresses, batch and release PSBT data, encrypted payment data, dispute fields, payment-confirmation state, ratings, and release transaction identifiers.
  • This is decisive evidence that Peach packages the operational backend for escrowed peer-to-peer trades, not merely listing discovery.

8) Broader GitHub operating surface

• URL: https://github.com/Peach2Peach
• Key excerpt:
  • The org exposes first-party repos for the mobile app, web app, API docs, TypeScript API wrapper, batching service, and Peach Improvement Proposals.
  • This indicates Peach treats its engineering and protocol-adjacent surfaces as part of the product’s public operating layer.

Working conclusion

Peach Bitcoin is best cataloged as peer-to-peer Bitcoin marketplace infrastructure with a substantial escrow, payment-method, and key-auth control plane behind it. The decisive signal in this pass was the combination of no-KYC/non-custodial marketplace positioning, public market-data endpoints, signed-public-key authentication, searchable offers, encrypted contract/payment workflows, and a broad first-party repo footprint.