Welcome!

Please Vote !!

https://mnowatch.org/votethenumbers/votethenumbers3/calc3.php?proposals%5B%5D=BTCBackportsVijay_01

Your proposal was accepted 66.18 % of the valid votes. In worst case, if we use the mean average election method, you should be paid 50*1.38/2 = 34.5 Dash.

So your proposal is already voted and accepted!
But it failed due to the stupid voting system!!!

So, wake up!

Stop beggins the possessed/stupid voters. Stop begging the daemon possessed DCG.
Spend 1 Dash, add the below proposal, and challenge now the Dash election system!

https://www.dash.org/forum/index.php?threads/pre-proposal-put-the-unvoted-10-net-votes-threshold-of-the-dash-budget-system-into-vote.54042/

I’m reaching out to humbly ask for your support in the final days of voting for my proposal,

Unfortunately, my proposal didn’t pass last cycle due to budget constraints. However, I remain hopeful that with your help, we can secure the votes needed to move forward.

I fully understand how important it is to ask for your support, and I don’t take it lightly. Let me explain why your vote matters:

Over the past months, I have been dedicated to backporting Bitcoin updates to Dash to keep our codebase aligned with critical Bitcoin Core enhancements and security fixes. Some of my recent work includes:
Improvements to memory safety, transaction processing, and RPC documentation.
Enhancements in error handling and overall system stability

PR Link Updates and Improvements Backported​
PR #6257 Added references for Bech32(m) generator and constants, dropped Leak Sanitizer suppressions​
PR #5884 Various refactors and bug fixes for stability​
PR #6064 Updated RPC command documentation for clarity​
PR #6061 Enhanced error handling for RPC errors​
PR #6071 Updates to documentation and minor bug fixes​
PR #6129 Fixes for memory handling and optimization​
PR #6130 Improvements to handling of core node settings​
PR #6133 Bug fixes for handling invalid transactions​
PR #6134 Refactoring to enhance code clarity and reduce code complexity​
PR #6220 Added missing RPC examples and enhanced documentation​
PR #6250 Prevented wallet code from interfering with node settings​
PR #6256 Fixed issues with the -persistmempool option and added necessary documentation​
PR #6264 Corrected C++ argument names and updated RPC handling​
PR #6263 Prevented potential memory exhaustion issues and enhanced fuzz testing stability​
PR #6274 Fixed bug in estimatesmartfee RPC and refactored unnecessary code​
PR #6305 Added additional validation and improved transaction safety checks​
PR #6309 Minor bug fixes and improvements in error handling​
PR #6435 Various improvements to the network and protocol layer​

You can explore a detailed list of my contributions [here](https://github.com/pulls?q=is%3Apr+author%3Avijaydasmp+archived%3Afalse+sort%3Aupdated-desc+is%3Aclosed+is%3Amerged).

The success of this proposal is critical to the ongoing backporting work I am doing, and your vote in the next few days could make all the difference. If you see the value this work brings, I would be incredibly grateful for your support.

Thank you to those who have already backed this proposal—your support has been a great motivator. If you have any questions or concerns, please don’t hesitate to reach out.

The URL https://github.com/pulls?q=is%3Apr+author%3Avijaydasmp+archived%3Afalse+sort%3Aupdated-desc+is%3Aclosed+is%3Amerged
does not work.

Hi Demo, its a github url; please login to github and try again

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dear MNO/Voters/community

I am incredibly grateful to those who have already supported my proposal.
I deeply value your trust and remain committed to contributing through my work.
My proposal, BTCBackportsVijay_01 (https://www.dashcentral.org/p/BTCBackportsVijay_01), was dropped last month due to budget constraints. I kindly ask for your support this time. While I have received half of the necessary votes, I still need additional "yes" votes to get it through.

Here’s a quick summary of my contributions:

- - GitHub profile: [https://github.com/vijaydasmp](https://github.com/vijaydasmp)
- - 98 Merged Pull Requests: [View here](https://github.com/pulls?q=is%3Apr+author%3Avijaydasmp+archived%3Afalse+sort%3Aupdated-desc+is%3Aclosed+is%3Amerged)
- - Active PRs: [View here](https://github.com/pulls?q=is%3Apr+author%3Avijaydasmp+archived%3Afalse+sort%3Aupdated-desc+is%3Aopen)

Your "yes" votes would greatly help me continue this important work.

Thank you for your time and consideration!
Vijay (aka cryptotura)
-----BEGIN PGP SIGNATURE-----
Version: Keybase OpenPGP v2.1.13
Comment: https://keybase.io/crypto

wsBcBAABCgAGBQJnUHHUAAoJEOWCi5R1+ahbMtkH/A0S1BtzUz9pBk4NfABPoPz0
KvM59ATb95JX1ITHE8oCCCVEK5bDsUGMD/qv8/3lf7QvS/lxiXCoMQrMKXYhAo+4
p67lgJwTFPOyzGiWtI1zgEZRWYpmrkxIhF6Fztx6LllURMgQfdoiS9+ISzI6h0Ls
svI5cBIG+W5J96rEWjKs/arDYK8B6eX+Uu435ROmL0/WhDBl9DmYKOSqbD5ONKbh
dN1LAlheZxi5BTME3nGXoRvHOxrAO4KfzcCBnQHbRRC+GXuN/PuhT8SWYRpGAM4V
CJtObXJRpuago/MIZXQWf6FiNuzJV0ICjyNvSL7jrUsPclRC/qu2etOZLzGdJG4=
=UqtQ
-----END PGP SIGNATURE-----

Now that the budget has eased due to Dash market price appreciation, I would like to see voters find room for this proposal in this cycle's budget.

This proposal was accepted by the 57.85 %

https://mnowatch.org/votethenumbers/votethenumbers3/calc3.php?proposals%5B%5D=BTCBackportsVijay_01

But it failed!!!

Wake up, stupid proposal onwers!

Challenge the election system!

https://www.dash.org/forum/index.php?threads/pre-proposal-put-the-unvoted-10-net-votes-threshold-of-the-dash-budget-system-into-vote.54042/

The backports are important work that I'd be happy to support, but I'm a bit confused by seeing this proposal. At every core release, DCG says they implemented so and so many Bitcoin backports. Are you part of DCG? Or are they claiming credit for your work? If not, could you please describe how the backport work is divided up?

Dear MasterNoodle,

Thank you for your question,

I am not part of DCG; I’m just an open-source enthusiast who stumbled upon Dash in September 2021. As I explored the project, I became intrigued by its potential and wanted to contribute. I applied to be a part of Dash, and I was redirected to the Dash Incubator program.

Since 2021, I’ve been contributing through the Dash Incubator under various strategists like Spectaprod and Pshemnic. The work I’ve done so far has been aligned with improving Dash through Bitcoin backports within the program.

Now, with changes in the way contributions are organized, we have to create our own proposals to continue the work we’ve been doing. This proposal represents my effort to secure the support needed to keep contributing to Dash’s development.

Backporting is a team effort, with core developers like KittyWhiskers and Pasta handling a significant portion of the work. I contribute as much as I can within my capacity.

I hope this clears up any confusion, and I’d be happy to answer any more questions you might have!

> Since 2021, I’ve been contributing through the Dash Incubator

So are you still getting paid from the Incubator?

> Now, with changes in the way contributions are organized, we have to create our own proposals

Could you please outline what those changes are? I thought the whole purpose if the Incubator was to collect a budget from the treasury to be able to pay out bounties for specific tasks. If you have to create your own proposals, what's the point of the Incubator then?

No, @MasterNoodle, the last received from Incubator was in September. The changes are an independent contractor model instead of working under a strategist.

Thanks, Rion. I’ll keep contributing in my capacity because I enjoy doing it. I remain optimistic about gaining the community’s support in the future.

The budget is tight right now, so I can understand not prioritizing this for this month.

I would ask MNOs to consider upvoting so that it can potentially be brought into funding next month when it seems likely that the budget will be more available.

Thanks for your consideration.

Dear Community,
I recognize that there are other high-priority projects needing funding ahead of mine. I’m perfectly okay with abstentions or even having my proposal overlooked given the current demands. That said, receiving a "no" vote can feel somewhat disheartening.

Dear Community,

I kindly request your support and vote for my proposal on backporting Bitcoin changes to Dash. Your vote will allow me to continue this essential work, ensuring Dash stays aligned with the latest Bitcoin advancements.

Thank you for your support!

Best regards,
Vijay

FYI, this is indeed Vijay's proposal. He submitted it using our new proposals.digitalcash.dev app, but he still needs to set up his full node to claim ownership here on dashcentral. We will eventually bring the proposal claiming feature within the app as well, but haven't got to it yet.

Thank you, Rion, for sharing the new tool—it made submitting the proposal much easier for me. I also appreciate all the help and support you've provided me.

You are doing great work, voting YES!

You can see Vijay's github account here and the PRs he is doing.

https://github.com/vijaydasmp

Thank you very much for your appreciation

Are you kidding?

Voting YES to a proposal with NO description?

Hi I have now updated the proposal, requesting your kind consideration

If you are the one who backports the Bitcoin changes, then WHAT THE HELL DCG IS DOING????

I support you.

Hi Demo, backporting is a substantial task, with Pasta and Kittywhiskers managing most of the heavy lifting. I contribute in my own capacity to support the team in this effort. I’m grateful for your support and hopeful for continued backing so I can expand my contributions in the future.

It's a team effort, Demo, Vijay only does a very small amount of the backports, kittywhiskers and pasta do the majority of them.