July 2023

Change Log for ORE ID

Key Exporting is Now Available

Summary

This month AIKON released the long-awaited Key Export Feature for ORE ID. As a sign of our commitment to decentralization and user agency, we’re making it easy for any user of an ORE ID product to take full control of their blockchain assets. This update also improves the usability of the ORE ID API with some new features and a patch to fix some recently discovered bugs.

Changes

• (Feature) Key Exporting

  As of this update, users now have the option to Export their private keys from the ORE ID Ecosystem, gaining full and sole control of the assets that key controls. This enables the keys to be imported into any compatible wallet.

  To access this functionality, users will need to navigate to their ORE ID profile page at OREID.io. From our login page, customers can use our standard social login or an email address to be taken to their profile. From here, they can review all of the ORE ID wallets attached to that account and may export those keys if they wish.

  You can find a more detailed explanation of the process in our documentation.

  If the user has benefited from a promotional program that allowed them to create a wallet for free, they will need to cover the cost of creating that wallet before exporting it from ORE ID.

• (Feature) Validate Transaction

  The Validate Transaction API endpoint ensures that a transaction is properly formed and will be accepted as valid by the API and the blockchain network. This endpoint is useful for developers who wish to avoid creating a transaction that will potentially fail or linger in the blockchain memory pool.

Validate Transaction

POST https://service.oreid.io/api/transaction/validate

Checks whether a transaction can be signed (via Custodial - Sign Transaction) without requiring user intervention

Request Body

Name	Type	Description
transaction_chain_account	String	The 12-character account name associated with the transaction (the transaction actor) for the chain specified by chain_network. Usually the same as the user’s ORE account but can be different for different chains.
chain_network*	String	eos_main, eos_kylin, etc. Valid options can be found in the Get Settings - Chains Config API call results
encoded_transaction	String	Base64 encoded JSON of the transaction.
transaction_options_stringfield	Object	An object that includes chain and transaction-specific options.
transaction_recordId	String	ID for the transaction record.

200: OK Transaction Analyzed

The transaction has been analyzed and the response will give you details about its status.

400: Bad Request Transaction not Analyzed

There was a problem validating the transaction.

Full Documentation

• (Feature) Validate Payer

  ORE ID App developers can use the Validate Payer API endpoint to validate that transactions can successfully be completed by the designated payer. A successful result confirms that the paying wallet actively controls the funds that are required by the transaction.

Validate Payer

POST https://service.oreid.io/api/transaction/validate-payer

Verifies that the designated payer of the transaction has access and permission to the funds required to complete the transaction.

Request Body

Name	Type	Description
chain_network*	String	eos_main, eos_kylin, etc. Valid options can be found in the Get Settings - Chains Config API call results
encoded_transaction	String	Base64 encoded JSON of the transaction.
transaction_chain_account	String	The 12-character account name for the receiving address of the transaction.
payer_chain_account*	String	The 12-character account name associated with the party that is funding the transaction.
transaction_options_stringified	String	An object that includes chain and transaction-specific options.
transaction_recordId	String	ID for the transaction recor

200: OK Transaction Analyzed

The transaction was successfully analyzed and the fees and resources required for the transaction have been calculated.

400: Bad Request Transaction Not Analyzed

There was an error in the request and the transaction was not analyzed.

Full Documentation

• (Update) Onramper Upgraded to Version 2

  The UI for the Onramper widget has been updated to version 2. This change will be applied automatically for anyone who implements Onramper through ORE ID. The implementation process will remain the same.

• (Bug Fix) Repeated Password Creation Dialog Removed

  An error where visitors to the Developer Portal were asked repeatedly to create a new password has been fixed.

• (Bug Fix) Login Issue with Google Auth Fixed

  An error that caused Google Authentication to occasionally fail when a user tries to log in via the ORE ID API has been fixed.

• (Bug Fix) Issue with Token Purchases Fixed

  Fixed an error that prevented token purchases from being made via a debit card transaction.