Some time ago, we announced our partnership with the Algorand Foundation with the goal to facilitate businesses to transfer their infrastructure, assets, and processes to the blockchain on a large scale.
The Algorand integration via AIKON’s ORE ID brings us one step closer to achieving our shared goal of having 100 million first-time blockchain users by 2025. And while it may seem extremely ambitious and far-reaching, we are guided by the belief that end-users do not need to have a deep understanding of the blockchain technology in order to use it and get accustomed to all the ways their lives are facilitated by it.
Safe in the knowledge that their identities are secure on the cloud with AIKON’s ORE ID and ORE Protocol, all financial entities can take part in the frictionless DeFi space with their Algorand wallet.
In fact, with ORE ID, users can utilize their social logins and email addresses to access the blockchain – without installing apps of browser extensions – and authorize transactions without leaving the app. Included are the most popular OAuth providers: Google, Facebook, GitHub, LinkedIn, Twitch and Twitter.
Moreover, bearing in mind that people, in general, tend to have issues with holding on to their passwords and private keys, the integration allows users to create multisig wallets and therefore prevent losing their assets in the blockchain ether. The ORE ID integration makes it easy to use the Algorand blockchain without exiting their applications.
Here is how it all works.
Run the ORE ID Sample APP
Pulling down and running the ORE ID sample app – on the Algorand blockchain – on the (company) user’s local machine will show you how the ORE ID works for the end-user.
First, it’s necessary to set up the environment by cloning the sample app repo and navigating to the Algorand example folder. This is followed by creating an .env file for the sample app which will hold App ID, API Key, and other relevant app deployment elements.
After deploying on the local machine and launching the React app from the browser, the user will now be able to login with a preferred OAuth platform and access their Algorand wallet with the help of ORE ID integration.
Note that ORE ID supports various blockchains aside from Algorand, like Ethereum, EOS and WAX.
After that, all that’s needed is to verify the account and it will become visible to the user on the block explorer. It’s important to test sign the transaction by updating the signing flow with the current value and rerunning the local instance to complete this process.
Create an ORE ID Application
The first step is to log in to ORE ID and create a company developer application. Afterward, there will be available the option to choose which social logins end-users will be able to perform authentication with to access their multisig crypto wallet.
The next step is setting up the environment – sample application files should already be on the local machine as a result of the steps taken in the previous section. After duplicating the .env example file (from the Sample App configuration) in the same folder and renaming it .env, the example App ID and API Key should be replaced with unique keys generated for a particular app that can be found on the ORE ID dashboard.
To complete the process of safely accessing the Algorand multisig wallet, the react app should be launched in the browser. It can then be accessed with any of the OAuth social platforms (outlined in the previous section).
Test the Algorand ORE ID Integration
After creating the app, to test the integration, it’s required to log in to the app’s developer dashboard on ORE ID.
In the Settings>Platforms Tab, each social media platform has the option to be tested for authentication and granting access to the Algorand wallet.
Once the test modal is shown for the chosen platform, a callback URL must be selected to generate a test link which is valid for only two minutes.
Adding new transactions to the whitelist table requires them to be tested, which can be done from the ORE ID Developer Dashboard by clicking on the Test Transaction button.
Again, a callback URL is needed to generate a test link and the test can be run by either clicking the Run Test button or manually copying the test link into the browser’s search bar.
Finally, this is where it can also be determined whether transactions (with Algorand coin and others) are to be broadcast to the chain and tested by signing with an external wallet.
Now that you’ve seen how easy it is to set up a wallet and manage keys with the ORE ID / Algorand integration, what are you waiting for? Get on the bandwagon!