Skip to main content
0xramp is a non-custodial fiat ↔ crypto on/off-ramp built on a lightweight, composable stack. This page gives developers and contributors a mental model of how the pieces fit together — what 0xramp builds and owns, and what it delegates to best-in-class protocol SDKs.

​
Stack Overview

​
How the Layers Interact

When a user initiates a transaction in the UI, the React frontend sends the order parameters to the Express API, which coordinates session state and order lifecycle. The Express layer invokes the @p2pdotme/sdk to place the on-chain order, match a Pix counterparty, and manage USDC escrow on Base. Once USDC is settled, NEAR Intents executes the conversion into the user’s target asset (e.g. ZEC, SOL, ETH). Status updates from both P2P.me and NEAR Intents are surfaced back through the API and reflected in real time in the frontend UI.

​
What 0xramp Owns vs. What It Delegates

0xramp owns

  • Product UX and quote presentation
  • Session correlation and order status display
  • Wallet connection surface (Rabby, Phantom, thirdweb)
  • Frontend routing and state management
  • Express API orchestration layer

Delegates to protocols

P2P.me — identity, KYC, Pix matching, USDC escrow, reputation and limitsNEAR Intents — USDC ↔ target asset swaps
0xramp does not fork or heavily customize P2P.me’s core SDK — it uses the pure @p2pdotme/sdk integration path.

​
Source Code

0xramp is open source. The GitHub organization is at github.com/0xramp. Specific repository URLs will be linked here when public. Architecture Decision Records (ADRs) documenting significant technical choices will also be linked from this page when published.
TODO: Add link to the public repository and ADR directory when available.