Welcome!




pshenmic.dev DFO Funding Proposal March 2025

Updated on 12 Feb 2025

Hey folks!

This is funding proposal for pshenmic.dev DFO operations for March 2025.

Progress


JS Dash SDK

The most noticeable issue I fixed last month was upgrading from Number to
BigInt for all uint64 DAPI GRPC types that wasn’t correctly handled in the Javascript
causing number type overflow, leading the SDK to read incorrect nonce value
from the DAPI, when you are making a new transaction. This led to inability to
make any more transactions towards this data contract from the given user
identity.

https://github.com/dashpay/platform/issues/2436

This severe issue was found when we have been working on pshenmic.dev
website, and the only one workaround was for us is to keep registering new
identities. Fortunately, I was able to find the root cause and provide a correct
fix for that. It is now working without issues in our Web application, and I’m
waiting for approval from the platform team to merge it in the main repo.

https://github.com/dashpay/platform/pull/2443

JS DAPI Client missing Contested Resources API methods for querying DAPI,
which is necessary to get information about ongoing polls in the platform.
Platform Explorer backend actually already have partially implemented this
in our own fork, and right now I’m trying to backport into main repository,
with the rest of the methods, typings and full unit test coverage.

https://github.com/dashpay/platform/pull/2446

NFT support for documents transactions is fully done and is in review.

https://github.com/dashpay/platform/pull/2444

There are couple more things to do in the SDK, such as v2.0 Tokens support,
issue with Webpack production bundles, and might be few more. I am going
to work on all that things and then update all the repository documentation
to reduce confusion among new developers. Additionally, I looked into WASM
SDK PoC code done by platform team and got on track with how provable
queries in the SDK is going to work in JS, would like to suggest my help here as
much as I can (from the JS perspective).JS Dash SDK does not work in Webpack
production bundles

https://github.com/dashpay/platform/issues/2415

Dash.org website

Few weeks ago, we had a call with Brian from DCG about current Dash website
and we are all agreed that it is becoming really hard going further with it. It
inherits the old codebase that was built ages ago using Wordpress, and it has
over 20 Wordpress plugins conflicting with each other and implementing each
change takes massive efforts.With our team, we can make a whole new website,
on modern techs, with a modern look that surely can compete with any other
high tier blockchain projects.

However, it is not going to be quick, we expect it to take at least 6-9 months of
development. But in exchange, we will receive a whole new website on new
engine that will allow us to implement, deploy, and change things on the way.
We are going to work on that together with DCG.

Right now, we are in the preparation phase, there is another proposal from
BlackMirrorDesigner, who will be able to provide us with much better and
modern assets, images, and mock ups for building a better, next-gen website.

Dash Trustless Staking DApp

A lot of people liked our concept of a decentralized trustless staking system that
can be built on top of Dash Platform. In general, it is a mobile first application
that connects and make additional consensus level utilizing multisig transactions.
The people will be able to organise in pools and earn  from running a masternodes
together.It is currently only exists as the discussion in the Dash Discord in the
#brainstorm channel and as a figma mock ups we were able to quickly to scratch up.

https://www.figma.com/design/GkpTThwlVzwslV3Sc0vPC0/Trustless-Pool-Staking 
https://discord.com/channels/484546513507188745/524726595060105226/1294778233320902767

However, a provable JS SDK is required with this projects, because a reliable
document querying is necessary to build client-side business logic inside the
application. We are hardly waiting for provable SDK on this project.

But we can use this time to fine out the concept and the specs, and try to
build a small proof of concept application that actually proves that the project
concept is working reliably and secure.

What I think would be great first, is to start with a small CLI application, that
would allow you to complete all these steps manually, and we could verify all
the steps from the creation of pools to withdrawals in the testnet network.

We just have started the development process of the CLI PoC with our full stack
developer, and you may follow the progress here (click watch): https://github.com/pshenmic/dash-trustless-staking

Plan

The plan for next month is to keep going with all the projects and keep improving the SDK for ongoing external developer’s needs.

Budget

Accounting Table

https://docs.google.com/spreadsheets/d/1Ujl5xgqhOkX_7JmpFYyo4T4nEQsv9yuSrpQjvN2_CuM/edit?gid=855683561

Our DFO operation ask for next month is 420 Dash, that is approximately being split:

200 pshenmic salary
195 UI / UX reserve (will be split among projects)
25 Infrastructure costs