Code:
Name: Liquid369-Aug-Oct24
Term: 3 Cycle
Cycle Amnt: 30,000
Total Amnt: 90,000
Author: Liquid369
Receiver: Liquid369
Address: D66LAo1cQmKJ3JoqeuSRrTL6hycLx7kKso
Created: 08-13-2024
Status: Active
Vote Hash: 55f737cb493bb1db985dcd74ee18799ad17b95ec8b51a53858d138c863098f06Liquid369 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
- Mempool updates from upstream for enhancing our services and better 'pending transaction' handling
Postponed while there are methods to code around this that were discovered
- Setting up plans with marketing and development on 6.0 testnet for the end of summer (tentatively)
Plans have started, we need to move code forward for testnet, and then we can advertise testnet and potentially apply for some incentives for users joining and finding issues. The goal in testnet is for a large amount of participation for adequately testing our changes to DMN and making sure it will be secure for the users, for example, we may want 150 MN, with 50 ipv4, 50 ipv6, and 50 tor. For this, we must work on getting more users or there could be more costs for us to purchase enough servers. Tor we can run multiple nodes per server, but ipv4/6 is what's most needed.
- Organizing infrastructure for testnet
We will need some budget for servers which we will explore costs and the idea is a minimal transition but for more masternode testing by the team. Incentivizing users will cut our costs and management of the infrastructure.
- Working with Business Development on integrations for some more use cases
Assisted in the following integrations for Exchange listings with Bitmart, Bitstorage, Koinbx, Xeggex, XT, Changelly, MEXC. I am also assisting with liquidity management with our Market Makers for better accessibility for PIVX.
- Organizing newcomers in the PIVX team and expanding Project Management
We have had several interested parties trying their hand at PIVX Core, but some are still working on their basics or ideas and familiarizing themselves with the codebase. There is not much to say here outside of when there is more to update we will have for new team members. We have started with marketing an idea of a referral bonus for users who help refer people to PIVX to work and will potentially get a payout for them working X amount of time minimum. Some polls are being posted on the official X account regarding what people would like to see as a referral bonus. After this cycle, we will implement due to the budget being needed for market-making this upcoming cycle(s).
- Establishing various team meetings for growth, participation, community, and progression of each team
In terms of bridging the gap between teams that worked more in isolation as we were smaller and dedicated, now as it grows we need to keep up with each other more and it helps to move ideas forward when more are aware. Scheduling meetings is difficult with a decentralized group as everyone is scattered across timezones, so the current proposal is meeting with groups in each timezone and then having meeting notes for the next timezone to update so on and so forth. If all team members' schedules permit we will be doing bi-weekly ish meetings for development, marketing, business development, open lobby voice chats for community updates, and lastly Core <> Labs coordination. This has been determined as a good model go-between from having few to no meetings to needing to have some to keep organization and cohesiveness. We shall see more in the upcoming month as we plan out the next meetings.
- Researching and implementing WebSockets into RustyBlox as MPW is now looking into more WebSocket usage to speed up sync
In development but on pause with some web socket work issues in MPW, I will use the findings there to update and finalize.
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
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:
To vote no:
Last edited:
