The core of SPARKS is comprised of two primary components: an Identity Wallet and a Service API. These tools allow you to assert ownership over Web2 and Web3 accounts you already control by claiming credentials, bringing together otherwise siloed attributes. This gives potential to make all your attributes useful everywhere, letting you extract more value from your own identity.

Identity Wallet

The identity wallet is the interface by which the user will build and use their identity. The user will be able to simply create an identity and go through attestation flows to claim credentials. Once credentials are claimed they can choose to present those credentials to peers which can be other people, applications, hardware etc.. The wallet will feature:

• User stored identity and credentials.
• Offline first, server-less progressive web app.
• Fee-less off-ledger identity creation.
• Password driven with rotation and device syncing.
• UI for claiming and presenting credentials.

Identity Service API

The identity service layer will allow Identity holders to claim credentials via attestation flows, present credentials with verification flows and contribute responsibly to data sets for insights.

Credential attestation flows

• one time passcodes to prove ownership of mobile phone number, email...
• challenge / verification to prove ownership over public web2 assets like Twitter, Medium, Domain, YouTube...
• digital signatures to prove ownership over accounts driven by public key such as EVM, PGP...
• claim & issue to claim credentials issued by a trusted party for anything like reputation, experience, etc…
• Verification flows
  • attribute predicates to verify you meet conditions without sharing the data directly for example: over 18, follows @sparks_dao on Twitter, has at least 3K GitHub contributions…
  • selective disclosure to share parts of your data needed for the interaction but nothing more for example: just the domain of your email, your Twitter follower count…
  • predicate verification proofs to make the attribute predicate verifications portable offline via P2P and even across blockchain systems.
• Insight flows
  • user data contributions stored via secure hashes, data splitting and statistically insignificant randomization.
  • service data consumption accessed via aggregation and minimum data set requirements depending on use-cases.

History of Identity

Get Involved!