Frequently Asked Questions

What kind of apps can use ORE ID

Our goal is to make it easy for everyone - developers and users to benefit from blockchain technology. Here are a few examples:

1 - DApp developers who are building on or want to build on EOS are an optimal use case. An example is ( which is an iOS and Android mobile app with a backend of EOS smart contracts and using ORE ID for user login and identity.

2 - A traditional web (or mobile) app that has no blockchain component can use ORE ID to provide an easy way for users to use the app’s own in-app currency or asset wallet

How much work is it to on-board a new app with ORE ID?

It’s a Simple app registration process - a single entry in our database and you will soon have an online registration flow for your users. Request early access via this form:

Where do the accounts created by ORE ID live?

Accounts created by ORE ID are native EOS accounts. They can be created on the EOS main net, test net, or any sister chain (like Telos, Worbli, or ORE network). ORE ID maintains additional data about a user that maps their online identity (e.g. Google, Facebook) to their EOS account. Any software wallet that supports EOS can see the user's account and balance(s).

If I use ORE ID to create my own crypto-currency, where is it and how do users use it?

Currencies created by registering your app with the ORE ID solution are standard EOS tokens residing on any EOS chain or sister network. The currencies are accessed just like any other EOS currency - usually via a software wallet (like Scatter). Only the owner of the account (the holder of the ‘wallet’ password) can send transactions from the account.

Who has access to the ORE ID accounts’ private keys?

During the creation of a new EOS account, the user enters a password that is used to encrypt the private key. Only the encrypted result is stored. The unencrypted private key and password are never stored anywhere. Only the password holder can sign transactions or send funds from the account on its behalf.

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.

Can users use a software wallet to control their accounts (and private keys) created using ORE ID?

Yes! ORE ID makes it easy for users to have their own EOS account on the ORE blockchain. After their account is created, it can be exported using a trusted encrypted file format directly into a software wallet (using the standard Transit Wallet Interface which supports Scatter, Ledger Nano S and other popular wallets). The user is in full control of the account and can perform transactions directly from the wallet just like any other EOS 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(s) - 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.

How can accounts created (via ORE ID) on the ORE blockchain or another Sister Chain (like Telos) be used by other blockchain dApps or regular applications.

Accounts and currency balances on the ORE blockchain is queryable like any EOS account. You just need to know the chain address (the ORE blockchain address is If a dApp is running on the main EOS chain (or any EOS chain) it can access the accounts directly using Inter-blockchain communications which is part of the design of the EOS network.

Why is using ORE ID better than just creating accounts on the main EOS network

The ORE blockchain is only used for accounts, identity, and rights management tokens. We don’t host general purpose smart contracts so the demand (and cost) for resources on the network is more stable and predictable than the main EOS network (that is more general purpose).

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 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?

We offer an easy to use javascript NPM module and sample apps for common architectures including Express, ReactJS, and React Native. In addition, the ORE ID HTTP-enabled API is simple and can be used by any technology stack. The libary and sample apps are described here:

What does it cost to create accounts using ORE ID

Our token-economics model is similar to EOS where the demand of the network will affect the price of creating accounts on it. But, it will be less volatile than the primary EOS network. We’ve announced our initial pricing (see announcement) but in general, the cost of creating an account on the ORE chain is a small fraction of what it will cost on the main EOS network. Of course, ORE ID supports creating accounts on the EOS Main Network. Pricing for creating these accounts varies by demand for the ORE token and cost of RAM on the network, but we offer a pricing model to buy a group of accounts in a block for a fixed price.

How does the ORE blockchain (and ORE ID) interact with the Eos main net?

ORE is an EOS ‘sister chain’ which means it runs the same EOS.IO software as the primary EOS network - it is just configured as a separate network. The EOS software is architected to provide inter-chain communications between multiple EOS networks - a feature to be released later this year. After this feature is released, contracts and accounts on the main chain will inter-operate natively with the ORE blockchain. Until this feature is released by the EOS.IO team, we support interoperability with other chains using the same approach as interoperating with other blockchains.

Does ORE work with Ethereum projects and other blockchains?

User accounts and tokens (including your own app’s custom currency) created with ORE ID reside on an EOS blockchain. Transactions that affect token balances (transfers, trades, purchases, staking, etc.) take place in contracts on the same chain and are replicated to other chains using an off-chain Oracle. We also use an approach designed to trade tokens across blockchains (those that enable ‘atomic swaps’) to ensure that transaction on the ORE network have an audit trail on an established, trusted network (Ethereum, EOS main network, etc.)

Do developers 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 service.

How is this different than OAuth?

ORE ID uses OAuth to connect the logins people use every day to the blockchain. It uses OAuth to start the login process then creates an account for the user and maintains a record that includes a ‘pointer’ to the user’s blockchain account.