Proposal “kwvg-core-dev-apr25“ (Active)Back

Title:Funding kwvg for Core development (Apr 25)
Owner:kwvg
One-time payment: 200 DASH (3989 USD)
Completed payments: no payments occurred yet (1 month remaining)
Payment start/end: 2025-04-08 / 2025-05-08 (added on 2025-03-25)
Final voting deadline: in 1 month
Votes: 218 Yes / 15 No / 0 Abstain
Will be funded: No. This proposal needs additional 124 Yes votes to become funded.
Manually vote on this proposal (DashCore - Tools - Debugconsole):
gobject vote-many b27e64bc45d4aa3d338d1b1c3452457860e16270c013c2b2e4538fb284f0fa46 funding yes

Please login or create a new DashCentral account for comfortable one button voting!

Proposal description

Disclaimer: This proposal is individual in nature and is not brought forward by Dash Core Group

I'm Kittywhiskers Van Gogh (kwvg on GitHub, kittywhiskers on Keybase), I've been contributing to Dash Core since Dec, 2020 (my first pull request!), contributed through the Dash Incubator program since Jan, 2021 (pull requestIncubator claim) before transitioning to a role within Dash Core Group effective Apr, 2022.

Since then, except for a brief periods, I have contributed to Dash Core in full-time capacity for 4 years.

What do I do?

I filled the role of C++ Software Engineer in the Core team. My responsibility was, beyond routine backports, implementing features needed in Dash Core sooner than sequential backports would allow.

This proposal seems familiar...

Because it is.

My last proposal (source) requested funding to continue my work for three months, which was graciously granted by the community for the funding cycles of Nov, 2024 to Jan, 2025, which went towards funding development between Dec, 2024 and Feb, 2025.

What have I done since last time?

Contributed 43 merged pull requests between Dec 6th, 2024 and Feb 28th, 2025 (source) totaling ~300 commits[1]. This is not an exhaustive list and does not include related contributions made by my peers and coworkers without whom, some of these wouldn't be possible.

  • Assume UTXO support (work in progress)
    • #6443 (refactor: move CConnman and PeerManager out of CDeterministicMNManager, LLMQContext member ctors)
    • #6304 (backport: merge bitcoin#23280)
    • #6504 (refactor: remove llmq::chainLocksHandler, llmq::quorum{InstantSend,Snapshot}Manager, move to LLMQContext)
  • Implementation of BIP-324/P2Pv2 (complete)
    • #6488 (backport: merge bitcoin#27452, #29347, #29356, #29353, #29452, #29483, #30545, #31383)
  • Migrating to C++20 (complete)
    • #6516 (backport: merge bitcoin#24866, #25612, #28432, #28757, #28845, #28932, #28973, #21778, #30204, #29765, #30201, #30287, #30511)
    • #6389[2] (backport: merge bitcoin#23060, #24164, #23565, #24337, #27682, #29208, #29091, #29165, #29934, #30261, partial bitcoin#27662, #28210, #28348, #30263)
    • #6564 (ci: update containers and CI to use Ubuntu 24.04 LTS (noble), merge bitcoin#29985)
    • #6380 (backport: merge bitcoin#24460, #27672, #27766, #28065, #30228, partial bitcoin#28349, #28579)
    • #6378 (backport: merge bitcoin#24989, #26135, #26150, #26159, #26489, #26825, #28127, #29275, #29263, partial bitcoin#27790, #27978)
  • Improving CI coverage (work in progress)
    • #6490 (ci: container improvements)
    • #6491 (ci: merge bitcoin#27314, #28954, fix multiprocess builds)
    • #6400 (ci: refactor GitHub Actions CI to use reusable workflows, respect DEP_OPTS, build multiprocess depends with Clang)
    • #6387[2] (ci: use GCC 14 for building nowallet source and depends, GCC 11 for building sqlite source)
    • #6421 (ci: merge bitcoin#30451, add macOS builds to GitHub Actions, refactor cache keys)
    • #6583 (ci: run functional tests on GitHub Actions, upload functional test logs as artifacts)
    • #6604 (ci: extract "slim" container to run functional tests and add multiprocess and tsan, drop unneeded packages)
And here are some contributions that fall outside task-oriented contributions.

  • Bugfixes
    • #6465 (fix: avoid potential divide-by-zero in network hashrate stats calculation)
    • #6471 (fix: don't shrink window when setting minimum width)
    • #6540 (fix(qt): Fix overlapping directory lock attempts when restarting Dash Qt)
  • Non-trivial backports
    • #6517 (backport: merge bitcoin#25497, #17331, #22155)
    • #6529 (backport: merge bitcoin#22008, #22686, #22742, #19101, #22183, #22009, #22938, #23288, #24592)
Why am I asking?

Due to external factors, current DCG funding would be insufficient to allow retaining me as a contractor. This proposal will allow me to continue my work in the Core Dev Team, retaining my reporting structure and maintaining work output.

How much am I asking for?

200 DASH per month for the duration of the proposal period. This is an increase of 40 DASH from the previous proposal (160 DASH) and represents my full compensation rate. The reduction in the prior proposal was due to the late submission of that proposal, in contrast to this proposal, which is being made earlier.

The amount disbursed will be paid to DCG's compensation fund for conversion and payment to me and shall be treated as proposal income and compensation expense for DCG.

Verification

The below message can be verified using Keybase (source)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

https://www.dashcentral.org/p/kwvg-core-dev-apr25
-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQSWkYeo50/kCopIBnQwzQwGXlxKrQUCZ9AwzQAKCRAwzQwGXlxK
rTapAP9gbFYLFlJ30XE5luYed25NstZZ+ogIHnTJ8WJipczf2wD+Ou6ls9muc3jR
XzGo+EKE9ENC2ZgCPtAqOYMt+XzHwwo=
=CGRa
-----END PGP SIGNATURE-----

Notes

[1] - Calculated using 'git shortlog 24dcce97..86cdd244 --summary --numbered --no-merges | grep "Kittywhiskers Van Gogh"', rounding down to nearest 100
[2] - These pull requests were also mentioned in the prior funding proposal but were merged between Dec, 2024 to Feb, 2025 and therefore included here.

Show full description ...

Discussion: Should we fund this proposal?

Submit comment