Luniverse User Guide

루니버스 사용을 환영합니다!
이 페이지에서는 루니버스 서비스 사용 가이드를 제공합니다.
루니버스를 사용하여 다양한 디앱(DApp)을 제작해보세요.

Welcome to Luniverse!
This page provides a guide to using the Luniverse service.
Try to create various DApps by utilizing Luniverse.

Get Started

Creating a Transaction List

Create a transaction list to integrate with a DApp. Generating an API key will make the integration with the DApp easier.

Luniverse provides [Transaction List] where individual functions for the user contracts and side token contracts that you wish to use in a DApp can be combined as a list and used for automatically generating a Restful API key.

When a DApp is integrated, you can easily apply the desired token economy to the service by calling the generated Restful API key.

Navigating to the Transaction List page

  1. In [Console], click the DApp for which you wish to create a transaction to go to the [DApp Overview] page.
  1. Click [Transaction List] on the left menu to go to the [Transaction Management] page.
  2. On the Transaction Management page, click [+ Create Transaction] to go to the page that you can create a transaction.

Creating a transaction by calling functions from a user's contract

  1. Token/Contract: User contracts and tokens that can be used for creating a transaction API are shown in a drop-down list. In this example, choose the contract you want to use to create a transaction API.
  2. Function: Functions with which transactions can be made from the selected contract are shown in the drop-down list. Choose the function you want to use to create a transaction API.
  3. Action Name: Set the name of the transaction. 3 to 20 alphanumeric characters and some special characters are allowed.
  4. Description: Enter the description of the transaction. The description can be written in Korean or English.
  5. Parameter (optional): Enter an initial value if there is a parameter value requiring an initial input. If there is no parameter requiring an initial input, the message “There is no function parameter” appears.
  6. When you finish entering the information as described above and click [Create], the message "Transaction created. Now you can apply the transaction to your service." appears in the pop-up window.
  7. Click [OK] to go to the [Transaction Management] page.

Creating a transaction by calling functions from a side token contract

This process is to create a Restful API corresponding to the functions included in a Side Token contract.
The created transactions will be bound to the corresponding Side Token as they are based on the features of the ST contract.
For example, when a simple transfer transaction that is created based on the Side Token “A” is executed, the ST A will be transferred.

Free Simple Transfer

Free Simple Transfer is a simple token transfer transaction for which no fee is charged.

  1. Token/Contract: User contracts and tokens that can be used for creating a transaction API are shown in a drop-down list. In this example, choose the ST you want to use to create a transaction API.
  2. Function: The five functions that can be called from the selected Side Token contract are shown in the drop-down list. In this example, choose Free Simple Transfer.
  3. Action Name: Set the name of the transaction. 3 to 20 alphanumeric characters and some special characters are allowed.
  4. Description: Enter the description of the transaction. The description can be written in Korean or English.
  5. Sender: Specify the sender of the transaction. A DApp REOA list appears as a top-down list that you can choose an REOA from, with the statement “Please choose wallet.”
    • Users may directly enter the EOA to call the API, instead of selecting an REOA from the REOA list.
  6. Receiver: Specify the receiver of the transaction. A DApp REOA list appears as a top-down list that you can choose an REOA from, with the statement “Please choose wallet.”
  7. Transaction Amount: Fix the amount of the STs to transfer when the transaction proceeds or choose to enter the amount when the API is called.
    • Fixed: Fix the amount of the STs to transfer when the transaction is called.
    • Flexible: Enter the amount of the STs to transfer when the transaction is called.
  8. When you click [Create], the message "Transaction created. Now you can apply the transaction to your service." appears in the pop-up window. Click [OK] to go to the [Transaction Management] page.

Paid Simple Transfer

Paid Simple Transfer is a simple token transfer transaction where a transaction fee is charged when the transaction proceeds. The paid fee will be sent to the EOA of the Member.

  1. Token/Contract: User contracts and tokens that can be used for creating a transaction API and have already been deployed to the chain are shown in a drop-down list. In this example, choose the ST you want to use to create a transaction API.
  2. Function: The five functions that can be called from the selected Side Token contract are shown in the drop-down list. Here, we chose Paid Simple Transfer.
  3. Action Name: Set the name of the transaction. 3 to 20 alphanumeric characters and some special characters are allowed.
  4. Description: Enter the description of the transaction. The description can be written in Korean or English.
  5. Transaction Amount: Fix the amount of the STs to transfer when the transaction proceeds or choose to enter the amount when the API is called.
    • Fixed: Fix the amount of the STs to transfer when the transaction is called.
    • Flexible: Enter the amount of the STs to transfer when the transaction is called.
  6. Transaction Fee: Fix the fee that is charged for the transaction or choose to enter the fee when the API is called.
    • Fixed: Fix the transfer fee to be charged when the transaction is called.
    • Flexible: Enter the transfer fee to be charged when the transaction is called.
  7. When you click [Create], the message "Transaction created. Now you can apply the transaction to your service." appears in the pop-up window. Click [OK] to go to the [Transaction Management] page.

Redeem to Main Token

Redeem to Main Token is a transaction where you can redeem the STs that were minted by pegging their value to the MT for MTs.

  1. Token/Contract: User contracts and tokens that can be used for creating a transaction API and have already been deployed to the chain are shown in a drop-down list. In this example, choose the ST you want to use to create a transaction API.
  2. Function: The five functions that can be called from the selected Side Token contract are shown in the drop-down list. Here, we choose Redeem to Main Token.
  3. Action Name: Set the name of the transaction. 3 to 20 alphanumeric characters and some special characters are allowed.
  4. Description: Enter the description of the transaction. The description can be written in Korean or English.
  5. Redeem Amount: Fix the amount of the STs to be redeemed for the MT or choose to enter the amount when the API is called.
    • Fixed: Fix the amount of the STs to be redeemed for the MTs when the transaction is called.
    • Flexible: Enter the amount of the STs to be redeemed for the MTs when the transaction is called.
  6. When you click [Create], the message "Transaction created. Now you can apply the transaction to your service." appears in the pop-up window. Click [OK] to go to the [Transaction Management] page.

Stake

Stake is a transaction that stakes the ST.

  1. Token/Contract: User contracts and tokens that can be used for creating a transaction API and have already been deployed to the chain are shown in a drop-down list. In this example, choose the ST you want to use to create a transaction API.
  2. Function: The five functions that can be called from the selected Side Token contract are shown in the drop-down list. Here, we chose Stake.
  3. Action Name: Set the name of the transaction. 3 to 20 alphanumeric characters and some special characters are allowed.
  4. Description: Enter the description of the transaction. The description can be written in Korean or English.
  5. Staking Amount: Fix the amount of the STs to stake or choose to enter the amount when the API is called.
    • Fixed: Fix the amount of the STs to stake when the transaction is called.
    • Flexible: Enter the amount of the STs to stake when the transaction is called.
  6. When you click [Create], the message "Transaction created. Now you can apply the transaction to your service." appears in the pop-up window. Click [OK] to go to the [Transaction Management] page.

Unstake

Unstake is a transaction that unstakes the staked STs.

  1. Token/Contract: User contracts and tokens that can be used for creating a transaction API and have already been deployed to the chain are shown in a drop-down list. In this example, choose the ST you want to use to create a transaction API.
  2. Function: The five functions that can be called from the selected Side Token contract are shown in the drop-down list. Here, we chose Unstake.
  3. Action Name: Set the name of the transaction. 3 to 20 alphanumeric characters and some special characters are allowed.
  4. Description: Enter the description of the transaction. The description can be written in Korean or English.
  5. Unstaking Amount: Fix the amount of the STs to unstake or choose to enter the amount when the API is called.
    • Fixed: Fix the amount of the STs to unstake when the transaction is called.
    • Flexible: Enter the amount of the STs to unstake when the transaction is called.
  6. When you click [Create], the message "Transaction created. Now you can apply the transaction to your service.” appears in the pop-up window. Click [OK] to go to the [Transaction Management] page.

Copying the transaction API from the transaction list

  1. In [Console], click the DApp for which you wish to create a transaction to go to the [DApp Overview] page.
  1. The created transactions are listed on the DApp Overview page.
  2. Click [API] on the right of the transaction from which you want to get an API key in the list to copy the Restful API key of the transaction.

Creating a Transaction List


Create a transaction list to integrate with a DApp. Generating an API key will make the integration with the DApp easier.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.