Welcome!

DashMoney - Creating P2P Markets

You can visit DashMoney.io and try out the Decentralized Frontend on testnet.
The code is here: https://github.com/DashMoney/DashMoney-Decentralized-Frontend

(05 18APR24- Testnet updating to 1.0.0-dev.10 11 - DONE) - You will need to either create a new wallet and get new testnet Dash OR clear your local storage in the browser. If you don't clear the local storage. The frontend will try to pull the old testnet identity.

Also, I think “DashMoney” the word itself may be a deterrent for some. So you can use “Frontend team” or “Frontend Development” if you want to refer to me or the work I do, differently. This does not change my goal of Dash being money in any way.

To further assist, I set up DashGetPaid.com as another copy of the Decentralized Frontend with a different name that starts in light mode instead of dark mode.


What I said last proposal and what I did:

1) Bring back ‘Groups’ (DONE)

Added new feature “Events” (DONE) in Nearby dapp that combines with Groups dapp for Meetups and that sort of thing.

2) Improve Login (DONE) – Platform Login with Wallet Loading in Background. The first time you log in will be slow though, because there is no chain data saved for the spv wallet, and you need an identity for Platform Login. All subsequent logins are much faster, and you can access platform data for dapps immediately.

3) Bring in “previous DashGetPaid” as ‘My Store’ and ‘Shopping’. (DONE)

• Add the "Pay Later" Feature (DONE)
• Additionally, added the ability to do ‘Tracking Only’ (DONE). Orders placed where the total cost of item(s) is 0.00 Dash, a user can submit the platform order document, so the merchant and buyer can coordinate and/or track status of an order without having to direct payments through My Store/Shopping dapps.

 
4) Create the ‘Identity and Documents - Control Page’ (CHANGED)

• Identity Control Page on the Account Login Screen (ONGOING)

• Documents Control Page (DEFERRED) – Instead of deleting documents in a separate area(poor design decision), I will just be adding the deletion of documents where you edit documents. This will be awhile before I get back to all the different dapps and add this, but that is the plan.

5) Bring in the “Credit Transfers” as the frontend fee mechanism (DONE)

New) P2P Exchange Market (DONE) - Marketplace operates on the Buyer-Beware Principle. Initial version needs testing and feedback.

Found and fixed numerous deficiencies.

What I plan on doing for this proposal(estimates):

1) Add Payment Requests to Wallet dapp. (2 weeks DONE, needs testing and feedback) In the Wallet dapp, you will be able to send payment requests to others and others can send to you, then with 2 clicks you can pay or reject payment requests.

2) Rides and Drivers Dapps  (4 2 weeks left total for both sets, each 2 sides like My Store and Shopping): Not just Dash Uber, but to capture the idea of Creating Markets on Dash Platform. So it could be a ride, moving service, or hauling/load boards (semi/trucking service). If you want movement of something from one place to another, then there is an opportunity for exchange.

I will go a bit further. Uber makes approximately 25% on each ride. Though Rides and Drivers will not have the UI/UX of a multi billion dollar company, there is always the ability to compete on price. And if Rides and Drivers can provide rides 20% cheaper, there is opportunity to compete.

(Separate Dapps) Load Boards and Trucking Dapps - Trucking is a 2 trillion dollar industry, if fuel is not priced in Dash, having the value of transportation in Dash wouldn’t be too bad.

How both work: If you were a driver, you search your local area like how Nearby dapp works. Then a list of ride requests appear. The driver can select from them based on the addresses for pickup and drop off with distance/time estimates and the offer’s price. The driver can then accept offer. (Counter with different price - possible future feature)

The ride requester can then confirm the driver who accepted OR wait for a different driver to accept.

Load Board and Trucking works the same but load provider instead of ride requester and trucker instead of driver.

Payment could be on pickup, drop off, or 1/2and1/2.

Differences between Rides and Drivers and Load Board and Trucking
Rides and Drivers: select number of Passengers, and future possibilities of add Ride Share or Carpool options.
Load Board and Trucking: select Trailer: F(flatbed), SD(steep deck) or V(Dry van), Weight: 48,000, etc.

These dapps should probably have their own development teams and be on mobile(not web). But I will do my best.

3) Reservations/Appointments dapp (4 weeks) :

How it works: The host, one with something to reserve or schedule (e.g., renting a room, haircut appointment, etc), posts what it is, title and description, and availability (e.g. “M-F 8-6, Sat. 9-7” OR “01MAR24 - 30JUN24”).

The customer sends a request for when they want to use or set appointment.

Host can then confirm the request, and this confirm blocks the requested time slot. Or if it is non-blocking, just accepts the request, like if you have multiple dental hygienists and a user is scheduling a dental appointment or multiple rooms in a hotel.

A visual schedule can then be formed and displayed from the confirmed requests. So users can determine based on posted availability and blocked out time slots when they can request. Additionally, the payment can be Pay On Request, Pay Later, or Schedule Only(no payment directed through dapp).

The search will be by name like the Shopping dapp, or you can add a location in Nearby dapp like “Shops/Menus” but this will be “Rsrvs/Appts”.

4) CrowdFunding Dash Platform style (4 weeks): How to Use: A proposer can post a topic or proposal. Each topic/proposal uses a platform identity as the “funding address” to show interest in topic. So people “up vote/fund” by Platform Credit Transfer amounts to the “funding address” identity.

There will also be a discussion area below the topic/proposal which will be a modified Group from Groups dapp. No joining of this Group required though, everyone has access.

The ‘Identity Controls’ page (link is on the ‘Account Login’ page of Decentralized Frontend) will allow users to copy the IdentityId of an identity prior to name purchase and the identity can be used as the “funding address”. This way the proposal’s interest is not conflated with a user’s platform credits for everyday usage.

And after certain time or if they reach certain amount, the proposer can withdraw funds, and edit the topic/proposal as completed.

5) Tickets dapp (for conference, concerts, etc)(4 weeks): Connected to Events in Nearby. User can submit ticket-request.  The ticket(if available) will show up in their Shopping – Orders or maybe separate dapp for purchase.

Ticket-Events are created with a number of tickets allotted, so let’s say 60 for example. And based on the timestamp that the Ticket-Event was created, and if your ticket-request is one of the first 60 based on its timestamp then you can purchase the ticket. (A query to Dash Platform handles this, the determining if your ticket request is in the first 60 or not.)

Extra -  What if there are 1000 tickets? Or what if someone submits a ticket request but doesn’t complete purchase. I think there will be a time limit to complete ticket purchase. This dapp is not fully planned out yet, but can work, just working on implementation details.

Future Thoughts, currently only thoughts/ideas/direction

1) Decentralized medical/dental market and completely different UI/UX: Think “google search-like” so just a blank screen with single text input, and you type in “knee injury” or you search “dental cleaning”(Category/keyword search). A list of different businesses or entities that have tags to what you searched will appear. Also, different search modifications, you can add a location/area or select a prices ‘view’ of different offerings by the different businesses.

And you can select between the different entities/businesses offering the services.

When you click on a business after the search, you have all the functionality/dapps for a business incorporated on a single page instead of all the functionalities separated into different dapps like DashMoney.io is setup currently.

Create entire new markets with visible pricing of different businesses for comparing and viewing offerings with locations, customer reviews, scheduling appointments, etc for a business on a single page.

2) Change all the payments (Pay-to-Name) to utilize the DashPay Data Contract. Currently, the way Pay-to-Name functions is by attaching an address to a Platform document, and this address is then query-able by the Dash Name. It is a simple, functional option, but the DashPay Data Contract is the gold standard for how Platform and payments should operate.

I have some of Dashameter’s old code with a Javascript implementation of the early DashPay Data Contract. But this does not include the updated Contract Bounds, and anyone interested I think this would be a worthwhile endeavor.

3) Messages  - private/encrypted Direct Messages and Shopping - private/encrypted orders. If there was a simple tutorial or library for this: i.e. add salt property to data contract, use this library, add identity keysId used to encrypt to data contract, with identity keys explanation via DIP 11, etc.


END OF PROPOSAL, next are my thoughts..

About the way I am building dapps and using Dash Platform.

First, there are many more ways to use Platform than how I am using it.

When I say more ways, the Frontend approach completely skipped the traditionally approach of having a server on the backend, and many other interesting opportunities with a backend to cache data and deliver other information to a user. But I chose a more decentralized approach; however, thinking about how currently the biggest industry in crypto are centralized exchanges, I wonder if I overlooked more valuable and immediate possibilities.

With that said, if you get to the heart of how I think Dash should function as money, you will find that it centers a lot on trust. But not trust of any centralized entity.

The trust, I am talking about is trust that each individual extends to another when they choose to interact and exchange with them.

The way I envision Dash functioning as money is captured in the idea of a high trust, low time preference culture.

An oversimplified example of a high trust, low time preference culture, let’s say you have a vegetable stand on the side of the road. But you don’t stand by the vegetables all day, you set the vegetables out in the morning, write down the prices, put your Dash Name on a sign, and go about your day. And people stop by, choose what they want, and pay Dash to you.

I know this is not how the world works. But the way I see Dash being money is in a world where a person’s word has weight, and a person’s name means something. Because the way I construct dapps, you connect to another person and nothing else. This is the user-network that I talk about.

What I find fascinating is, this not only works best in a high trust, low time preference society, but it reinforces that behavior through economic incentives. Or It Builds a high trust, low time preference economy  through economics.

For example, if this was your first time interacting with someone on a P2P Exchange market, you should use a low amount, and if they reciprocate, you will most likely trust that person in the future. If you requested and confirmed a ride from someone and no one shows up, you will not use that person in the future.

It is a gentle* force. But the greatest power manifests in such things.

As I said earlier Dash Platform could be used in many different ways, but this is the way, I am building on Dash Platform.

--END-- (Not quite)

I had all the above prepared prior to 20 March 2024.

I was then introduced to Pshenmic’s (from Dash Incubator) Platform Explorer API.

It gave me many interesting ideas. I will share two of the biggest ones.

Someone could reproduce all the dapps I have made, but instead employ server-side rendering, and so the application would get to the user nearly instantly by only sending the data and components, the user had requested, instead of the whole Frontend.  (This is specifically pertaining to slower networks, like 3G when comparing to the Decentralized Frontend) But this path negates the proofs of Dash Platform and would not be decentralized.

Added to the above - This is strictly speaking of the long load time from page load (Not from Platform queries), but from Dash SDK which is big, and it is included in the Decentralized Frontend.

Employing server-side rendering could be a better way to use Dash Platform for mobile (cellular network, 3G) and development could happen relatively quickly. The frontend's components for display are built. You just change where the data is pulled from (platform data would be pulled by the server, this is the centralization part, this is where the Explorer API started the idea), and you don’t have the Dash SDK in the client any more which speeds up the page load.

If you take the idea of Web3 - Decentralized Accounts, that just means using the 12 word mnemonic, which is your wallet, but treat it as a hot wallet and think of it as an “account” that you control and can plug into different applications.

The takeaway is you could access the dapps through decentralized means (Decentralized Frontends) or what could be a faster, lighter, centralized way. And you could go back and forth between them, if you wanted.

OR! What if we don’t do web at all? And go React Native with the frontend, so users can go to an Android app. That could be Decentralized and fast!

Because until this I was unsure of how the large frontend could be truly used in a mobile sense (not connected to wifi), but both server-side rendering and React Native seem like they would work.

(As an aside - The React Native approach could be decentralized and fast, but Android or Apple could gatekeep.)

Right now centralized exchanges are much bigger than decentralized exchanges. And say someone wanted to be a driver for the Rides and Drivers dapp. They could have like no Dash in their wallet, because they are wanting to earn Dash, and they want the fastest UX available, whether decentralized or centralized.  The free market is big enough for both to compete and the customer(the driver/Dash entrepreneur) is always right.

Some people may not use Decentralized Frontends if they are not fast enough, but now, fast can be an option. And just like centralized exchanges have to compete with each other, possibly centralized frontends could also compete with Decentralized Frontends in the marketplace of delivering P2P markets to users! I added this, because I thought it was very fascinating.

The second idea I wanted to share from Pshenmic’s API is “Credit Transfers as a payment mechanism”.

So you can send Credit Transfers without the API, but with the API, you can know who sent to you. That is the game changer.

Pshenmic’s Platform Explorer API doesn’t have to be used in a fully centralized way. I think I will use as part of the Decentralized Frontend to enable Credit Transfer payments.

For instance, what if there was a business, a concession stand, with the Dash Name of ConeyIsland-ConcessionStand. People really like this concession stand, so there are 4 or 5 orders placed every minute, and there are 10 employees working. The employees could log in to a dapp with a “viewer mode”, and because credit transfers are public, employees could fulfill orders sent to ConeyIsland-ConcessionStand and see verified credit transfer payments. And you have a separation of money from people working, so nothing to steal and employee's safety is improved.

Having said all that, I am still going to build the above dapps that I have planned, Rides and Drivers and Load Boards and Trucking, Reservations and Appointments, CrowdFundingDash, and Tickets.
The only change is that I will incorporate the paying with Credit Transfers. This is fairly simple from the spending side. It's the verifying receiving by receipient that is more involved.

These dapps will take at least a few months to do. And then we can see where Platform is at and make a new plan with all that information and feedback from Platform users.

But if someone wants to start building, don’t wait. Nothing I have built is beyond using React and Javascript. And ideas are for whoever wants to use them.

In conclusion, as exchanges have really been the center of the crypto world up to now. I think Frontends (centralized or decentralized), allowing users to connect in a P2P way, will be the marketplaces of the future. And Dash will be the medium of exchange that facilitates these P2P markets.

I hope many others operate and build on Decentralized Frontends (even just translating to a different language) and earning Dash. I will continue to add new dapps and features to the frontend I am building. Thank you for your time.



* The gentle* force is why all smart contract systems get it wrong. In smart contracts, the computing and execution is done on the computer-network side. But there are two sides in each crypto: the computer-network and the user-network.

In money, the user-network computes and executes through the market. The computation is of a market good or service vs the price, and the execution is the exchange between the buyer and seller. With data contracts, the computer-network side simply connects the users together.

Data Contracts facilitate the network effect of the users. The user or the human mind is a quantum computer. The network effect operating on the computer-network is an exponential force multiplier based on every user that uses the money. Making money the most powerful computational force in existence.

The irony is smart contract systems didn't want to be money, so they focused on being the world's computer. But that is what money is. Even greater than any AI model could dream of.




-
-

-