Let's get this crypto!
|CMC#||Market Cap (USD)||Volume (24hr)||Circulating Supply||NVTS||Change (7d)||Change (24h)||Savings Per 1K|
Civic is attempting to create a decentralized identification platform that allows users to control their personally identifiable information (PII). The team believes that by using a distributed, cryptographically secured database users can gain greater control of who access their data and how it is stored, reducing identity theft and increasing access to identity for many in areas where government services are lacking. Civic imagines a broad set of applications such as travel documentation, banking, credit, and web credentials. Personal identification services are currently provided via the Civic mobile app. The app allows users to upload their personal data which is stored locally on their device using encryption and biometric locks. Storing data in this way gives the user full control over their data and can remove the risks involved with Civic holding user data in a central database. Current services are not fully decentralized and rely on the company to verify a user’s credentials before validating them for use. After verification, an attestation is added to the blockchain providing proof-of-ownership for users. Requestors can confirm that the details being provided by a user belong to that user by checking the attestation provided on the blockchain. In the future, using the Civic (CVC) token as an incentive, the team plans to create a fully decentralized system. Civic believes that the future system will allow users complete control over how their information is verified and remove the ability for governments or other organizations to censor data, which they see as compelling enough to make a blockchain potentially worth the cost and inefficiency involved in building a distributed system
Civic currently provides identity verification through the Secure ID Platform (SIP). Users access SIP through the Civic App. Users are able to upload identity documents, like a driver’s license, which is then verified by a third party and an attestation is added to the blockchain. An attestation is the hash of underlying element of personal identification plus some additional metadata, which results in a ‘stamp of approval’ that can be referenced to validate identity. When a user wishes to prove their identity, they scan a QR code provided by the requestor and can share the specific information being requested. The requestor is able to verify the user’s identity based on details stored in the Civic App and by referencing the blockchain attestation. blockchain attestation. Additionally, user’s personally identifiable data (PII) is organized locally into a Merkel tree that allows for verifying selective attributes and enables users to share data selectively. Civic is currently developing a decentralized, open-source ecosystem, Identity.com. Civic leverage the Identity.com platform for their identity verification solutions provided through the Secure ID Platform (SIP). Identity.com will incentivize identification providers (Validators), such as a business that has already performed verification on a customer, to perform trustworthy identity verification, for which they will be rewarded in CVC tokens. Validators will validate the identity of a Civic user and “stamp” this approval on the blockchain in the form of an attestation. Recent updates to the Civic whitepaper include a Token Behavior Model, explaining a detailed proposal for incentivizing valid attestations by validators in the Identity.com ecosystem. Civic Inc., in conjunction with Newtown partners, proposes a game-theoretic model where requestors can flag validations if they believe these to be incorrect and validators can either accept or reject responsibility for a flagged attestation being incorrect. The Token Behavior Model, predicated on game theory and smart contracts, and is designed to focus on the mandatory goal alignment between ecosystem participants. The penalty and rewards system provides four possible results: 1) correct attestation accepted by requester, 2) correct or incorrect attestation flagged by requester but flag rejected by validator, 3) correct or incorrect attestation flagged by requester and flag accepted by validator, 4) incorrect attestation accepted by requester. Because option one provides the greatest reward, most participants should be incentivized to act in a way that achieves this outcome. A party seeking user identification would stake tokens which would be transferred through a smart contract to the validator once honest validation has been performed.
- No data is available yet.
Back to Coin Listing