Peer offers a non-custodial Base USDC-to-fiat sell flow that fits Edge’s existing ramp-provider architecture, but it has one product difference worth agreeing before code lands: the user creates an onchain deposit, receives fiat from a matched buyer in a supported payment app, and may need to return to Edge to track or withdraw the order.
I propose adding a sell-only peer provider behind the existing info-server enablement path.
Proposed integration
- Add
src/plugins/gui/providers/peerProvider.ts and register it with the amount-quote plugin.
- Discover current payment platforms, currencies, amount bounds, and required payee fields from
@zkp2p/cash rather than hard-coding them.
- Present the SDK oracle result as an estimate, not a locked quote; the binding rate is set when a buyer fills.
- Use Edge’s existing Base wallet to sign and submit the ordered USDC approval/deposit transactions. Peer never receives a private key and does not custody funds.
- Persist the returned
depositId so the user can resume order status, withdraw unmatched funds, or top up.
- Gate initial availability through Edge’s info server, matching the other ramp plugins.
Affiliate fit
The SDK supports an optional onchain referral code on deposits. That gives Edge attributable filled volume without an API-key dependency. We can coordinate the referral mapping and commercial terms separately; the code path can keep attribution optional.
Product questions
- Should the first version live in the amount-quote sell flow, or would Edge prefer an external-ramp card while the order-status UX is proven?
- Is returning to an in-app order-status scene acceptable, or should the first release deep-link to Peer-hosted tracking?
- Once the approach is approved, can the Edge team provide the
peer info-server flag/referral value for test builds?
I can implement the provider, tests, and integration documentation once the intended UX is confirmed.
SDK: https://www.npmjs.com/package/@zkp2p/cash
Documentation: https://docs.peer.xyz/developer/peer-cash
Reference MCP/tool contract: https://github.com/zkp2p/peer-cash-mcp
Peer offers a non-custodial Base USDC-to-fiat sell flow that fits Edge’s existing ramp-provider architecture, but it has one product difference worth agreeing before code lands: the user creates an onchain deposit, receives fiat from a matched buyer in a supported payment app, and may need to return to Edge to track or withdraw the order.
I propose adding a sell-only
peerprovider behind the existing info-server enablement path.Proposed integration
src/plugins/gui/providers/peerProvider.tsand register it with the amount-quote plugin.@zkp2p/cashrather than hard-coding them.depositIdso the user can resume order status, withdraw unmatched funds, or top up.Affiliate fit
The SDK supports an optional onchain referral code on deposits. That gives Edge attributable filled volume without an API-key dependency. We can coordinate the referral mapping and commercial terms separately; the code path can keep attribution optional.
Product questions
peerinfo-server flag/referral value for test builds?I can implement the provider, tests, and integration documentation once the intended UX is confirmed.
SDK: https://www.npmjs.com/package/@zkp2p/cash
Documentation: https://docs.peer.xyz/developer/peer-cash
Reference MCP/tool contract: https://github.com/zkp2p/peer-cash-mcp