Proposal “pshenmic-dev-sdk-jule-2025“ (Active)Back

Title:pshenmic.dev SDK / Extension Funding Proposal Jule 2025
Owner:pshenmic
One-time payment: 630 DASH (12767 USD)
Completed payments: no payments occurred yet (1 month remaining)
Payment start/end: 2025-06-11 / 2025-07-17 (added on 2025-06-11)
Final voting deadline: in 1 month
Votes: 121 Yes / 18 No / 0 Abstain
Will be funded: No. This proposal needs additional 239 Yes votes to become funded.
Manually vote on this proposal (DashCore - Tools - Debugconsole):
gobject vote-many dc6ab1fe17a6a844693dbac2a8101dc7b4dd75ba8d5a3d02badad0ebdbdd1daf funding yes

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

Proposal description

pshenmic.dev SDK / Extension Funding Proposal June 2025

Updated on 13 June 2025

This is funding proposal for Dash Platform SDK and Extension within pshenmic.dev DFO.

General

There was lot of work happened around SDK and Extension, but most important is that we
finally laid out the code architecture, both frontend and backend in the browser extension
that will let us build next features more quickly and secure.

Our frontend dev, Alexey, switched to help with organizing frontend code. I’ve been working
on backend part of the extension, that involved building a reliable and secure messaging system
between web page and an extension. Our WASM DPP (pshenmic-dpp) was updated to the Dash
Platform v2.0 to support token transitions, and more DP v2.0 integrations is on the way.

Progress

JS SDK
https://github.com/pshenmic/dash-platform-sdk
https://github.com/owl352/pshenmic-dpp

SDK has been migrated to Typescript, to allow better code autocompletion and make better general
understanding of Dash Platform and its types. We did them both in DPP and SDK, so people can
easily know which methods or fields exists in their objects.

WASM DPP (pshenmic-dpp) was updated to Dash Platform v2.0 protocol, and the new Batch Token
transitions, and we are in the process of testing it in the testnet network.

A lot of unit test coverage was added in both repositories for a better stability during development.

On last DCG Sprint Review, Sam from DCG introduced a new JS bindings for a drive verification functions,
that should help us finally build provable Javascript SDK. This week, we finally was able to use it on real
function, and the test getIdentityBalance query has been successfully cryptographically verified! That
means we can do proofs in the SDK.

Dash Platform Extension

https://github.com/pshenmic/dash-platform-extension

Extension frontend code has been refactored and we are ready implement new features in it now. The
initial black-white UI was reworked so it does not hurt eyes anymore, and next features, like register and
import seed phrase on the way.

We have more than 1 projects now, and its time to think about reusing the components between apps so
the UX/UI look more consistent. As a result, we created a Dash React UI kit library, based on Tailwind CSS,
that is going to include common components that can be reused in other projects and further DApp
applications. We are using it now in extension code, and will update components as we will have more.

https://github.com/AlexeyTripleA/dash-ui-kit

Backend side of the extension, was heavily refactored for a secure messaging between web page and an
extension context. 
In browsers, web pages never have a direct access to an extension environment, where all extension
scripts are executed or data is stored. It ensures that your private keys are safe and never leak to a
website by a mistake.
The new code will let us build an DApp authorization dialogue, similar to Metamask, where only approved
websites can request and exchange information with extension.

We started drawing UI mock ups for a next features, and we began with the Registration via seedphrase flow,
that will allow create a mnemonic and register an Identity. We aim to implement it in next releases.

https://github.com/pshenmic/dash-platform-extension/issues/9

Plan

Our current goal right now is to release and distribute the extension for an open testing release as soon as possible
and we plan to finish that within a weeks (hopefully on the next week).

Then we are going to implement a Register Identity / Import via seedphrase flow, that will allow both importing your
existing seedphrase or creating a new one, and registering your first identity. I believe it should onboard more people
to Dash Platform in the Web.

More UX designs for next features are also going to be done, like Tokens, NFTs, Usernames, etc, that are necessary for
an easier frontend development.

SDK will be updated with the all new Dash Platform v2.0 features, like tokens and new Data Contracts.

Budget

The total budget on this proposal is 630 DASH:
  • Frontend / UX 200 DASH
  • Backend / SDK 430 DASH

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
1 point,9 hours ago
Building a provable Javascript SDK is exactly what we need. It will also in my view eliminate the need for DCG to build Javascript SDK from scratch, after releasing Platform 2.0 Tokens later this week.
As your developed SDK will include the cryptographically verified element and will therefore not be inherently less secure.
Reply
1 point,9 hours ago
Hopefully DCG can just go straight to further coding the marketplace for Tokens and does not need to spend so much time towards Javascript SDK.
Reply