Re: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency
Thanks for those links, OneDay. V. useful information.
Look at the chart:
https://coinmarketcap.com/currencies/dash/
I'm throwing everything into Dash, for both technical and fundamental reasons. I think Bitcoin is going way up.
Perhaps to $2.5Kwithin six months.
Dash will go up at least x12 within a few months of Evolution release, only if they can eliminate 'crypto' addresses in favor of "human readable addresses" and implement a plausible 'savings account' interest bearing account.
Just remember, this won't happen for about another year, right?
Right, Tante. Money invested now will be multiplied, money invested in about another year will not
You sound like you expect Dash Evolution to flop and not get any traction in adoption? It will probably take a few more years, but it will catch on IMO. Paypal didn't really exist until 2002, and by 2004, I was using all the time. Now it's beyond huge. I don't see why Dash won't be just as successful when we will have an amazingly easy to use interface.
The one thing that Paypal had that Dash currently doesn't, is a marketplace. It had Ebay. This is why I've wanted something like Open Bazaar, only run on masternodes, for the past 2 years, but it's too much, and it complicates things with Masternodes, so nobody wants to do that at this time. That's fine with me, I'm sure a solution will present itself at some point here.
So though I agree that money invested now will multiply, I don't agree that it won't continue to do so well into the future
Evolution does have a marketplace
It's the Apps section in the screens Amanda showed. An app is similar to a store in open bazaar, except you don't need to operate a p2p node to list/use one, you can do that through the decentralized API, in addition to moderated refunds there are other payment types too like recurring auto-pay for subscriptions. I remember when you suggested OB for Dash and was on the todo list and we found a way to do that and it's a logical progression of the system as soon as you introduce the concept of users and merchants at the protocol level tbh (or rather objects that are be configured to model users and merchants in Dash's higher tiers). The difference with OB is, Apps in Evolution are integrated to the Dash Network / blockchain via DashDrive, not a seperate p2p network on top of Dash, it also means any merchant / service / business that accepts Dash is listed in DashDrive (provided they use DAPI) so everyone can discover and access all Dash enabled services. It's always better to integrate services like this rather than try to run as a satellite p2p network which never seem to get good usage and have low node counts, to be fair this isn't possible in Bitcoin though which is an understandably conservative project in terms of protocol innovation due to the existing traction and comparatively large market size.
Super cool!
Is the Dash Evolution a open source? Everybody can deploy Evolution code on his website or we can only use Evolution on Dash.org?
Thank you,
Yes everything in Dash is always open source, and Evo code can be deployed on any website. There is really nothing special about dash.org apart from it's run by the core team and using the domain the network purchased. We will add an Evolution signup to dash.org when it's released, but any site can add this by just hooking into the https api the MN network will be hosting.
Excellent! What's the requirements to run Evolution website?
On the frontend, it's just JavaScript, on the backend, just include a DashPay library in your server-side code, which will connect to DAPI automatically in the same way you integrate Stripe with a library that speaks to their servers. The lib can connect to a local fullnode too if required.
For the Alpha we will release the DashPay lib for Node JS servers but we can add PHP, Ruby, Python, Java etc later or maybe people in the community will build those sooner.
For the website users, the minimum browser version requirements depend on the type of application. Anything that needs cryptographically strong random number generation or SPV, like wallets or signup portals, will need at least these versions:
Firefox 21 (2013)
Chrome 11 (2011)
Tor Browser v3.6 (2014)
IE 11 (Oct 2013)
Edge 12 ( 2015)
Safari 6.1 (2013)
Opera 15 (2013)
iOS 7.1 Safari (2014)
Android 4.4 Browser (2013)
But the bulk of the applications, like a merchant checkout or social plugin, don't actually need these features on the frontend, so old browsers will be fine, probably going back to IE6. Also, most Evo wallet users would probably be on native mobile we would think, but it's good to have a web option for that.
Sound interesting!
Does it means all the applications on app store are running on decentralized masternodes and the backend web server only interact with DAPI and the backend web server does not need a database?
All user information, user wallet, and application data... stores and retrieves by DAPI?
Thank you,
Hi there, a few people have asked similar questions on DF/Slack so let me clarify:
The term 'App' in the Evolution marketplace really means 'Merchant listing' or any entity that is providing a paid service, and it's a listing rather than a traditional App that you install (although this term was chosen because in future we can implement more in this area..) But Apps don't run on Masternodes, they are really data structures stored in DashDrive
So if you are an e-commerce Merchant, a POS retailer, a game developer, a vending machine operator or a masternode hosting service, when you signup an 'App' in DAPI you get an API key and then you can enable payments within your webstore, game, app, soda machine or whatever software / hardware you are selling through, by linking the DashPay lib into your source code then using it like a traditional payment API (e.g. Stripe).
The data DAPI will store for your app is just your basic listing info, a list of product SKUs (if you want), and a list of Orders which are raised by Dash users from your checkout.
So...yes you could implement a basic (e.g.) webstore without your own database and just rely on your App, product and order listings from DAPI, which relates to existing Dash users also in DAPI. This wouldnt be enough for a full-blown e-commerce pipeline, but it would be fine for e.g. buying content in a game or e.g. monetizing user generated content in a social plugin where the app provider just wants to see basic billing / customer info. This is a big advantage, because integrating crypto is so complicated for most businesses right now its one of the reasons they won't touch it.
A few other points - all of this is fee based, so every time an object is created / updated in DashDrive there is a small fee (but much smaller than TX fees because the data is smaller and it's also sharded in storage on MNs).
Also, Masternodes don't serve any code or content, DAPI is purely an API service.
We have a paper internally at RFC stage we should release next month that should explain it a lot better than me posting a few things here
Andy