Vinny
New Pivian
Code:
Title: MintIt - PIVX Integration for Open-Source Privacy Payment Processor
Name: mintit-pivx-integration
Term: 1 Cycle
Cycle Amnt: 5,000 PIVX
Total Amnt: 5,000
PIVX Author: Vinny (forum.pivx.org/members/vinny.27891)
Receiver: Vinny
Address: DQJVApoqEgbcp88u7kydhBDi4wzme62VXD
Created: July 21, 2026
Status: Awaiting FeedbackMintIt - PIVX Integration for Open-Source Privacy Payment Processor
mintit.dev | GitHub
Overview
MintIt is a self-hosted, open-source payment processor built for privacy-focused cryptocurrencies — a BTCPay Server alternative purpose-built around privacy coins, not treating them as an afterthought. It generates a unique address per invoice and notifies merchant applications via authenticated webhooks.
I'm requesting a small, one-cycle grant to finish and harden PIVX support as MintIt's third supported coin, alongside my existing Firo and Monero integrations. This is a solo build (open source, auditable by anyone), and I'm keeping the ask modest: PIVX's SDK already does the heavy lifting, and I expect to reach production-ready comfort within a month.
Commitments & Standard
I'll post a progress update on the forum thread partway through the cycle, and again on completion, covering what's shipped and what's left. The codebase is open-source and auditable throughout — commits are public as work lands, not held back until a final reveal. If the work isn't finished by the time the cycle's funds are paid out, I'll say so plainly on the thread rather than go quiet.
Why PIVX, Why Now
BTCPay Server recently added PIVX support — good for the ecosystem, but BTCPay is a generalist processor where privacy coins are one line item among many. MintIt is built around privacy as the core use case, not a checkbox. I see this as complementary to BTCPay's PIVX support, not competing with it: a second, purpose-built on-ramp for merchants who want privacy first.
Track Record
- Firo: production-ready, including shielded (Spark) receiving with sweep-based withdrawal.
- Monero: production-ready, unique address per invoice
- PIVX: integration underway against pivx-js-sdk (built by Liquid369); the SDK makes this doable, and the remaining work is validation and hardening rather than building from scratch.
Shielded Receiving
PIVX support follows the same model as Firo: invoices generate shielded addresses by default, and merchants withdraw by sweeping their balance to a public or shielded address of their choice. My review of pivx-js-sdk indicates this flow is supported, and implementation is underway. I plan to validate with small, real-value transactions rather than testnet, to confirm behavior under live network conditions.
Scope of Work
- Finish and validate shielded-address invoicing and payment detection for PIVX
- Implement and validate balance-sweep withdrawal (shielded → public or shielded)
- Wire PIVX into MintIt's existing invoice, webhook, and per-invoice coin-selection systems
- Live small-value validation on mainnet
- Merchant/self-hosting documentation for PIVX
Budget
5,000 PIV for a single cycle, covering the remaining development and validation work to bring PIVX to the same production standard as Firo and Monero. No multi-month commitment — if the community wants to keep supporting MintIt after this ships, I'm open to a follow-up proposal then.
The Bigger Picture
To be upfront: I want MintIt to become a real, credible alternative to BTCPay Server for privacy-first merchants and users. That's a big undertaking for a solo build, and I'd rather be honest about aiming high than undersell it. Solid PIVX support is a meaningful part of getting there.
Links
- Docs: https://mintit.dev
- GitHub: https://github.com/nexusocean/mintit
- PIVX SDK used: https://github.com/Liquid369/pivx-js-sdk
- Author: https://forum.pivx.org/members/vinny.27891
- Vote hash: TBD
Feedback welcome before this goes to a final vote — happy to answer technical questions about the integration.
Last edited: