Threely and Other DIDs
At Threely, we harbor a steadfast conviction that current approaches to Web3 authentication and fiat integration fall short of fully onboarding users to the vast possibilities of the decentralized Web3 ecosystem. We refuse to accept the status quo of confining users to a single blockchain and compromising the composability of on-chain wallets. Instead, we are committed to pushing the boundaries of user onboarding and setting a new standard for seamless access to the more than 300 existing blockchain protocols, all while maintaining a superior user experience and fostering true wallet composability. Our philosophy is one of collaboration, not competition, as we strive to serve as a catalyst for growth across the world of Web3.
We are driven by a vision of a future where Web3 brings people and organizations together for a cause. By fostering collaboration and co-existence, we believe we can create an inclusive and diverse ecosystem for all parties involved. Below is a TLDR version of the Threely Identities platform in comparison to other Identity providers.
| Feature set | Threely Identity | Status Quo |
|---|---|---|
Universal and blockchain agnostic Identities ↗ | Yes | No |
Support other DIDs via wrapping ↗ | Yes | No |
Composability and co-existence with other open-source DID stacks ↗ | Yes | No |
Hyper-local community-focused use cases for dApp, DAOs, NFTs communities, teams, causes, smart contracts, and more ↗ | Yes | No |
Login to dApps with Identity ↗ | Yes | Some |
Inherited KYC Signature/Solution ↗ | Yes | No |
Data transportation like broadcasts, messages, notifications, and payments are inherently built ↗ | Yes | No |
Get more support
Tell us about your project, and ask us any technical questions you have.
To integrate, use our Integration form
To chat with us, shoot a message on Telegram, Discord or email us at hello@threely.io
Something missing?
If you find issues with the documentation or have suggestions on how to improve the documentation or the project in general, please submit a request (Canny) for us on our feature requests board. This allows us to triage issues appropriately, track demand across users, and align requested changes with our roadmap - which is also featured on Canny.
Last updated