Active Core DevOps Fuzz (Q4 2024)

[fuzzbawls]

Title: Core DevOps Fuzz (Q4 2024)
Name: CoreDevOps-Fuzz-Q424
Term: 3 Cycles
Cycle Amnt: 15000 PIV
Total Amnt: 45000 PIV
Author: Fuzzbawls
Receiver: Fuzzbawls
Address: DBh9o9uRGohcDKpeiEyRiwtmTaTL3xDdev
Created: 2024-10-14
Status: Active
Vote Hash: 35165c0165bc05a9ff4a69fa0ef138e2534ea2febda779ad381b5c688ef3a469

Abstract

This document outlines the funding and responsibilities for myself as a PIVX Core Dev and one of the maintainers of the PIVX-Project GitHub organization.

Responsibilities

As a Core Dev, my responsibilities include the following:

• Review and test code submissions (PRs) for viability, accuracy, and compliance with our code standards
• Research and develop code improvements (my particular area-of-focus revolves around build systems
• Research and backport upstream improvements
• Provide timely gitian sigs for releases, release candidates, and test releases
• Assist in support team and exchange troubleshooting

Additionally, my own responsibilities that I have been undertaking include the following:

• Primary maintainer of the gitian.sigs and pivx-detached-sigs repositories
• macOS code signing for all macOS desktop software releases (PIVX-Core, SPMT, PET4L)
• macOS 11+ (Apple Silicon) build and deployment compatibility (ongoing project)
• Ubuntu PPA maintainer, ensuring that new release versions are pushed and that nightly builds are properly built (https://launchpad.net/~pivx)
• Maintainer of BerkeleyDB v4 Ubuntu PPA
• Chiabls 3rd party library build system integration and maintenance (https://github.com/PIVX-Project/bls-signatures)
• Snapcraft maintainer (nightly and release versions) (https://snapcraft.io/pivx-core)
• Run and maintain four (4) DNS seeders (2 for testnet, 2 for mainnet)
• Monitor and maintain budget finalization (whilst paying to finalize) cycles.
• Track network/protocol upgrades and provide visual stats when necessary (https://seeder.fuzzbawls.pw/pivx/network)
• Maintain the Doxygen developer documentation (updated nightly when needed) (https://www.fuzzbawls.pw/pivx/doxygen/)
• Maintain the code coverage report (updated nightly when needed) (https://www.fuzzbawls.pw/pivx/regression-test-coverage/)
• Coordinate and provide tracking (including historical data) for exchange/service update responsiveness
• Transifex (core wallet translation) management and integration (https://app.transifex.com/pivx-project)
• Build systems compliance and maintenance for multiple host OSes and toolchains
• Maintain three (3) SPMT public RPC endpoint nodes
• Maintain a testnet blockbook explorer (https://testnet.fuzzbawls.pw/)
• Six (6) dedicated testnet MN nodes to ensure testnet always has the minimum number of MNs required
• Two (2) dedicated testnet staking nodes to ensure testnet's chain continues moving at all times
• Github org management (teams, permissions, repository rules)
• PIVX Forum Proposal moderation (ensuring that proposal posts are prefixed/moved according to their on-network status)
• Supporting other PIVX teams in areas where GitHub is involved (website, docs, etc)

A newer area I've been working on while other devs have either been away or focused elsewhere, has been research into expanding PIVX's use in the charity field. I cannot give specifics yet though.

Funding

The funding I am asking for to cover the continued duties and responsibilities listed above is 15000 PIV per cycle. The above lists are extensive in nature, but not exhaustive, and minor or nuanced tasks may not be listed. DevOps covers a rather broad range of tasks that, if done well, should really not be noticeable from an outside perspective.

Donations and Receiving of Additional Funds

Any funds received by the proposal payout address from any source other than the PIVX network’s in-built budget distribution system will be considered as donations.

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 35165c0165bc05a9ff4a69fa0ef138e2534ea2febda779ad381b5c688ef3a469 yes

To vote no:
mnbudgetvote many 35165c0165bc05a9ff4a69fa0ef138e2534ea2febda779ad381b5c688ef3a469 no

 

[Eric_Stanek]

Clearly there is an 'unknown whale' that has thrown a lot of NO votes at this proposal.
This message is for that Unknown Whale.

It is of course totally cool for you to remain unknown. It is also OK for you to vote as you see fit. However, given the level of detail that @fuzzbawls has provided, how critical his contributions are, and the fact the current dev team highly values his skills and efforts, it is really confusing as to WHY you would vote down the proposal. Frankly, a lot of what Fuzzbawls does, keeps the Dev Team organized and following well established best practices, that protect the Developers, and the PIVX brand, from any major mistakes that could hurt us all. Further, the timing couldn't be worse as we have at least 2 C++ devs returning to work on getting v6.0 Core wallet released.

If you've got constructive criticisms to add, please feel free to use an anonymous account here to communicate. Without your feedback, it is impossible to correct for it, and nothing will change. Once you communicate your issues, then they can be resolved; either by providing clarification you need to better understand the value of the proposal, or by Fuzzbawls making changes.

Thanks.

 

[SiggeB]

To all masternode owners:

As masternode holders, we all have the right to vote as we see fit. However, I urge each of you to take a step back and reflect on the broader implications of your vote, particularly when it comes to this crucial proposal. This isn't just a routine funding request. It comes from our lead developer, whose ongoing work is critical to the continued success and growth of PIVX.

The responsibilities outlined in this proposal cover essential tasks that keep PIVX running smoothly. The rejection of this proposal would not just delay these important functions. It could have severe consequences for the community as a whole.

To the whales, in particular: with great power comes great responsibility. Your influence in a project like PIVX is enormous, and it has the potential to shape PIVX's future in profound ways. Voting with your masternodes should not be about personal feelings or past grievances. This is about the future of PIVX and the collective success we are all striving for. Every vote you cast has a ripple effect across the entire ecosystem.

I ask all of you, and especially the whales, to put aside personal biases and consider the greater good of PIVX. Our strength lies in our shared goals and hopes for PIVX. Ego or individual concerns should never stand in the way of PIVX's progress.

For the good of PIVX and its future, I encourage you to vote with a deep thought about what's best for PIVX's future, and with mature responsibility.