
Proposal “kwvg-core-dev-jul25“ (Active)Back
Title: | Funding kwvg for Core development (Jul 25 - Sep 25) |
Owner: | kwvg |
Monthly amount: | 175 DASH (4250 USD) |
Completed payments: | 2 totaling in 350 DASH (1 month remaining) |
Payment start/end: | 2025-07-08 / 2025-10-05 (added on 2025-07-05) |
Votes: | 530 Yes / 43 No / 19 Abstain |
Will be funded: | Yes |
Manually vote on this proposal (DashCore - Tools - Debugconsole): gobject vote-many 4e7b42b60c86356a2fc075fd8e997a72fbce7b45c6ef935bab67300187393e32 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 request, Incubator 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. Below are my past proposals.
What have I done since last time?[1]
Contributed 29 merged pull requests between Apr 1st, 2025 and Jul 5th, 2025 (source) totaling ~250 commits[2].
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?
175 DASH per month for the duration of the proposal period. 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.
The currently proposed amount is a reduction of the standard compensation by 25 DASH in recognition of market conditions and budget contention.
Verification
The below message can be verified using Keybase (source)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
https://www.dashcentral.org/p/kwvg-core-dev-jul25
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQSWkYeo50/kCopIBnQwzQwGXlxKrQUCaGlauwAKCRAwzQwGXlxK
rQAHAP0ZPZb9fzx/mHkaPI88o2NHipqZ3uCAjcigJs9wfZHJMwD+PDZKTaIG1uyg
TseRBiOl/bim1/kHSuKaaGhAU9DXSgY=
=LY7S
-----END PGP SIGNATURE-----
Notes
[1] - Unlike the last three proposals, which are monthly, this is a quarterly proposal. The provided statistics count from the start of Q2 CY2025 to the proposal date.
[2] - Calculated using 'git shortlog 1e062a665..094ceb99f --summary --numbered --no-merges | grep "Kittywhiskers Van Gogh"', rounding down to nearest 10.
[3] - Not merged as of Jul 5th, 2025, included as most work for it was done during Q2 CY2025. It is not counted towards merged pull requests or commit count.
[4] - Not merged as of Jul 5th, 2025, mentioned in previous proposal as prior work was done in Q2 CY2025. It is not counted towards merged pull requests or commit count. #6674 has been omitted from the list despite being mentioned in a previous proposal as it is dependent on #6665 and remains dormant otherwise.
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 request, Incubator 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. Below are my past proposals.
Proposal Name | Funding Period | Work Period |
kwvg-core-dev-nov24 | Nov, 2024 - Jan, 2025 (3 months) | Dec, 2024 - Feb, 2025 (3 months) |
kwvg-core-dev-apr25 | Apr, 2025 (1 month) | Apr, 2025 (1 month) |
kwvg-core-dev-may25 | May, 2025 (1 month) | May, 2025 (1 month) |
kwvg-core-dev-jun25 | Jun, 2025 (1 month) | Jun, 2025 (1 month) |
What have I done since last time?[1]
Contributed 29 merged pull requests between Apr 1st, 2025 and Jul 5th, 2025 (source) totaling ~250 commits[2].
- Extended addresses support
- Preliminary work
- dips#162 (docs: move (platform) network information fields from DIP-00{03, 04, 28} to Appendix C of DIP-0003, minor cleanup)
- #6626 (refactor: reduce references to masternode service, cleanup index code, consolidate ProTx versioning)
- #6636 (refactor: replace CDeterministicMNStateDiff macros with boost::hana)
- #6635 (refactor: reduce ostringstream usage, reduce GetHash() usage)
- #6669 (feat: define BIP 9 fork DEPLOYMENT_V23 for new version featureset)
- #6723 (chore: deprecate protx register{,_fund,_prepare}_legacy and protx update_registrar_legacy, specifying scheme in bls generate)
- Implementation
- #6627 (refactor: section off masternode network information to MnNetInfo, lay groundwork for multiple entries)
- #6629 (feat: introduce type-flexible NetInfoEntry to allow non-CService entries, use in MnNetInfo)
- #6718 (test: consolidate masternode info tracking (MasternodeInfo) in functional tests, implement helpers, add type annotations)
- #6720 (test: implement helper functions for ProTx creation, allow working with assert_raises_rpc_error, add ability to withhold submission to all ProTx creation RPCs)
- #6665[4] (refactor: model interface after MnNetInfo and support switching impls, add new ProTx version)
- Preliminary work
- Backports
- Build/CI
- #6637 (fix: restore --enable-werror coverage, tenatively disable it for Clang and GCC builds)
- #6638 (fix: resolve or sidestep compiler warnings, reenable -Werror builds for Clang)
- #6639 (fix: resolve or sidestep compiler warnings, reenable -Werror builds for GCC)
- #6657 (backport: merge bitcoin#24469, #24470, #29040, #29181, #29085, #29484, #29577, #29081, #29815, #28687, #31502, partial bitcoin#26707, #28894)
- #6659 (ci: cancel prior runs by defining concurrency groups in GitHub Actions, remove unused DOCKER_DRIVER var)
- #6735 (backport: merge bitcoin#24681, #25244, #24291, #25687, #25813, #25852, #26056, #26089, #26086, #26099, #26833, #25974, #27057, #27027, #27118, #27406, #27387, #27696)
- Networking
- Refactors
- Wallet
- #6633 (backport: merge bitcoin#22100, #25148, #22941, #20591, #23596, #22868, #24225)
- #6654 (backport: merge bitcoin#17526, #22928, #22019, #23762, #24067, #24091, #24560, partial bitcoin#17211)
- #6685 (backport: merge bitcoin#23334, #21206, #24196, #24530, #24635, #24502, #24494, #24677, #24602, #24644, #24820, #25507, #25825, #29042, partial bitcoin#23725)
- #6733[3] (backport: merge bitcoin#24711, #24666, #25083, #25005, #25410, #24236, #25438, #25036, #25489, #25544, #25594, #13226, partial bitcoin#25218, #26005)
- Build/CI
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?
175 DASH per month for the duration of the proposal period. 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.
The currently proposed amount is a reduction of the standard compensation by 25 DASH in recognition of market conditions and budget contention.
Verification
The below message can be verified using Keybase (source)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
https://www.dashcentral.org/p/kwvg-core-dev-jul25
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQSWkYeo50/kCopIBnQwzQwGXlxKrQUCaGlauwAKCRAwzQwGXlxK
rQAHAP0ZPZb9fzx/mHkaPI88o2NHipqZ3uCAjcigJs9wfZHJMwD+PDZKTaIG1uyg
TseRBiOl/bim1/kHSuKaaGhAU9DXSgY=
=LY7S
-----END PGP SIGNATURE-----
Notes
[1] - Unlike the last three proposals, which are monthly, this is a quarterly proposal. The provided statistics count from the start of Q2 CY2025 to the proposal date.
[2] - Calculated using 'git shortlog 1e062a665..094ceb99f --summary --numbered --no-merges | grep "Kittywhiskers Van Gogh"', rounding down to nearest 10.
[3] - Not merged as of Jul 5th, 2025, included as most work for it was done during Q2 CY2025. It is not counted towards merged pull requests or commit count.
[4] - Not merged as of Jul 5th, 2025, mentioned in previous proposal as prior work was done in Q2 CY2025. It is not counted towards merged pull requests or commit count. #6674 has been omitted from the list despite being mentioned in a previous proposal as it is dependent on #6665 and remains dormant otherwise.
Show full description ...
Discussion: Should we fund this proposal?
Submit comment
![]() |
No comments so far?
Be the first to start the discussion! |
Xkcd and pasta: DDOS masternode owners that they don't agree with
Joel: hogs funds in both DashBoost and the DAO, while refusing to be accountable for the funds
pmbf: refuses to answer my legitimate concerns regarding their proposal
Rango: spitefully deletes my proposal with no reason, no feedback, just censorship
I'm starting to get the feeling that you guys just *don't want me here*. But why? Why would you all who are supposed to be Dash members, be against the guy who has defended Dash for years?
Its becoming obvious that you are part of a "clique" who's goal is to CORNER THE MARKET on MNs so that YOU WILL CONTROL the network "behind the scenes" while pretending that all is normal.
In other words, you all have validated a post I made 7 years ago: https://www.reddit.com/r/dashpay/comments/ahasrv/the_final_and_strongest_weapon_against_us_will_be/
Conflict of interests is INDEED the weapon that bankers are using to takeover the Dash network and destroy our advantages so that we cannot compete with fiat and other coins.
Thank you for proving this for me.
But you behave like that all of the time !!
And don´t blame Rango for this.
Undermining the authority of the MNO isn´t a funny schoolboy prank, but rather a heinous crime.
You simply don´t have enough Masternodes for your voice having any weight.
Stop acting as if you own 5 or 10 or 20 this is ridiculous.
Who is paying you to make these comments and attack me this way?
Also, I behave like this "all the time" because the enemies of Dash never cease attacking Dash. Defending Dash is a GOOD thing and if you really care about Dash you would THANK ME for my service. The fact that you attack me for it instead is also strong evidence that I am correct and that you are a bad actor, along with Lysergic.
Lysergic hiding behind "having a bad day" is completely inappropriate. I NEVER post this way because I'm "in a foul mood" or "trying to take my anger out on others". I ONLY post this way in order to get BAD ACTORS TO STOP BEHAVING BADLY.
I have been very successful at this, and yet you do not acknowledge or commend my efforts, which means you are likely aligned with the enemies of Dash. How do you respond?
I can blame whomever I see fit for this. Rango has responsibilities to the network as the administrator of this site. You are probably paid by him, or even are him himself, in order to "respond without responding".
You say that "undermining the authortity of the MNO ... is a rather heinous crime", apparently trying to mirror my language in calling DDOSing my masternode a federal crime, WHICH IT IS. It is NOT a crime to "undermine the authority of the MNOs" and anyway I have in no way done any such thing.
You are PROJECTING because YOU ARE NOT A MNO by your own admission and thus have no right to address me in this manner, in this place or even at all! This place is for MNOs to discuss our business, not for paid trolls to attack MNOs because you're BUTTHURT I called your cabal out for your dishonest and bad acting.
Also, you claiming "I don't have enough Masternodes for my voice to have any weight" is completely projection as YOU DON'T HAVE ANY MASTERNODE at all. One masternode is ALL IT TAKES to gain a voice in the network. And since I am undefeatable in argumentation, that means MY VOICE HAS THE MOST WEIGHT OF ALL in the network.
That's why you guys are trying to "force me out through trolling" because, despite your efforts to rig the votes, MY VOICE IS MUCH LOUDER and more effective than yours is, which means you lose power despite your attempts to manipulate things.
STOP POSTING HERE as you don't have a MN and its ridiculous for you to participate in this manner!
And what if I verify my node, and then I sell my node?
Dashcentral admins should always check whether a masternode badge is still valid. But they do not, thats another reason why the whole masternodes badge system of dashcentral is flawed.
Thus I refuse to participate in it.
Its not complicated at all and accomplishes your desire. Are you lazy or what?
>And what if I verify my node, and then I sell my node?
You'll at least have proof that you WERE a MNO, which is better than the crap you're pulling now. Please try to pay attention. Someone who's NEVER had a MN can't do that.
DC admins don't check whether a node is valid because they've likely been captured by the cabal that I've pointed out definitely exists, so this is a way for you to prove that you belong here without exposing yourself to that cabal.
>Thus I refuse to participate in it.
Then you should refuse to comment here as well. Its really that simple and is not complicated.
So the proposal owners should be able to prove the flaws of other proposals, in order for their proposal to be voted.
Thats why proposal owners should be allowed to talk to all proposals.
Not people without a masternode.
Thats my prespective.
You are clearly just trying to abuse the edge cases in order to "force MNOs to take disrespect" so that your comments and the negative results they have will be "our fault".
This is a form of trolling and indicates that you are a bad actor.
Proposal owners are only supposed to speak ON THEIR proposal, not on every other proposal. Why are you trying to justify your comments using clear 'flaws in the system'? Its not a design, its a design flaw, and you claim to be against the design flaws in the system, so you taking advantage of them to troll us is what's 'nonsense', here.
Stop being a bad actor.
So the proposal owners should be able to prove the flaws of other proposals, in order for their proposal to be voted.
Thats why proposal owners should be allowed to talk to all proposals.
And no, the MNs decided years ago that non-MNOs shouldn't comment here. You are trying to subvert the will of the MNs by commenting here without verifying.
And its clear why, you don't have an actual MN, you're just a delegate voter. Again, you are on the fringe of what's acceptable here, and it explains why your comments are so destructive and trollish.
You should be banned from posting here.
That's my perspective.
That how I gain my talking rights.
Thats a desigh too, so stop telling nonsenses.
You are clearly just trying to abuse the edge cases in order to "force MNOs to take disrespect" so that your comments and the negative results they have will be "our fault".
This is a form of trolling and indicates that you are a bad actor.
Proposal owners are only supposed to speak ON THEIR proposal, not on every other proposal. Why are you trying to justify your comments using clear 'flaws in the system'? Its not a design, its a design flaw, and you claim to be against the design flaws in the system, so you taking advantage of them to troll us is what's 'nonsense', here.
Stop being a bad actor.
Here is my latest proposal, still active.
https://www.dashcentral.org/p/encointerUBI-mean26
Clearly that is not how this is supposed to work. You are attempting to troll the network by exploiting flaws in the governance system so that you can blame the negative consequences of YOUR ACTIONS on us.
These are power moves, they are deliberate, and they prove that you're being a bad actor.
So the proposal owners should be able to prove the flaws of other proposals, in order for their proposal to be voted.
Thats why proposal owners should be allowed to talk to all proposals.
During the period I mentioned, people like George Donnelly were abusing this flaw in the design in order to troll and attack competing proposals. We MNOs determined that this was bad acting and requested Rango to make it stop.
That's the will of the MNs.
PO's should NOT be able to attack or "prove the flaws" of other proposals. This place is for MNOs ONLY to have those discussions. You are trying to subvert the will of the MNOs with your false reasoning.