ORE ID Updates — October 2019 & Stats

The team at AIKON has been hard at working building scalable solutions and features improving our ORE ID product offering to be the simplest tool out there for any company looking to adopt blockchain solutions and to provide an onboarding integration for developers building their next Dapp.

In turn what ORE ID also provides for end users is a completely seamless experience accessing and using Dapps, just like any app they are already used to, with the complicated blockchain mechanisms working behind the scenes and hidden from sight.

The following are some of the new features we’ve launched recently.

Auto-sign

ORE ID customers can now grant permission for their app to sign transactions on their user’s behalf so users won’t need to confirm each similar transaction with their PIN.

This is a great feature for apps that require frequent similar transactions in order to interact with the app, like making edits on Everipedia, or when trading assets in a mobile game.

The default duration this lasts for will be displayed in the tool tip, after which you will be required to enter your PIN again and enable auto-signing.

Sign in with Apple

As a service that offers a variety of social login options, we were excited to hear that Apple would be providing a login option themselves a special feature that protect a user’s privacy by obscuring the email given during. For us in the blockchain space, that was music to our ears, and if that sounds good to you as well, any ORE ID customer can now enable Apple as a sign in option for their users.

Connecting Logins

ORE ID end users now have the option of connecting extra logins. When you connect your other logins to your ORE ID account, you’ll be able to manage your access to any other ORE ID enabled Dapp all under the same account for the social logins you have connected.

For example, if you created your ORE ID account using a Facebook Login, and later you connect Google and Twitter, you can log into new Dapp using any of the 3 logins, all managed under the same ORE ID account.

EOS REX Implementation

Especially relevant now with EOS and the congestion issues the mainnet is facing, we have implemented REX that allows ORE ID customers to spend far less EOS in the form of staking resources for their users. You can read more about REX and how it works here.

First Authorizer

If you’ve been following EOS or are an active participant in using EOS based dapps, you’ll know that the EOS mainnet over the past several months has been put through the ringer by various parties resulting in the severe congestion in the network making things difficult for the average user to even interact with the chain.

We at AIKON have always prioritized User Experience since the beginning, and have supported the very same notion, so right on the heels of our REX integration we’ve also adopted one of these new EOSIO upgrades from the recently launched version 1.8, which allows anyone to pay for resources on behalf of anyone else, the First Authorizer feature. With this feature we move one step closer to an ideal and seamless user experience that mainstream adoption is waiting for.

By the way, we also have a new Block Explorer

If you’ve been following our progress, you may have used our old block explorer in the past to look up accounts or our BPs. Because of our recent integration with the awesome APIs by dfuse, we adopted their high performance block explorer as well. Check it out here.

ORE ID Stats

By the way, here’s some ORE ID stats for you as of 11/07. We’re over 20,000 accounts and 95k+ transactions, with 75k+ within the month of October alone and things are still heating up!

Join the community: want to stay ahead of the news? Join our email newsletter, and telegram channel for updates.

Leave a Reply

%d bloggers like this: