Threely Enter (Onboarding)
Onboard users to dApps without wallet and KYC friction points
Current onboarding to dApps with wallets is an intimidating and time-consuming flow decreasing conversions by up to 64%. Threely lets dApps onboard users instantly to dApps without the friction point of connecting a wallet using an extension or a crypto wallet at hand. Threely enables users to authenticate and share their reusable zkKYC securely using decentralized logins with their Threely addresses.
To sign a transaction, the user is first authenticated by a decentralized login to Threely. The concerned wallet is identified, and its time-limited ADS access token is generated and retrieved from Threely Networks Layer (TNL), a decentralized computational layer.
Then, a Transaction Sign Function runs inside the TNL in a decentralized trusted execution environment. The function uses the access token to retrieve the encrypted PK from the Access Data Store (ADS) (encrypted decentralized storage) and the transaction details to be signed from the dApp. Then, the PK is decrypted using the user password to sign the constructed transaction. The signed transaction is returned to TNL to be broadcasted to the blockchain.
The user’s private keys are never exposed to the client machine or outside a secure environment, and it also means that no one, including any process run by Threely or the user device, has a possible access path to any of the user’s private data. Alternatively, new wallets are automatically created when signing a function to enable access control and revoke functionality if enabled.
Tell us about your project, and ask us any technical questions you have.
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.