Menu
What's new

Archived Core DevOps Fuzz (Jul-Sep 2023)

fuzzbawls

fuzzbawls

Core Developer
Staff member
Code: 
Title: Core DevOps Fuzz (Jul-Sep 2023)
Name: CoreDevOps-Fuzz-Q323
Term: 3 Cycles
Cycle Amnt: 15000 PIV
Total Amnt: 45000 PIV
Author: Fuzzbawls
Receiver: Fuzzbawls
Address: DBh9o9uRGohcDKpeiEyRiwtmTaTL3xDdev
Created: 2023-07-12
Status: Active
Vote Hash: 3f403babe435fae3ee593370e090b2a70bb36da01b187026f87d06abfaa71755

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)
  • Rust toolchain maintainer (as of PR #2872, this is no longer in effect currently, but still being watched)
  • 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)
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.

Changes from previous cycle

The last cycle saw considerable effort to support other developer's desire to update the rust zcash library we're using, which required extensive testing of our own rust toolchain version usage. This ultimately led to the decision to forego support for some older but still valid linux distros in the name of pressing onward. As a result of this change, we have ultimately reduced the burden on PIVX devs to maintain a custom Rust toolchain and can now use standard Rust toolchain binaries.

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 3f403babe435fae3ee593370e090b2a70bb36da01b187026f87d06abfaa71755 yes

To vote no:
mnbudgetvote many 3f403babe435fae3ee593370e090b2a70bb36da01b187026f87d06abfaa71755 no
 
Last edited:
You must log in or register to reply here.
Top