Provide your dApp users with a simple account creation experience using everyday logins like GMail, Facebook, SMS and more.
Simplify Your Login Experience
ORE ID is a single sign-on identification platform that works cross-chain.
With ORE ID, users of your web or mobile app easily create an on-chain account upon first sign-in. Their private key is encrypted with a PIN of their choosing and stored for them — so your users never have to remember their blockchain accounts or keys.
ORE ID removes the friction between your app and your future users.
Our open-source libraries support any blockchain
Create an ORE ID account in 24 seconds through OAuth
Save months of dev work with a powerful API library
End-to-end encryption protects your user’s account
Easily track user adoption and retention
Users own their keys across any chain
Join ORE ID Customers
ORE ID supports all of the major OAuth providers for your app, email and SMS logins.
Get ORE ID Today
- Up to 1,000 active users
- Eight popular social logins, including Facebook, Github, Telegram and Twitch
- Best option for over 5,000 active users
- SLA 99.9% uptime guarantees
- Email & SMS Logins
Designed for Developers
ORE ID is the easiest way to add support for Scatter, Ledger Nano S, Metro and every other EOS wallet that supports the new Transit API standard.
Learn how to easily integrate ORE ID and instantly support these popular wallets.
Complete Data Transparency and Security
With end-to-end encryption and a hierarchical permission structure, your users — and their digital assets — are protected from malicious actors.
ORE ID has built-in data security GDPR and CCPA compliance bringing the latest security technology to the hands of your users.
Join the AIKON Telegram Community
Frequently Asked Questions
What kind of Apps can use ORE ID?
Our goal is to make blockchain easy for everyone. Here are a few examples:
- App developers who are building on or want to build cross-chain are an optimal use case. An example is Everipedia which is a modern web app with a backend of EOS smart contracts and is using ORE ID for user login and identity.
- A traditional web or mobile app that has no blockchain component can use ORE ID to provide an easy way for users to leverage the app’s own in-app currency or asset wallet.
How do you protect private keys for the accounts you create with ORE ID?
The user must provide the password to send from their ‘wallet’ account. The account info (including the encrypted key) can be imported directly to a software wallet without ever exposing the private key. We currently support the Transit Wallet interface which provides integration with a range of popular wallets (like Scatter and Ledger Nano S). Software wallets (like Scatter) can be used to sign and send transactions from the user’s account.
You’re using Google and Facebook as authentication providers. Doesn’t that make my private key hackable?
No. We are only using these providers as a way to help users connect to your app. Once their crypto account is created, only the account’s public key is associated with those account(s). This association is not public. The user must enter a separate password to protect the accounts’ private key – the account is not ‘controlled’ by these other account providers in any way. If your Google account is hacked, the attacker would still need to know your crypto account’s separate password to access it.
If a user has an account created with ORE ID, how will they be able to sign a transaction for my app?
ORE ID offers a simple web service for you to request that a user wants to sign a transaction. Your app simply calls the /sign endpoint on ORE ID and passes in the JSON representation of the transaction to be signed. ORE ID validates that the user has signed-in using his OAuth identity, then requests that he enter his wallet password. The signed transaction is then returned to your app.
ORE ID protects you and the user by ensuring that only the user who controls an EOS account can sign a transaction using its authority. ORE ID provides a simple way to whitelist approved contracts and actions to prevent malicious apps from tricking the user. ORE ID also uses the EOS hierarchical account permission model to ensure that the app requesting the user’s signature has the right to request the action and permission specified in the transaction.
How hard is it to add ORE ID to my app?
Do I need to understand blockchain technology to use ORE ID?
Any Dapp or traditional App that can call an API can use ORE ID. Although we use blockchain technology to deliver this service, developers do not need to know how to write smart contracts or develop any blockchain code to leverage ORE services.
How is this different than just OAuth?
ORE ID uses OAuth to connect the logins people use every day to the blockchain. The major difference is that ORE ID also handles secure wallet creation, which blockchain users also need to be able to interact with blockchain dApps.