I don't know why, I can't install the lastest realease on my phone. Previous was working fine.
User feedback is important. If anyone tries CashID out, please let me know how well it works for you.
i've now replaced the old phonegap barcode scanner with bitpays scanner plugin, which lets me add fully customized UI on top of the preview.
Lots of quality of life fixes done today. It no longer shows metadata choices if there is no choices to be made (none was request, or those that was requested was all previously known)
Configuration option to disable metadata sharing now always sends without optional parts, and complains if you scan a code with required parts.
all bugs encountered during the last video are fixed as well, and the general feel is now quite polished.
Left to do before v1.0: implement backups, NFC, intents, more metadata fields, user-initiated actions, identity history and identity updates.
I'm looking into backups atm. I wonder how to make "strong" pins to use for backup encryption, or if there's a better mechanism I could use to prevent use of backups when they fall into wrong hands.
I will be attending a local meetup in Gothenburg, Sweden this wednesday to talk about CashID. In the unlikely case there's a swedishtalking person here who wants to come, let me know.
In the coming month, I will be visiting local meetups in Gothenburg, Hamburg and Paris, and possible Amsterdam/The Hague to talk about CashID.
I've now visited a first meetup to talk about CashID. The presentation lasted for 26 minutes (out of 30 planned), and a very engaged discussion emerged afterwards that lasted for ~40 minutes.
From it, I've learned that demand for easy to use identification, in particular when tied to national identities, is something companies sees as valuable today.
The other "big" usecase seems to be the simplifications for everyday life that emerges when all your cards, keys and codes merge together to form a conventient single-system auth.
This validates the idea that a good protocol should be value agnostic in terms of politics: what data to share, when to share and how to use isn't something a protocol should dictate, but users.
Tomorrow I will be interviewed by the BCH Boys () about CashID.
The interview went well, though I think I should've let more light in. I didn't know during recording how dark it would come out.
cashport enables: "giving you access to their personal information and funds". This is a powerful concept and one that is missing bitcoin, and is established in traditional finance.
It could potentially be widely adopted, but the for-profit nature of their "business plans" could hamper adoption significantly, and there is little technical information regarding security.
Remember that it is competing with free (usernames + passwords), and that it faces the same challenges as CashID + monetization issues: namely, its value depends on the network effect of handcash.
Reading the cashport web SDK, the implementation is more complex than CashID, because it by necessity supports payments. The payments themselves seem fine, but I dislike the 3rd party centralization
I met with Rick Falkvinge who is a long-time user of BitID in berlin yesterday and talked about CashID. Got some valuable feedback and a few actionable items I can do to improve the specification.
I don't understand CashID. How does it work and then what's the point.
I'm currently working on a redesign of the identity manager to include wallet functions, so that I can showcase functions that relate to it without needing to rely on an external wallet for support.
