Thanks Reuben, appreciate the quick reply. To provide more detail for the community.
What we’re solving
Privacy-focused networks like Firo lose both privacy and adoption when users have to rely on centralized exchanges to move between fiat and crypto. This hits hardest in the Global South, where peer-to-peer trading is a main way people get crypto, and many are pushed onto centralized platforms with a poor user experience.
Onboarding into a currency like Firo with fiat today has four main problems:
- Custody risk and account freezes: To sell on a centralized P2P desk, users first deposit their assets into the exchange’s wallet. If the platform freezes the account, the funds are stuck until the exchange releases them.
- Privacy loss: Most centralized exchanges don’t support shielded deposits, so users must give up the privacy Firo is built to protect just to cash out.
- The KYC barrier: Centralized fiat ramps require heavy identity checks and often reject users from emerging regions where P2P trading is needed most.
- DEX blind spot: On-chain DEXs are good for crypto-to-crypto swaps but can’t process bank transfers, payment apps, or local cash.
The result is less financial sovereignty, less accessibility, more dependence on centralized infrastructure, and less economic activity inside the Firo ecosystem.
Our solution: Local Money
We’re building a non-custodial P2P fiat on/offramp where users buy and sell crypto directly with each other using local payment methods, without depositing assets on a centralized exchange. Users keep control of their funds, and we want to let them enter privacy-focused assets like Firo through local payment rails without arbitrary exchange freezes.
Why Firo?
We think Firo is a natural fit because of its focus on financial privacy and its Lelantus Spark shielded protocol. The integration would let users receive and cash out into Firo privately using shielded addresses, without relying on a centralized exchange for custody.
Where we are
Currently in development for Solana, with more networks planned.
What we’re asking
We’re fully funding and building the integration ourselves. We’re not asking for grants, treasury capital, or development resources from Firo.
All we need from the core team or community developers is pretty light:
- A technical review and feedback, so our implementation aligns cleanly with Firo’s Lelantus Spark architecture and properly supports shielded addresses.
- Once it’s tested and meets the team’s requirements, coordination so the integration can be recognized in official channels.
We’d love to open a direct line with you, Reuben, or the core team to map this out.
Would the team be open to exploring this? Happy to jump on a short call or share a technical overview whichever is convenient.