# icRamp — A Trustless Multi-Chain P2P On/Off-Ramp on ICP

**URL:** <https://forum.dfinity.org/t/icramp-a-trustless-multi-chain-p2p-on-off-ramp-on-icp/59847>\
**Category:** Showcase\
**Created:** [November 15, 2025, 1:52am UTC](https://forum.dfinity.org/t/icramp-a-trustless-multi-chain-p2p-on-off-ramp-on-icp/59847 "2025-11-15T01:52:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Reymon](https://avatars.discourse-cdn.com/v4/letter/r/ba8739/32.png) [@Reymon](https://forum.dfinity.org/u/Reymon)\
**Post date:** [November 15, 2025, 1:52am UTC](https://forum.dfinity.org/t/icramp-a-trustless-multi-chain-p2p-on-off-ramp-on-icp/59847/1 "2025-11-15T01:52:11Z")

</div>

## **Project Highlights**

icRamp is a trustless P2P on/off-ramp supporting Bitcoin, Ethereum, Solana, and ICP.  
Users can exchange fiat ↔ crypto using PayPal, Revolut, Stripe, email, or fully on-chain crypto payments (BTC/ETH/SOL/ICP/SPL/ICRC1/ERC20).  
The system uses the Internet Computer to verify payments, orchestrate orders, and release funds through a unified multi-chain vault.  
Target users are Web3 traders, small OTC desks, and communities needing global P2P liquidity without custodial risk.

## **Web3 Advantages**

Traditional Web2 P2P ramps require custody, KYC enforcement, and centralized trust.  
icRamp is different:

- Funds never sit in a custodial account.

- Fiat is verified via programmable HTTP outcalls (PayPal, Stripe).

- Crypto flows entirely wallet-to-wallet.

- Release logic is decentralized in ICP canisters.

- Multi-chain support is native: BTC UTXOs, EVM logs, SPL transfers, ICRC1.

- Users remain anonymous while still protected by verifiable state transitions.

There is **no Web2 equivalent** of icRamp because Web2 platforms cannot do trustless multi-chain validation.

## **How It Is Built**

- **Languages:** Rust (canisters), TypeScript (frontend/Telegram), Solidity (EVM vault v2).

- **ICP Features:** HTTP outcalls (PayPal, Stripe), ic-alloy (EVM RPC), Management Canister calls, stable memory.

- **3rd-party integrations:** PayPal APIs, Stripe Connect, RPC EVM canister, Solana RPCs, Bitcoin RPC.

- **Architecture:**

Decision philosophy:

- Keep chains independent.

- ICP holds only the **business state** , not user funds.

- Users always control their keys.

## **Internet Computer Superpowers**

icRamp could _only_ be built on the Internet Computer because:

- **HTTP Outcalls:** backend verifies Stripe/PayPal payments autonomously.

- **Deterministic Rust canisters:** clean multi-chain state machine.

- **ic-alloy:** typed ABI-free EVM calls.

- **Cheap compute & long-term storage:** persistent orderbook, fills, and user providers.

- **Security boundary:** vault logic in canisters, not smart contracts.

Without ICP’s outcalls + canister orchestration, trustless fiat ↔ crypto P2P would not be possible.

## **Status of the Project**

**3 grants completed** (EVM integration, Bitcoin vault, Solana integration + Payment Layer overhaul).  
Production-ready prototype shipped with:

- Stripe Connect

- Revolut & PayPal

- Crypto payment flows

- Bitcoin/EVM/Solana/ICP order support

- Liquid Orders (partial fills & top-ups)

- Multi-wallet login

- EVM vault v2 using ic-alloy

- 20+ devlogs documenting the entire development journey

We are currently preparing compliance requirements (Stripe/PayPal permissions) before public launch.

## **Resources**

- **Dapp:** [https://sandbox.icramp.xyz/](https://sandbox.icramp.xyz/)

- **GitHub:** [GitHub - reymom/ic2P2ramp: Decentralized onramp and offramp protocol for Ethereum, Bitcoin, and ICP](https://github.com/reymom/ic2P2ramp)

- **Blog Devlogs:** [icRamp Devlog #13 — Stripe Backend (Connect + Checkout)](https://www.reymom.xyz/blog/icramp/2025-10-15-icp-grant-devlog-13-stripe-backend)

- **Twitter/X:** [https://x.com/ic\_rampXYZ](https://x.com/ic_rampXYZ)

- **Video:** [https://youtu.be/m6w7ekt2fzQ](https://youtu.be/m6w7ekt2fzQ)