Luniverse Developer
Luniverse Developer-eng
Search…
⌃K

1.5 API Upgrade Guide

How to Pre-upgrade API to 1.5 Compatibility Mode

When the Luniverse 1.0 service terminates, the 1.0 and 1.1 API services terminate as well. We provide the 1.5 API to allow you to use the existing API with minimal changes. 1.5 API operates in compatibility mode in Luniverse 2.0 service, not 1.0 service.
The content below will guide you on how to pre-upgrade to Luniverse 2.0 through the 1.5 API:
Please proceed to pre-upgrade Luniverse 2.0 as below:
  1. 1.
    Notify a Lambda 256 manager of your pre-upgrade process.
  2. 2.
    Check the list of Luniverse 1.X API you are using.
  3. 3.
    Send the list of Luniverse 1.X API you are using to lambda 256.
  4. 4.
    Change the Luniverse 1.X API to the Luniverse compatible 1.5 API.
  5. 5.
    Test changed API calls.
  6. 6.
    Reflect (deploy) the changed contents to the service.

Notify a Lambda 256 Manager of Pre-Upgrade Process

If you decide to proceed with the pre-upgrade, please inform your Lambda 256 manager. The manager will assist you with the process.

Check the List of Luniverse 1.X API You Are Using

1.X API provided by Luniverse is as follows:
  1. 1.
    TX (Side Chain Transaction) API
This is an API to control resources on the side chain. 1.1 Tx API document could be found here.
2. MX (Main Chain Transaction) API
This is an API to control the resources of the main chain. 1.0 Mx API document could be found here.
3. BE (Luniverse console backend) API
This is an API used in the Luniverse console and is not intended for external public use; however, there are cases where it is being used by a separate request. If you have an API that starts with a URL like the one below, please report to Lambda 256. If the 1.0service is terminated, it may not operate normally.
https://api.luniverse.io/be/

Send the List of Luniverse 1.X API You Are Using to Lambda 256

If you have checked the list of Luniverse 1.X APIs you are using, please send it to the Lambda 256 manager. If you have already sent it, you can skip this step.
If you do not have any Luniverse 1.X API in use, you do not need to go through an upgrade process. Please use the Luniverse 2.0 console right away.
Lambda 256 will contact you if there are any special issues in the list of Luniverse 1.X APIs you are using. If there is no contact, please proceed directly to the next process.

Change the Luniverse 1.X API to the Luniverse Compatible 1.5 API

1.0 MX API

The MX API does not require an upgrade.

1.1 TX API

Change only the version value of the existing call API path from v1.1 to v1.5 as shown below:
https://api.luniverse.io/tx/v1.1/~
https://api.luniverse.io/tx/v1.5/~

(1.0) BE API

Add prefix tx/v1.5/ in front of “be” in the existing calling API path as shown below.
https://api.luniverse.io/be/~
https://api.luniverse.io/tx/v1.5/be/~

Testing Changed API Calls

Test the changed API calls.
Please inform the Luniverse manager when you are ready to test.
The test order is as follows:
  1. 1.
    Create EOA for the test (important).
  2. 2.
    Change and call the API.
  3. 3.
    Proceed with the test and check the results.
  4. 4.
    Inquiry and feedback about call failure (Lambda 256).
If you request a test run to the Lambda256 manager, we will respond as soon as possible for the call.
Cautions
You cannot use 1.0, 1.1, and 1.5 APIs simultaneously for the same EOA.
There is a problem that nonces conflict with each other because the nonce grant module of the 1.0 service and that of the 2.0 service differs.
Please proceed with the test by creating an EOA for the test and ny changing all the existing APIs to 1.5.
A problem occurs when you call the 1.0 and 1.1 APIs again after calling the 1.5 API.

Checking the Result

Check the result via scans.

Reflect (Deploy) the Changed Contents to the Service

When the test is complete, reflect the changed API.
If you have any questions about the guide or the process, please contact us. We will respond as quickly as possible. Thank you.