Active Liquid369-Nov-Jan25

[Liquid369]

Name: Liquid369-Nov-Jan25
Term: 3 Cycle
Cycle Amnt: 30,000
Total Amnt: 90,000
Author: Liquid369
Receiver: Liquid369
Address: DS22VkCcwGyaLXkTS9ci9cCLkmWzhAf5yJ
Created: 11-11-2024
Status: Active
Vote Hash: 6012d1b002af8921c160ceea79468cb1835259479762dc688b10cfa834ea7d6a

Liquid369 Proposal

This proposal is outlining what has been done as an update to users and what will be continued in the next portions. It outlines some ideas for users and the responsibilities entailed overall.

Last Proposal Report

Updating PIVX PET4L Application:

[GUI][DB] Allow Custom Explorers by Liquid369 · Pull Request #20 · PIVX-Project/PET4L

This pull requests adds to the GUI a dropdown menu for explorer selection and allows for custom URL's. We have updated the two hardcoded ones with https://explorer.duddino.com and https://testn...

github.com

Update PET4L to Python 3.10 by Liquid369 · Pull Request #22 · PIVX-Project/PET4L

Here is a PR similar to the SPMT update to Python 3.10 Excluding build adjustments which is in PR #21

github.com

These are submitted and maybe a few more adjustments before merging but allows for custom explorers to help users with issues that have cropped up recently in support with many unable to use PET4L at times. The other is to update the Python standard like what was done last cycle with PIVX-SPMT.
- Updates have been ongoing for these two above pull requests, we should be finishing them within the next week or so and releasing the new updates if the last tests go as planned.

[RPC][Backport] JSON-RPC 2.0 when Client requests by Liquid369 · Pull Request #2937 · PIVX-Project/PIVX

PIVX Core is currently working with a mix of 1.0, 1.1 and 2.0 behaviors for the JSON RPC server. @Duddino was having issues with a rust json rpc library interfacing with our daemon because of the r...

github.com

- Backported JSON-RPC update for MPW needs to help move along more functionality and updates to standards.

Ledger Progress
- We have become more known to the Ledger group. I have been working with various individuals in their chain to talk us up before working on getting Jeffery and me face-to-face with the Ledger CEO. We have contacts to get directly to them, but I am working on getting a soft handoff rather than us just barging in and cold emailing.

6.0 DMN's
- We are progressing now with the other developers back. A few updates have been identified from the time being and some older ones that were missed to bring proper performance and stability to the new masternode system. I have prepped some testnet servers for testing when we are ready to move to testnet these changes we have identified. Creating ansible scripts for quick deployment across the nodes within my control. Working on reviewing and adding in those identified needs for DMN. From this point forward we are not going to push too much else into 6.0, we need to focus on stability and finally deliver the new masternode system. With the current market space, we want to start introducing things slowly while MPW consistently breaks pace to become on par 1 to 1. Advancements will gain us traction but stability is first and foremost right now to capitalize on the bull market.

RustyBlox:
- I have started some basic Vue layouts, but it is difficult to use our current Web team for Vue projects, as it is not their favorite to work with but the scale of this project makes more sense to work in Vue over some plain bootstrap system. This will take some time and will look into getting its design in line with the branding on PIVX. Will be outsourcing some web devs to improve upon the base work I will be doing at this point.

Everything reported here will be continued during this upcoming cycle.

Responsibilities:

- Maintaining PIVX Core and Repositories under PIVX-Project organization
- Coordinating between Core and Labs
- Reviewing and testing code submissions in both Core and Labs (organization rules is 2 approvals and reviews needed for anything to be merged from non-authors)
- Research and improve current code for optimizations
- Research and improve backports for our perpetual updating to BTC Core
- Maintain networking infrastructure and build some analytics
- Maintain explorer servers
- Supporting Community/Exchanges/Services/DEX all in technical regards for PIVX
- Coordinating with Marketing to bring accurate technical representations and promotions for PIVX development
- Maintaining regtest network servers for testing and infrastructure for others to use in testing new features
- Maintaining testnet network servers for testing and infrastructure for wider community testing features and new implementations
- Making overall PIVX Project development updates
- Maintaining ElectrumX servers for DEX's
- Coordinating with Business Development to ensure smooth and timely listings to evaluate markets for optimal liquidity for PIVX health and market retention
- Assisting market makers alongside jeffrey with inventory verification, management as well as decision making
- Assisting exchanges and integrations with technical information, rpc integration and more to ensure proper integration of PIVX into their platform
- Vetting potential new members for development

Voting

Qt GUI wallet users can use the built-in DAO page to cast their votes.

For console users, use one of the below commands.

To vote yes:

mnbudgetvote many 6012d1b002af8921c160ceea79468cb1835259479762dc688b10cfa834ea7d6a yes

To vote no:

mnbudgetvote many 6012d1b002af8921c160ceea79468cb1835259479762dc688b10cfa834ea7d6a no