Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 1500. (Read 9723849 times)

yr missing the localbitcoin market that the third tier will provide, the fiat/crypto transactions between users that can be initiated with messages...

qwizzie --> msg --> Otoh : interested in converting EUR to Dash ?
(as example)

These local bitcoin trades between users will also need to be rated / commented so in the end we can create our own internal trusted (build up of trust but also with multisig ?) fiat/crypto supply and demand
and not be dependent on external parties like exchanges..

yr missing the localbitcoin market that the third tier will provide, the fiat/crypto transactions between users that can be initiated with messages...

qwizzie --> msg --> Otoh : interested in converting EUR to Dash ?
(as example)

These local bitcoin trades between users will also need to be rated / commented so in the end we can create our own internal trusted (build up of trust but also with multisig ?) fiat/crypto supply and demand
and not be dependent on external parties like exchanges..

selfsufficiency is the keyword here i guess

edit : could also be seen as an attempt to decouple from Bitcoin ?

The need for distributed SPV  and DAPI implementations of contracts and multisig is clear and should be a priority IMHO.

Maybe some kind of alias is needed for a merchant to be visible (ie. no more ugly pubkeys)

So lets imagine I am a merchant that wishes to implement dash payments. As I see it I would need to create a wallet first and should be like creating an HD wallet. Now I only need an SPV client connected to DAPI to monitor the transactions. Now I need to integrate with my billing/management software (this is very specific and out of Evolution - market oportunity for developers)

Then I need that my clients know where to send money (QR codes are the best thing we have now I guess), this is where some improvements could be made.

So the client now could pick is phone, scan the QR and hit PAY. InstantXly I get the payment confirmation in my register SPV'd machine with DAPI integration and that's it.

From the brick and mortar perspective I continue to fail to see the need for users/messages... but I'm probably missing something  

I agree that verbal communication is sometimes important when co-ordinating payments, but please folks, stop. And think.

There is a trap that is one of the first pitfalls in software design, and that is loosing sight of your product's priority in favour of all the supporting ones that are not a priority. We live in a technology eco-system. The trick is to understand how that ecosystem sees you - not how you see it since it has options, you don't.

There's a tendency when developing product ideas to adopt an asymmetric, product centric view whereby the product 'becomes' the market instead of a market player.

As a great example of this, I knew a guy who built an online retailing service in the far east. His little company bought stuff (clothes, souvenirs) in little markets and shipped it around the world - acting as a proxy for people perusing the market themselves. (At that time you could only get mainstream, Amazon type stuff online). He got very excited about this business model and wanted to extend it to "any type of product from anywhere". In that vein he started buying up domain names around the theme of "shipdirect2U" and "worldDirect2U".

I tried to advise him that what he was seeing in his mind was the eco-system projected onto a product, not a product that would become the eco-system but he couldn't see it. 15 years later his vision has manifested - except it's called Google Shopping Feed and is contributed to by thousands of businesses all over the world.

What we need to do is ditch our product-centric view and switch to seeing how the world views the product. How and why will it pick it out amongst the myriad of other options it has ?

Form the "world's" perspective, Dash as a product does three things very well and three things only IMO:

[1] - being a public blockchain asset

[2] - fulfilling the monetary requirements of cash, being that it fully addresses bitcoin's fungibility and transaction time shortfalls

[3] - does the above with a technology stack thats largely compatible with bitcoin's

In fact it does those things so well that it's in a class of its own with regard to those three properties in combination.

There are of course other things that set it apart - like the articulated protocol etc - but they aren't things that "world" is going to care about to the extent that it can pick Dash out amongst the mass of options. They are not 'visible' to the market, they only support the 'visible' properties that I listed above.

Dash doesn't do chat, doesn't do online storage (other than blockchain), doesn't do social media and I don't think it should try to do any of those. However it can make itself "digestible" by social media applications which is the right way around for things IMO.

Re. Bells & Whistles
What do people do when they need to co-ordinate payments right now ? They pick up the phone. What do they do when they need internet voice-comms ? Get onto Skype. If you happen to be one of the miniscule percentage of people who require encrypted comms while they are making payments then there's always...

I use Team-viewer a lot which now has a built in chat feature, but I never use it because my 'perception' of Teamviewer is as a screensharing tool and Skype as a chat tool.

In summary - ok, lets have a brainstorm about everything - but I think any feature that isn't directly (or at least indirectly) supporting one of Dash's primary objectives as a highly fungible, anonymous, sustainably developed electronic currency asset needs to be regarded as 'excess baggage' by default. Those that are thought to be supporting Dash's primary market objectives need to have their roles well defined and in the appropriate context.

For example, the Facebook API example is a social media tool but which DOES have a definite role in supporting the currency since people already use Facebook but cannot spend Dash on their Facebook page. Adding social media features to a Dash wallet reverses this logic: the target market does NOT use Dash wallets and they CAN currently do social media, ergo: fail. (Dare I say...#R3.. ? LOL ! )

IMO, what Evan drew in that mockup posted earlier is similar to my mate from the Far East's 1999 view of the market - i.e. it is a symbolic illustration of how Dash will eventually integrate with the eco-system but not a realistic component of that ecosystem.

 

Maybe but if you could make that optional then you get the best of both worlds, entirely transparent public records when you want them and gone and forgotten when you don't.

Am I the only one who gets a little bit uneasy about the fungibility part lately? How is the priority currently beside all the other features? The sooner we get rid of this long darksend times, the better. When do you think the "separate paper" about Privacy & Fungibility is ready Evan? Thank you.

I was hoping you might have been looking to implement zk-SNARKs/zerocash as it looks very private and very fast.