FAQ
A DApp Service defines and manages APIs and resources that are needed to implement various features using contracts, tokens and more on the blockchain in a specific application (web/mobile/desktop application, etc.). For more information on how to use this service, go to [User Guide > Using Luniverse]
Luniverse plans offer Chain Service, Token Service, DApp Service, and User Management Service. The same services are provided in all plans, but the chain specifications vary depending on the plan. We recommend choosing plans that consider the characteristics of the services as explained below.
- Dev Plan
- Suitable for building a development environment for blockchain DApps, B2B services with lower traffic, or early-stage services.
- Service Plan
- Suitable for building and operating a general blockchain DApp service.
- Premium Plan
- Suitable for building and operating a blockchain DApp service with higher traffic and increased activity such as games. The plan selected for the chain can be conveniently upgraded as necessary. (The chain upgrade feature will be supported soon.)
You can use up to 3 REOAs and 10 IP Whitelists per DApp.
Only one MT can be linked and used on each Side Chain. In addition, only one Side Chain can be linked and used with each MT.
A Side Chain consists of two Validator Nodes and one Monitoring Node. You can create and use as many nodes as you want for the purpose of maintaining governance, enhancing stability, etc., and more features such as governance of the Side Chain will be additionally developed and introduced in order. (The feature to create nodes will be updated soon.)
Luniverse supports a delegation contract to help various participants in the Side Chain manage their balance more conveniently for all gases they need to pay for by using the Main Chain. The Organization Owner may recharge all gases required for the operation of the Side Chain by recharging LUK in the Gas Delegation Contract of the Side Chain. Fees for the gases used by the members of the organization will be paid through the delegation contract. The Organization Owner may recharge all gases required for the operation of the Side Chain by recharging LUK in the Gas Delegation Contract.
Currently, up to Solidity v5.0 is supported in the Luniverse Side Chain. Solidity v5.1 or later versions are temporarily unavailable. Please deploy a smart contract created in Solidity v5.0 or earlier versions.
After creating a side token, use Redeem transaction in Dapp -> transaction management menu to convert to main token. You must inquire separately for the main token API.
Currently, we are preparing the function to delete DApp after creation. However, since there is no limit on the number of DApps, you can create additional DApps.
You can use it after directly writing and distributing a contract that exchanges side tokens. Take a look at the contract code attached below.
https://github.com/bokkypoobah/TokenTrader/blob/master/contracts/TokenTraderFactory.sol
You can use it after directly writing and distributing a contract that exchanges side tokens. Take a look at the contract code attached below.
https://github.com/bokkypoobah/TokenTrader/blob/master/contracts/TokenTraderFactory.sol
In the case of Validator nodes, three are required for initial registration. There are plans to add, delete, and change nodes, but they have not been implemented yet. However, even if the function is implemented, there will be restrictions in dynamically adding and deleting because voting of other validators is required even in the geth stage when replacing validators.
Tx API is assumed to be called by the DApp Backend server. Therefore, the IP address of the DApp Backend server can be registered and used through the IP Whitelist management menu. Also, we check the permission of the DApp based on the DApp API Key.
1. Snapshot method
2. Collection after issuance of virtual account is possible in two ways.
Details on the procedure can be found in the User Guide.
You can view the related source code here on Github. https://github.com/Lambda256/luniverse-poa