https://stamp-protocol.github.io/
Effectively, this is a key management system that allows building and signing ("stamping") various claims about yourself and about others. The eventual goal is to create easy-to-use implementations of the protocol that allow logging in to websites or managing cryptographic keys for various security-conscious applications. Secure, simple distributed key management for cryptography and identity management.
Currently Stamp uses crypto primitives found in libsodium, but is also built such that different algorithms can be added as needed.
The identity itself is set up as a DAG which is appended to by signing transactions with an opinionated set of keys. A DAG was chosen so parallel offline updates could be made and merged later. One of Stamp's main features is it allows recovery of the identity via a pre-determined recovery policy, using signatures from trusted keys (friends, family, institutional providers). Think of it as sort of a multisig recovery mechanism.
A few things I'm actively exploring:
- A storage network (https://stamp-protocol.github.io/#arch-stampnet). This would necessarily need to be some sort of p2p system, and hopefully not blockchain-based as I believe the consensus/validation used in blockchain systems are superfluous to identity storage and retrieval.
- Putting stamp on USB keys/embedded devices (ARM TrustZone, RISC-V PMP, etc) so it can be used in more trusted environments.
- Some sort of FIDO2 interop would be great so Stamp could act as a login system without having to re-tool a bunch of stuff.
There's also a somewhat-incomplete CLI implementation of the protocol here: https://github.com/stamp-protocol/cli. This allows creation of identities, creating and stamping claims, automatic verification of certain claims (www/DNS), as well as cryptographic messaging/signing tools.
Let me know what you think! What's good, what's bad, what's missing, etc. Obviously it's early days so more feedback is better.