Proposal “pshenmic-dev-dfo-february-2025“ (Active)Back

Title:pshenmic.dev DFO Funding Proposal February 2025
Owner:pshenmic
One-time payment: 405 DASH (14505 USD)
Completed payments: no payments occurred yet (1 month remaining)
Payment start/end: 2025-01-07 / 2025-02-06 (added on 2025-01-10)
Votes: 442 Yes / 56 No / 46 Abstain
Will be funded: Yes
Manually vote on this proposal (DashCore - Tools - Debugconsole):
gobject vote-many 52b4948e0ac9f4ff145fcfa6ff912e52c1c0923622c1fafe607a38adc54a9889 funding yes

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

Proposal description

https://raw.githubusercontent.com/pshenmic/pshenmic-dev-dfo/refs/heads/master/assets/images/18.png

pshenmic.dev DFO Funding Proposal December

Updated on 17 Jan 2025

Hello folks!

Happy New Year to everyone, and we’re kicking off with so much updates, so much things
happened last month and I would like to share it with you. Let's me go with it one by one.

Platform Explorer
PE received new Identity page, a lot of new backend queries, and we are already preparing
for Contested Resources and Masternode Votes pages as well as Fungible Tokens. We designed
tokens page based on the platform code I’ve read in the draft page, and as soon as token will
be live on any devnet or testnet, we will finalize the design mocks and proceed to implementation
to be ready with the date it will be rolled out in the mainnet.

We have finished the designs for the most features that we see are necessary, and will be
slowly moving development capacity to other projects.

Platform CLI
I got back to it as there are some update from the Core team. There is new query that is going to 
be included in the Dash Core that I was missing for implementation of the Identity registration
command. The new `getrawislocks` Core RPC now returns raw InstantSend signature value, that
is being used in platform Identity creation transaction. Previously, it was only available through
ZMQ. Thank you so much Core team for helping me with that.

I deployed the test Core build locally, updated my code and tested it, and it workedGreat, I was
able to make a successful Identity registration with my CLI. I am finishing my PR right now, and
as soon as new version is out, I will merge it in and release a new version of the application.

https://github.com/pshenmic/platform-cli/pull/13

The purpose of the application is to have a simple, cross-compiled, binary application that allow
you to interact with Platform chain.

This is going to be very useful for developers, testers, and enthusiasts who would like to interact
with platform via command line in the terminal.

The plan is to stabilize current features (register name, creditswithdrawals, masternode vote), and
implement creation of the identities, data contract, documents and all other possibleplatform state
transitions.

Dash Electrum
We worked really hard last month on the Electrum Project.

The current DIP3 implementation turns out to be partially working, and we really wanted to fix that.
The problem is that some transaction are working, some are not, and that there were a lot of things
causing that.

The wallet code itself was incorrectly working with ProRegTx transactions when you use existing
collateral UTXO, because it was originally incorrectly implemented. Masternodes were still on the
legacy BLS scheme, and that caused errors in the ProUpServTx transactions.

We was able to track everything down, and fixed the current DIP3 implementation and all related
features. The PR was merged in and we built a pre-release build for a manual testing. Everything
was tested against all platform (MacOS, Linux, Windows), and everything appears to be working
fine, though we found one more little thing that we are going to fix very shortly.

After a final testing and quality assurance, I am going to release a new Dash Electrum stable build.

https://github.com/pshenmic/electrum-dash/releases/tag/4.1.7.8-rc.2

Dash Electrum is tested with v22 nodes, and luckily current CoinJoin mixing working as expected.
Our protocol version is 70230, and Core P2P code is backward compatible. I am going to finish dsq
changes soon and will update Dash Electrum to the latest P2P protocol version.

JS Dash SDK
I was working on the NFT support in the current JS Dash SDK and got some success.

There are currently missing WASM bindings and JS SDK implementation for document transitions
like:
  • Transfer (change identity ownership from one to another)
  • Update Price (set a price for your document)
  • Purchase (buy a document from someone)
I have got working first two quite easily, and actually got broadcasted those in the testnet network.

https://testnet.platform-explorer.com/transaction/42175A63E25A316B5E0666317A3FF36A407EDDBA01D844982F68A6D10CBBFAF7
https://testnet.platform-explorer.com/transaction/36F3002686CA5ED23ED1FEFAD58803493055EFE55FC07517779AB267C8151747

However I got stuck on the Purchase one, as it is giving me an “state transition already in mempool”
error. During further investigation,It turns out there is some issue in the platform, we are investigating
it together with Platform team.

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

The next platform release will come with the fungible tokens support in the protocol, which I would like
to help integrating in the current JS Dash SDK as well.

Pshenmic.dev DFO Website
As part of the previous funding, we’ve finished seedphrase authentication with any associated identity to it.
It works transparently throughout the application, and able to pick up last check point where sync left off
making it way quicker to load all dataagain after page refresh.

During testing, we found the issue with JS Dash SDK, when it is bundled in Frontend Client application in
production mode with webpack. I investigated this problem and created an issue in Platform GitHub repo.
The issue very likely related to webpack Configurations and I’m going to find a proper fix for it soon.

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

Next feature that is going to be completed with previous fundings, is a first document platform document
submitting. That will happen on the all Projects page, giving us a first interface to interact with platform. It
is going to include creating a projects with admin Identity, and loading the data on the website straight from
Platform via DAPI for both authenticated and anonymous users.

As soon as we finish projects page, I am going to merge everything in, and deploy it to the production, and fill
it out with all our current projects in work.

The plan for this project is to continue moving hardcoded data from the frontend to the Dash Platform chain
where it will stay forever.

Decentralized Trustless Staking

A lot of people liked our project Decentralized Dash Pooled Staking, which willBe a Dash Platform DApp
application allowing people to easily create pools for Dash Masternodes and Evonodes, and even create
their own nodes.

Unfortunately mainnet Dash SDK is still in work, and to make it secure enough to work with people’s
money, we have to wait for a Provable Dash SDK in the mainnet network.

We have time before that happens, and meanwhile, we are going to start with smaller efforts, with a
Proof of Concept of the such approach with command line application, that would imitate all of the
ongoing processes in the mobile application, but in a terminal interface and a testnet.

We will create all the commands and test the concept in the testnet network, hopefully receive feedback
and find any potential security flaws.

Dashmate
There is one feature requested by a Core team recently. Dash Core implemented a Tor onion P2P peers
support, which allows it to share and exchange peer information independently from IPv4. Since it heavily
censored and nodes in different regions maybe inaccessible to each other due restrictions or network
outages, Onion support should help nodes to still find and exchange data regardless.

All Platform and Dash Core will still work with IPv4, but give masternode an additional transport layer to
exchange the info. 

WalletConnect
Unfortunately, cannot give you any new updates on this yet. Hopefully, I will update this section on a next
week.

Dash Rebranding
Last summer I met up with our UX designer, Sam (blackmirrordesigner), and it turnt out to be one of the
best contacts of the 2024 year. He is an experienced designer with, a really big blockchain background,
with a lot of connections with different designers, developers, and other product and content creators.

He got very inspired with Dash, with what products we do, and what we’re trying to accomplish, and we
started working together. He already showed himself as a professional, bringing our Platform Explorer
to the complete new level, that I’ve been only dreamed about.

All of us really wish Dash to have nice, fresh, and good-looking applications, that looks modern and fresh.
It's been a long time since Dash's branding was last time renewed. And I think might be a good chance
for Dash to refresh its styling and appearance. Although it could require a lot of changes and a lot of
efforts for Dash in the short term, it might be a really good thing for a long term, that will pay for itself
more than once.

We got a branding designer behind our back, who specialise himself on brands and guidelines, and ready
to start the work.

We will collect all the information and submit decision proposal soon.

Dash.org new website
A quite a bunch of people asking us if we could make a new Dash.org website or help out with the existing
one. Actually, we have everything needed for that: a dedicated UX designer willing to help, and a team of
frontend Devs ready to start making it.

We could design and create a new website from scratch, on a modern technologies, that will look fresh and
can for sure compete with any other top tier blockchain websites out there in the internet. Our designer
will put all efforts for the website to look great.

As a result, we will get a new Dash.org website, that we will be able to maintain and quickly add new features,
as per community requests, and make any further improvements or SEO optimisations.

Since it will require a lot of parties to negotiate on this, I am going to go with decision proposal on this project
first.

I will submit it very soon

Budget
The overall DFO reserve for today is 384 DASH, which is being split by the projects:
Platform Explorer 244.5 DASH
DFO Reserve 100.34 DASH
DFO Website 40 DASH

All unspent resources are going into the next month reserve reducing proposal ask amount.

For February, we are asking 620 Dash overall, totalling from 2 proposals:

Platform Explorer 215 Dash
  • Backend 65 Dash
  • Frontend 150 Dash
DFO 405 Dash
  • pshenmic, research, development and management compensation 175 Dash 
  • BlackMirrorDesigner, UX design reserve 150 Dash
  • LexxXell, full stack dev (moving from Dash Electrum to Trustless Staking DApp) 60 Dash
  • Infrastructure costs, 20 Dash

Accounting
https://docs.google.com/spreadsheets/d/1Ujl5xgqhOkX_7JmpFYyo4T4nEQsv9yuSrpQjvN2_CuM

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
1 point,3 days ago
Yes from me.
Reply
3 points,7 days ago
I am supporting both your proposals, good luck !
Reply
-3 points,7 days ago
Yet anohter slave developer, who satisfies the needs of the network of government agents, that vote in favor of him, in order to built destructive code that supports the stupidity of the platform.

A platform that is mandatorily distributed through the docker container (no compile, no reproducable builts) so that it is tottaly controlled by the agents in case the project derails from their instructions.

Go on, slave developer. You will be paid a lot, but you will end up in the prison of Hell, because your code offers nothing in favor of the human freedom.
Reply