Code:
Name: Q4Liquid369
Term: 3 Cycle
Cycle Amnt: 33,000
Total Amnt: 96,000
Author: Liquid369
Receiver: Liquid369
Address:
Created: 11-15‑2025
Status: Pending
Vote Hash:
Liquid369 Proposal Update
This report summarizes what we’ve accomplished since the last cycle, and what we’ll continue over the remainder of the term. Our focus remains on finalizing 6.0, expanding PIVX’s visibility, and laying the groundwork for MPW → PIVX Core wallet integration to streamline onboarding.
Last Cycle Report
- 6.0 Testnet
- As the testnet funds proposal is now complete, we will buy some long-term servers to set up the ideal testnet for us for testing DMNs in various up and down quorum scenarios - Testnet servers are prepared
- Need to remove testnet5 from code and submit a testnet6 PR - Have to still submit for everyone
- MPW → Core Wallet
- Continued frontend reviewing for MPW and Multi-MN. - Some reviewing has slowed down due to events and the scheduling of other work
- Infrastructure & Analytics
- Continue evaluating and improving the ElectrumX servers; they need some care for upgrades, updates, and more stability on restart. - Deployed an advanced script for monitoring and restarting ElectrumX so our DEX can stay online better. We need to restructure who hosts all the servers, as it is quite a few people currently.
- Community & BizDev
- Support new exchanges/integrations with RPC, docs, and technical liaison - Working with various groups for integrations currently, such as Coinomi, Edge, needing some fixes for Shielding, and Cardstorm with a better payment API.
- Coordinate with marketing on events and campus outreach
- Continue AMAs, workshops, and hackathon sponsorships - Several AMA's completed with NOWNodes, SWAPZone, and another I can remember right now lol.
- Recruitment & Mentorship
- Onboarding new contributors continues, and many seem to fall off quickly. Thoughts: College recruiting? Would we want to invest in this?
- Mentoring Ambassadors for the NAP (New Ambassador Program)
Private Repository is deployed for now with BTCPay for testing zcash/PIVX plugin. I have to deploy a test instance this coming month and make sure it's all bug-free, and then we have a new payment processor.
Remove PING Function from PET4L
https://github.com/PIVX-Project/PET4L/pull/28
Deploying More Infra to SPMT/PET4L
https://github.com/PIVX-Project/PIVX-NGINX-Proxy
Deployed a test instance of the upgraded blockbook for Edge:
Upcoming Cycle Plans
- MPW → Core Wallet
- Continued frontend reviewing for MPW and Multi-MN.
- Infrastructure & Analytics
- New scripts deployed need to give them time to evaluate functionality, and if helpful and what's next steps.
- Community & BizDev
- Support new exchanges/integrations with RPC, docs, and technical liaison
- Coordinate with marketing on events and campus outreach
- Continue AMAs, workshops, and hackathon sponsorships
- Recruitment & Mentorship
- Onboarding new contributors continues, and many seem to fall off quickly. Thoughts: College recruiting? Would we want to invest in this?
- Mentoring Ambassadors for the NAP (New Ambassador Program)
- Finishing Integrations with Partners
- Edge needs some more work for shielded support
- Cardstorm payment API needs completion and testing for use with their system
- Coinomi will need help with integrating Shield Support
- Integrating PIVX Explorer into MPW backend slowly and testing it for replacing Blockbook
Responsibilities (ongoing)
- Maintain PIVX Core code & repo hygiene
- Coordinate Core ↔ Labs development
- Review, test & QA all PRs (2 approvals required)
- Optimize code & backport BTC Core updates
- Operate explorer, ElectrumX, regtest & testnet servers
- Provide infra support for DEXs, community tools, analytics
- Liaise with exchanges, wallets & market‑makers
- Drive developer recruitment, events & campus outreach
Voting
GUI Wallet: DAO page → vote “yes” on
Console:
Code:
mnbudgetvote many yes
Code:
mnbudgetvote many no
Please cast your vote to keep PIVX development moving forward!