Active Q1Liquid369-26

[Liquid369]

Name: Q1Liquid369
Term: 3 Cycle
Cycle Amnt: 40,000
Total Amnt: 120,000
Author: Liquid369
Receiver: Liquid369
Address: DPT2VhFFst1oXZExahEy4ATkZAgMg7uD7q
Created: 02-18-2026
Status: Active
Vote Hash: a8c8127ce55ffcce40fb18adc625ed6b715f1fd0c2a1ba330531a7ac8d889239

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. Proposal ask has been upped a little bit to adjust for price during a trying time to make it.

Last Cycle Report

• 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.
  • ElectrumX is more stable and has deployed an updated ElectrumX that supports Sapling/Shielded Data so we can sync Sapling through ElectrumX services. https://github.com/Liquid369/electrumx-1
  • BasicSwap has been running through these for the last ~2 months and looks also more stable
• 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
  • We have identified some ways to work with Ambassadors and Marketing to grow our strategy. This will be outlined more in depth below and discussed in the upcoming TownHall with the Ambassadors. I will try to spearhead the initiative until everyone gets into the workflow.
• 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)
  • Reviewed about ~15 applicants majority were still scammers or people who want to try and then just disappear. I still think the colleges would be a better spot, more campuses are starting "Blockchain Clubs," and we can move into this initiative.
• Finishing Integrations with Partners
  • Edge needs some more work for shielded support
  • Edge has stalled a bit with the work after the deployment of the backend for them. I will push more soon, but I have been pushing other items while doing this.
  • Cardstorm payment API needs completion and testing for use with their system
  • Payment API is in testing; they need to deploy and get approval to move forward.
  • Coinomi will need help with integrating Shield Support
  • Coinomi is on a full workload with its development team; this is put on hold for now.
  • Integrating PIVX Explorer into MPW backend slowly and testing it for replacing Blockbook
  • PIVX Explorer is now capable of syncing MPW. The API is functional, and I have conducted extensive bug and balance testing across multiple addresses and xpubs. We will need to renew servers soon so they can be deployed for more usage and actually take over the backend capabilities. Frontend work is ongoing with @YuurinBee (Main), assisting where he can with input and changes for styling and design. Analytics will be a work in progress, but the MVP is finally almost here.
  • Published the PIVX-RPC-RS Crate to Crates.io so it can be utilized widely by those wanting to develop in Rust and communicate to the PIVX RPC.
  • Cake wallet is also being tested for PIVX Integration now. I have done the work personally, where it syncs and can receive and show Shielded balances. Need to expand efforts into sending Shielded PIV because this requires more device testing and the download of the PIVX Params files onto Mobile Devices. This integration utilizes the ElectrumX Sapling fork I mentioned above.

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.
Deployed, found some bugs related to invoices and prices, juggling everything, this is on hold, will have some assistance from Labs to push through more thorough testing and get across the finish line.


Upcoming Cycle Plans

• Continued work on the PIVX Explorer and Frontend fixes so that we can prepare for an Official Release.
• Continued BTCPay testing and making stores to validate payments
• @LeacyMcK is only able to handle so much, and with the introduction of the Ambassador program, we are going to pivot with a workflow of the Ambassadors to support the PIVX socials more by targeting the algorithm that has recently been released: https://github.com/xai-org/x-algorithm. We now have a small army ready to attack on social media but now we just need a concentrated effort. No more of 20 individuals yelling into a void, but 20 individuals yelling together to grow that reach. Alongside more planning in responses and slow rolling some posts/replies to continue them living longer in the feed for others. This will then expand onto other socials once the flow and direction everyone is trained and comfortable with. Afterwards we have discussed ways for maximizing the Ambassadors IRL Events.

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:

mnbudgetvote many a8c8127ce55ffcce40fb18adc625ed6b715f1fd0c2a1ba330531a7ac8d889239 yes

mnbudgetvote many a8c8127ce55ffcce40fb18adc625ed6b715f1fd0c2a1ba330531a7ac8d889239 no

Please cast your vote to keep PIVX development moving forward!