Proposal “pshenmic-dev-sdk-jule-2025“ (Completed)Back
| Title: | pshenmic.dev SDK / Extension Funding Proposal Jule 2025 |
| Owner: | pshenmic |
| One-time payment: | 630 DASH (13362 USD) |
| Completed payments: | 1 totaling in 630 DASH (0 month remaining) |
| Payment start/end: | 2025-06-11 / 2025-07-17 (added on 2025-06-11) |
| Votes: | 452 Yes / 44 No / 21 Abstain |
Proposal description
pshenmic.dev SDK / Extension Funding Proposal June 2025
Updated on 17 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 (Update)
We are done with huge codebase refactoring, and heading towards first open test build. We expect to have it
on this week and hopefully release it for public testing.
The SDK already have been updated to work with v2.0 protocol, but only for regular document transitions
for now. The plan for it is to integrate all missing necessary features, implement proofs verification, and check
that everything is ready for mainnet.
There is a lot of work that has to be done in the extension, in UX, Backend (script), and Frontend. We aim to
finish importing by seedphrase, creating a new wallet and registering the new Identity flow, that should
onboard more people to Dash Platform in Web.
In best case scenario, I believe we can see a fully working extension wallet with minimal features in a next
month: multi-wallet, keystore / seedphrase wallets, identities registration, extension API for developers
In the worst case, we will have all that, but a little unfinished, in case some thing will take some additional time.
Timeline
1st week
Extension internal methods for wallet with seedphrase
SDK Token Transitions methods
UX screens (homepage, settings, about)
2nd week
Proofs Integration in SDK
Extension cross-browser support
UX screens (Approve State Transition Screen, State Transition Details)
3rd week
SDK / Extension Mainnet tests
Frontend implementation of seedphrase import and identity registration in Extension
Extension UX screens (State Transition Details)
4th week
SDK Documentation
Frontend rework of Approve Transaction Screen
Extension UX screens (Send credits / Withdrawal credits)
Budget
The total budget on this proposal is 630 DASH:
Updated on 17 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 (Update)
We are done with huge codebase refactoring, and heading towards first open test build. We expect to have it
on this week and hopefully release it for public testing.
The SDK already have been updated to work with v2.0 protocol, but only for regular document transitions
for now. The plan for it is to integrate all missing necessary features, implement proofs verification, and check
that everything is ready for mainnet.
There is a lot of work that has to be done in the extension, in UX, Backend (script), and Frontend. We aim to
finish importing by seedphrase, creating a new wallet and registering the new Identity flow, that should
onboard more people to Dash Platform in Web.
In best case scenario, I believe we can see a fully working extension wallet with minimal features in a next
month: multi-wallet, keystore / seedphrase wallets, identities registration, extension API for developers
In the worst case, we will have all that, but a little unfinished, in case some thing will take some additional time.
Timeline
1st week
Extension internal methods for wallet with seedphrase
SDK Token Transitions methods
UX screens (homepage, settings, about)
2nd week
Proofs Integration in SDK
Extension cross-browser support
UX screens (Approve State Transition Screen, State Transition Details)
3rd week
SDK / Extension Mainnet tests
Frontend implementation of seedphrase import and identity registration in Extension
Extension UX screens (State Transition Details)
4th week
SDK Documentation
Frontend rework of Approve Transaction Screen
Extension UX screens (Send credits / Withdrawal credits)
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
|
No comments so far?
Be the first to start the discussion! |
I just have finished the huge code refactor, that gave us clean code architecture for next features in the extension, multi wallet support, secure messaging system and private keys encryption. Right now, we are adapting frontend to new internal queries, cleaning up the code, and preparing the extension for distribution. We expect to end with that on this week.
Our plan for next month is to add all Token Transition methods in SDK, integrate proofs verification for DAPI queries, and generally prepare SDK for production by testing it in both testnet and mainnet networks. Extension will receive login by seedphrase, creating a new wallet, and even register the Identity functionality, that should engage more people into Dash Platform. I expect that next month we are going to have a first Web-compatible Dash Platform wallet that will keep your keys secure and allow devs to easily connect the extension in their DApps (we are going to integrate it in Dash Torrent Tracker as the first example).
Please vote for our proposal so we can do the extension that makes Dash Platform easier for everyone to use!
Finish and provide a positive result!
Then we will vote for
As your developed SDK will include the cryptographically verified element and will therefore not be inherently less secure.