Code:
Title: Lead of Business Development15
Name: BusinessDev15
Term: 3 Cycles
Cycle Amount: 45 000
Total Amount: 135 000
Author: Jeffrey
Receiver: Jeffrey
Address: D5DBsoCCuffSBM2VBRpb2ZkrD1qesVMYYF
Status: Active
Vote Hash: f824eca454e892c9c591c73a261ecca2e9121ebc2d4671d5866efb3a79647153 [VOTE HASH]
Hi everyone!
This proposal is to renew my role part time as Lead of Business Development for PIVX for the next 3 cycles. You can see my previous proposal here: LOBD14
I'll be upfront: the last few months have been the hardest stretch for PIVX on the exchange side in a long time. Binance added the Monitoring Tag in June and then delisted PIVX on 17 August, citing many particular reasons that they wouldn't completely disclose. Gate.io also delisted after hiding us as a privacy coin for some time. This is part of a wider wave of privacy coins being pushed off centralised exchanges ahead of MiCA and similar rules, and it isn't unique to us, but it changes what business development has to focus on.
My job this term is to make sure PIVX stays tradeable, liquid and usable without depending on any single big exchange. I also have a focus on our existing partners and to work alongside @WizardWam and @Liquid369 in doing so. and other tasks such as:
- Stabilise our core exchange (MEXC). Get deposits and trading fully restored and make MEXC our primary venue, with constant market-maker liquidity.
- Consolidate, don't spread thin. Pause or exit weak markets that cost us money and reputation, and only reopen them with proper market making in place.
- Build real use cases. Merchant integrations, privacy identity, AI-agent payments and non-custodial swap routes, so demand for PIVX doesn't depend on CEX listings.
- Find new partners in the privacy-friendly and no-KYC space that are less exposed to the delisting wave.
Accomplishments / tasks these past 3 months:
Exchanges & liquidity
- MEXC: Working directly with MEXC to re-enable PIVX deposits and trading. The suspension also broke partner services that source liquidity from MEXC (ChangeNOW, Changelly, Travala), so restoring it wasmy top priority. Once it came back, MEXC becomes our main exchange with continuous MM support.
- XT: Paused PIVX trading on XT until a new market-making arrangement is in place. A thin, unmanaged order book does more harm than good, so we'll only reopen when liquidity can be properly supported.
- LBank: Chose to exit LBank instead of leaving a paused market in limbo, as part of consolidating liquidity into exchanges that users actually trade on.
- Binance: Managed communication with Binance through the Monitoring Tag period and the delisting. Made sure the community had the timelines for trading end (17 Aug), deposits (18 Aug) and the withdrawal window (until 17 Oct).
- Gate.io: Handled the delisting and user communication.
- Ongoing coordination with our market makers on spread, depth and reporting.
Use cases & partners
- Mask.ID: Supporting Mask.ID, a PIVX-based privacy identity platform, with its first live integration on masternodes.space. This is a direct new use case for PIVX.
- Continued work on wallet integrations: Coinomi Shield support [In Testing] and Edge Shield support [In development].
- Exolix partnership and swap widget [STATUS]
Focus for the next 3 cycles:
- Focused on liquidity management with Enflux
- XT decision: secure a new market-making arrangement and reopen.
- New exchange and partner pipeline: target venues and swap services that are friendly to privacy coins (instant-swap providers, non-custodial/DEX routes such as BasicSwap and Houdini-style aggregators, and regional exchanges outside the strictest MiCA scope).
- Merchant and use-case growth: more Mask.ID merchant integrations, payment-processor and merchant onboarding, which give us real announcements to share.
- Wallet coverage: finish Shield support in Coinomi and Edge so users have more self-custody options as CEX access shrinks.
- Transparency: monthly BD update on the forum covering exchange status, MM performance, the partner pipeline and what's been closed.
- New listing New listing on SafeTrade in discussion.
My tasks / responsibilities: (same as prior proposal)
- Submit proposals as an intermediary between organisations and the PIVX DAO.
- Represent PIVX officially by being KYC compliant with exchanges and organisations that require it.
- Identify and pursue business partnerships that benefit PIVX and the community.
- Facilitate communication between businesses and the community, so that partnership and listing decisions stay community decisions.
- Take part in online events that promote PIVX, including events where partners request PIVX representation.
- Run continuous competitor analysis and track the market, especially the regulatory and delisting landscape for privacy coins, to find ways to differentiate and improve.
- Manage our relationships with partners and exchanges (my most important responsibility).
- Get PIVX listed on additional exchanges, opening separate proposals for exchange fees where applicable.
- Identify marketing campaigns with our alliances and partners to introduce PIVX to a larger audience.
- Build PIVX outside the PIVX community.
- Research and maintain relationships with market makers to secure listings and bring the liquidity we need.
Funding:
For this round I'm asking for 45 000 PIVX per cycle for 3 cycles, 135 000 PIVX in total. This funds my position as a full-time staff member and Lead of Business Development. The amount is the same as last term, and I'll review it again after 3 cycles.
I will not be asking for the 50 PIV submission and processing fees to be reimbursed.
Thank you all for your continued trust and support, especially through a tough period. PIVX has survived market cycles before, and I'm committed to making sure we come out of this one stronger.
Contact me:
Have an idea for growing PIVX or want to collaborate? Contact me any of these ways:
Telegram - @guapic
Email - [email protected]
Discord - guapic
Or simply reply here in the forum
Voting Details:
To vote YES for this proposal:
Code:
mnbudgetvote many f824eca454e892c9c591c73a261ecca2e9121ebc2d4671d5866efb3a79647153 yes
Code:
mnbudgetvote many f824eca454e892c9c591c73a261ecca2e9121ebc2d4671d5866efb3a79647153] no