Proposal “pshenmic-dev-extension-november-2025“ (Completed)Back
| Title: | pshenmic.dev DFO Extension / SDKs November 2025 |
| Owner: | pshenmic |
| One-time payment: | 600 DASH (29668 USD) |
| Completed payments: | 1 totaling in 600 DASH (0 month remaining) |
| Payment start/end: | 2025-10-08 / 2025-11-13 (added on 2025-10-08) |
| Votes: | 637 Yes / 30 No / 6 Abstain |
Proposal description
pshenmic.dev DFO Extension / SDKs November 2025
Updated on 12 October 2025
Progress
Javascript SDK (dash-platform-sdk)
We have done a very important work in Javascript SDK, by optimizing the
dependency tree, cutting out unused code, and improving compatibility
between Node.js and Web environments. Very huge amount of optimisations
were made in the pshenmic-dpp by our backend dev owl352 that heavily
reduced bundle size (to 2.5mb, 1.4 mb compressed in NPM), and that gave a
significant performance boost, judging by response times on Platform Explorer
(it is using SDK almost on every request).
A lot of libraries were re-checked, and switch to a more efficient, performant,
and audited packages, and especially that uses standard Javascript APIs that
resolves a lot of cross-env potential compatibility issues. Now, we expect it to
work well in any JS environments, like Web, Node.js, React Native, Bun, Deno,
and others.
Although, React Native does not have native support of WebAssembly out of
the box, there are ways to make it possible (through native bridges, or by
using different bindings), and we’re just exploring that possibility right now!
The new, major version introducing all these changes will become available
very soon, as soon as we finish testing it in every frontend framework and
environment.
Core SDK (dash-core-sdk)
I started a work on a Javascript SDK for core, that we are already need for
implementing Identity registration in the Dash Platform Extension. It is going
to provide more easier libraries for interacting with Core protocol in Javascript
and will be using DAPI as the information provider.
It will include all experience we received during creation of dash-platform-sdk
and will be fast, cross-compatible between different envs, and provide all
necessary features to work with Core network, such as subscribing to new
transactions (with InstantSend locks!) and block headers (with ChainLocks!).
I have already drafted first version and made a proof of concept, now all left
to do is to just fill all missing parts with code.
Dash Platform Extension
Last month, we were targeting 4 major features:
pushed to stores very soon. We’re finalizing and integrating it with new SDK
version right now, but we’re at the final point, so expect it to be available early
on the next week (13-17 Oct).
Registration of identities is on the way, it will appear in the next version after
usernames, but I already did a good RnD on the correct way to do it and our
frontend dev already began drawing the screens, so we are hardly working
on making it as soon as possible.
This is not an easy task, as it involves Core chain, but my expectation it will
take 2 weeks approximately (first is to make screens with logic, and the
second to fine out the integration).
Plan
Short-term (1 month)
In next two weeks we are gong to be focused on Identity registration with
seedphrases, and after that, the next major feature is going to be a DashPay
contact list.
Although we don’t have access to Core chain in the extension yet, we can still
implement friending each other, and already can start receiving payments
from your friends.
Sending and spending Dash coins will be available after extension will get a
Core chain support
Mid-term (3 month)
In upcoming months, we would like to add all minimum necessary Platform
features in the extension wallets, so that we can finally start onboarding users
into it.
We will implement the basic Platform stuff that we need from wallet, fine out the
UI, make it work better, faster, and just generally stabilize it.
Long-term (6+ months)
On long run, we would like to see a Core chain in the extension and enable L1
payments in Dash as well. This will require a a lot of work to integrate Core
chain in the extension because of the L1 specific, and we need to research
a best way to implement SPV in browser, especially within browser's storage
limitations. But in the end, there will be a single extension supporting both
Dash chains.
Meanwhile, we are researching the possibility of porting the extension in an
React Native application, so that users could store all keys on their phone securely
without putting them even in browser.
Budget
Due Dash price, we can't set a specific Dash nominals in this month, but here's
approximate values in dollars (everything paid in Dash). All the excess will go
to reserve.
Frontend 6000$ (Extension Frontend)
Backend 10000$ (SDKs, extension backend layer, also includes pshenmic's salary)

_
Updated on 12 October 2025
Progress
Javascript SDK (dash-platform-sdk)
We have done a very important work in Javascript SDK, by optimizing the
dependency tree, cutting out unused code, and improving compatibility
between Node.js and Web environments. Very huge amount of optimisations
were made in the pshenmic-dpp by our backend dev owl352 that heavily
reduced bundle size (to 2.5mb, 1.4 mb compressed in NPM), and that gave a
significant performance boost, judging by response times on Platform Explorer
(it is using SDK almost on every request).
A lot of libraries were re-checked, and switch to a more efficient, performant,
and audited packages, and especially that uses standard Javascript APIs that
resolves a lot of cross-env potential compatibility issues. Now, we expect it to
work well in any JS environments, like Web, Node.js, React Native, Bun, Deno,
and others.
Although, React Native does not have native support of WebAssembly out of
the box, there are ways to make it possible (through native bridges, or by
using different bindings), and we’re just exploring that possibility right now!
The new, major version introducing all these changes will become available
very soon, as soon as we finish testing it in every frontend framework and
environment.
Core SDK (dash-core-sdk)
I started a work on a Javascript SDK for core, that we are already need for
implementing Identity registration in the Dash Platform Extension. It is going
to provide more easier libraries for interacting with Core protocol in Javascript
and will be using DAPI as the information provider.
It will include all experience we received during creation of dash-platform-sdk
and will be fast, cross-compatible between different envs, and provide all
necessary features to work with Core network, such as subscribing to new
transactions (with InstantSend locks!) and block headers (with ChainLocks!).
I have already drafted first version and made a proof of concept, now all left
to do is to just fill all missing parts with code.
Dash Platform Extension
Last month, we were targeting 4 major features:
- Masternode identities (for voting from PE)
- Token / Credit transfers
- Usernames registration
- Identity registration
pushed to stores very soon. We’re finalizing and integrating it with new SDK
version right now, but we’re at the final point, so expect it to be available early
on the next week (13-17 Oct).
Registration of identities is on the way, it will appear in the next version after
usernames, but I already did a good RnD on the correct way to do it and our
frontend dev already began drawing the screens, so we are hardly working
on making it as soon as possible.
This is not an easy task, as it involves Core chain, but my expectation it will
take 2 weeks approximately (first is to make screens with logic, and the
second to fine out the integration).
Plan
Short-term (1 month)
In next two weeks we are gong to be focused on Identity registration with
seedphrases, and after that, the next major feature is going to be a DashPay
contact list.
Although we don’t have access to Core chain in the extension yet, we can still
implement friending each other, and already can start receiving payments
from your friends.
Sending and spending Dash coins will be available after extension will get a
Core chain support
Mid-term (3 month)
In upcoming months, we would like to add all minimum necessary Platform
features in the extension wallets, so that we can finally start onboarding users
into it.
We will implement the basic Platform stuff that we need from wallet, fine out the
UI, make it work better, faster, and just generally stabilize it.
Long-term (6+ months)
On long run, we would like to see a Core chain in the extension and enable L1
payments in Dash as well. This will require a a lot of work to integrate Core
chain in the extension because of the L1 specific, and we need to research
a best way to implement SPV in browser, especially within browser's storage
limitations. But in the end, there will be a single extension supporting both
Dash chains.
Meanwhile, we are researching the possibility of porting the extension in an
React Native application, so that users could store all keys on their phone securely
without putting them even in browser.
Budget
Due Dash price, we can't set a specific Dash nominals in this month, but here's
approximate values in dollars (everything paid in Dash). All the excess will go
to reserve.
Frontend 6000$ (Extension Frontend)
Backend 10000$ (SDKs, extension backend layer, also includes pshenmic's salary)

_
Show full description ...
Discussion: Should we fund this proposal?
Submit comment
|
No comments so far?
Be the first to start the discussion! |