Open dckc opened 3 years ago
more market context:
Digital Identity on the Blockchain With Chainlink 9 Nov 2020
more market context:
In this case, the Digital Accreditation Wallet design presented Nov 18 does seem roughly on par, though this presentation reflects substantial usability research and it's not clear whether we could take advantage of that or if we'd be starting from scratch.
I have to agree that there is plenty of competition that's trying to do the same thing with much bigger budgets, and the only leverage we have over them is object capability model. A lot of those alternatives don't force end user to go to an exchange and purchase tokens in order to manage their identity wallet, especially if that token is not allowed to be purchased by US citizens. What we can do however (on the Casper level) is to enable some party to pay for those deploys upfront if we know how much phlo is needed and validators have to respect them as any other deploy. I usually refer to those as pre-paid deploys. There are of course privacy concerns, moral concerns, etc. I would prefer if the primary goal is not for mass-testing of people for Covid, as there are many more useful usecases, like "does anyone who's boarding this plane have certain alergies, in which case how many are there" rather than "Sir, you don't have a proof of vaccination for covid and are not allowed to travel, pleace go to the end of the line".
Civic is another one I ran across this morning. Its current offerings are largely centralized, but the whitepaper shows a road to decentralization.
decentralized storage + transactions motivates RChain.
quick note from chat with @leithaus ; here's hoping I find time to elaborate
Another one:
They're hiring a scala dev:
The current market leaders are services such as sovrin. It's permissioned rather than decentralized, but at this point, so is RChain (cf https://github.com/rchain-community/rstake/issues/6 ).
Common cases of writing to the Sovrin Public Ledger are free: DIDs for Individuals (Peer DIDs) and Credential Issuance. In RChain, every deploy costs REV. (There is discussion of sponsored data APIs but not much work has been done.)
sovrin uses technology from what seems to be the most popular self-sovreign identity API, hyperledger indy.
Zero Knowledge Proofs in the Sovrin Network are deployed in production. Perhaps the same essential design could work with RChain, but it's not clear what benefit justifies the effort / risk.
Hyperledger members and governance shows involvement of ConsenSys, IBM, Intel and so on; sidetree have has involvement from Microsoft.
RChain doesn't even get mentioned in the context of events such as IIW 31 Oct 2020.
RChain's architecture has advantages over these designs in that rholang supports scalable cooperation without vulnerability thru capability security. But the Digital Accreditation Wallet design presented Nov 18 makes no use of that. (See also rchain-community/liquid-democracy)
The value proposition of this design is entirely unclear, to me.