# Peer > No barriers, no middlemen, just peer Peer is a peer-to-peer crypto marketplace and payment protocol, formerly known as ZKP2P. It lets users trade fiat and crypto directly through everyday payment apps without a custodial middleman. Peer is a peer-to-peer crypto marketplace and payment protocol that connects everyday payment apps to onchain crypto. It is aimed at people who want to buy or sell crypto without routing through a custodial exchange, giving both individual traders and liquidity providers a direct way to transact using payment methods they already use. The protocol addresses the friction and fees of conventional onramps and offramps, where a platform account, payment processor, and approval queue typically sit between the two sides of a trade. On Peer, a seller deposits crypto into a non-custodial onchain escrow and sets a price, while a buyer pays the seller directly through a payment app. Cryptographic techniques verify that the payment occurred, confirming amount, recipient, and timing without exposing bank details or transaction history, after which the escrow contract releases the crypto to the buyer. The offering centers on the Peer app, which supports trading, cash-out to everyday payment platforms, and yield for liquidity providers who fund escrow. It is used by privacy-conscious traders, newcomers seeking a simple way into crypto, and liquidity providers earning returns by supplying funds to the marketplace. The project previously operated under the name ZKP2P and now presents its consumer-facing marketplace and protocol under the Peer brand. - Type: Protocol - Sector: Payments - Status: Active - Founded: 2023-11-01 - Profile: https://thegrid.id/profiles/peer ## Products - [Peer Protocol](https://thegrid.id/profiles/peer): Peer Protocol is a peer-to-peer onramp and offramp that lets users trade crypto directly with other users through everyday payment apps. Sellers deposit stablecoins into onchain escrow and set rates, while buyers pay through their preferred payment method and receive crypto once payment is verified through privacy-preserving proofs. The protocol keeps funds non-custodial throughout, releasing assets directly to a buyer wallet without a middleman holding funds. It supports trading across multiple blockchains and a range of payment applications and fiat currencies. (On/Off Ramp, Live, Main Product) - [PeerAuth](https://thegrid.id/profiles/peer): PeerAuth is a browser extension that helps buyers authenticate payment transactions when completing fiat-to-crypto trades on the Peer platform. It opens the selected payment provider, captures only the metadata required to verify a transaction, and encrypts sensitive session material before sending it to a verified attestation service. The tool does not store a wallet, browsing history, or persistent account data, and is used by traders needing faster, privacy-preserving payment verification. (Developer Tooling, Live) ## Links - [Main](https://www.peer.xyz) - [Documentation](https://docs.peer.xyz) - [Media Kit/branding](https://docs.peer.xyz/brand-kit) - [Blog](https://docs.peer.xyz/blog) - [Privacy policy](https://www.peer.xyz/pp) - [Terms of Service](https://www.peer.xyz/tos) - [Twitter / X](https://x.com/zkp2p) - [Telegram](https://t.me/+XDj9FNnW-xs5ODNl) - [GitHub](https://github.com/zkp2p) - [Twitter / X](https://x.com/peerxyz) - [Discord](https://discord.com/invite/h3rzP79jj3) - [YouTube](https://www.youtube.com/@ZKP2P) ## Legal This data is provided under two licensing models. Model 1 - open data. The open data core is licensed under the Open Database License (ODbL) — a copyleft/share-alike license allowing free use, modification, and sharing for any purpose. Attribution is required: include "Powered by The Grid" linking to https://thegrid.id wherever the data is used. Derivative databases must be shared under ODbL terms. Trademarks, logos, and brand names (marked "Special TPIP") are not covered by the ODbL. For ML/AI use: training datasets that substantially extract ODbL data are Derivative Databases and must be shared under ODbL if publicly used; models must be attributed in documentation. Model 2 - commercial licenses. The Grid Data Service (TGDS) is also available as a commercial license. See [Web Services Terms](https://about.thegrid.id/legal/web-services-terms) for commercial use that is not covered by the open data service. The following applies to both licensing models. - All data is provided AS IS with no guarantees of accuracy. - The Grid does not provide investment, legal, or tax advice, and - a project's presence in The Grid's data does not imply endorsement. - [Data Licensing & Disclaimers](https://about.thegrid.id/legal/data-licensing-and-disclaimers): Licensing models and disclaimers - [Open Data (ODbL)](https://about.thegrid.id/legal/open-data): Open Database License terms and scope for The Grid's open data service. - [Attribution Guidelines](https://about.thegrid.id/legal/open-data-attribution-guidelines): How to attribute The Grid's data when using the open data service. - [Web Services Terms](https://about.thegrid.id/legal/web-services-terms): commercial Terms for using data services. - [All Legal Documents](https://about.thegrid.id/legal): Full index of terms, policies, and disclosures ## Optional - [TGS Field Descriptions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-field-descriptions.md): Schema field definitions for The Grid's data model - [TGS JSON Structure](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-json-structure.md): Data model structure and relationships - [Product Type Definitions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-definitions.md): Definitions for each product type - [Product Type Classification](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-classification.md): Guide for classifying products into types - [Grid MCP Guide](https://github.com/The-Grid-Data/workspace-public/blob/main/grid-search/skills/grid-query/references/grid-mcp-guide.md): How to query The Grid programmatically via MCP