What's new
  • Due to abuse, self-registration is disabled.

    Registration is only required for posting topics or replies. To register, make a request on any of the PIVX social media or chat channels.

    NOTE: To enhance forum security, new accounts that have no posts within a 30-day period are subject to being deleted.

Active Q3Liquid369

Liquid369

Administrator
Code:
Name: Q3Liquid369
Term: 3 Cycle
Cycle Amnt: 33,000
Total Amnt: 96,000
Author: Liquid369
Receiver: Liquid369
Address: DLXqCcUhUibrdaK2Ku3hmQjtRr3TiJQWYz
Created: 08‑18‑2025
Status: Active
Vote Hash: 64b2fbb9b0ac986381388b05cc9f299b4e0f0af8f18f765cfde2423574a3da12

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
  • Wallet Integrations
    • Working in collaboration slowly with Luke on the BTCPay ZCash Plugin Fork for PIVX.
  • Exchange & Network Support
    • Helped exchanges recover from an explorer-related outage.
  • Ecosystem & Events
    • Multiple partner meetings across the Casper, Cosmos, and Solana ecosystems - ZCash is winning as the premier Privacy option here. We need to work on our pitching of Proof of Stake > Proof of Work and the similar privacy. We can get some good points here if we can break into it.
    • Managed conference fund allocations for 2025
    • Hosted two AMA with Coinomi and SwapZone
  • Explorer & Services
    • Reviewed MPW PR's for Shield Sync and Masternode improvements
    • Upgraded Electrumx for better handling and restarting, had a few outages from some edge cases.
    • Ansbile playbook near complete for managing testnet infrastructure
  • New Dev Recruitment
    • Interviewed candidates—a few panned out. Solana dev event was alright, but many have jobs or are innovating, looking to do more events with Merch and Business cards for landing with people more. Privacy is the next wave we can maybe get their focus.

Upcoming Cycle Plans
  • 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
    • Need to remove testnet5 from code and submit a testnet6 PR
  • MPW → Core Wallet
    • Continued frontend reviewing for MPW and Multi-MN.
  • Infrastructure & Analytics
    • Continue evaluating and improving the ElectrumX servers; they need some care for upgrades, updates, and more stability on restart.
  • 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)

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 64b2fbb9b0ac986381388b05cc9f299b4e0f0af8f18f765cfde2423574a3da12 yes

Code:
mnbudgetvote many 64b2fbb9b0ac986381388b05cc9f299b4e0f0af8f18f765cfde2423574a3da12 no


Please cast your vote to keep PIVX development moving forward!

New format! Let me know what you guys think.
 
Last edited:
Any time frames on 6.0, getting test net setup etc? Have we got a road map for everything?
I was in the process of moving last month, so we have secured all funds. I plan to start purchasing servers this week and next as supply becomes available from the locations listed in the testnet funds proposal.
I have started the structural design for a devops pipeline for it, and we have to start putting it all together. Duddino was also out last month for some time, so we are getting all back up to speed this month.
No real need for a roadmap for the setup of the testnet, I have to provision the servers and then configure multiples of each node type IPv4, IPv6, Tor. We will be running various stress testing and up and down scenarios for the liveliness of the network with the multiple quorums we plan to have running. I have a log pipeline im working on for easy log reading for everyone. Lastly, I will submit a PR for removing our old "testnet5" in PIVX Core for a new "testnet6" this will be in preparation for staging everything moving forward and hopefully this will run for awhile.
 
Top