Nodes that store all of the blockchain are called “full-nodes”. They are connected to the blockchain through a P2P network. All the nodes in the blockchain network are equal, they act both as a client interface and as a server.
There are two full-node programs:
- Krona-GUI, which has all the basic functions of a user-client including a graphical user interface and is intended for Krona users.
- Krona-CLI, which provides an external API for basic wallet functions and is intended for XKNL developers. It also helps other nodes achieve consensus with the network and is involved in generating new blocks.
The Krona network protocol provides a low level API for some transaction types that are not currently supported by the CLI, such as sending XKN without an open wallet.
Krona client download address
GUI node and CLI node functions comparison
|Command Line Interface||✅|
|Reconstruct Wallet Index||✅||✅|
|Show all key pairs||✅||✅|
|Import/Export Key Pair||✅||✅|
|Show all addresses||✅||✅|
|Create a multi-party signature contract||✅|
|Create a custom smart contract||✅||✅|
|Election Consensus Node||✅|
|Batch Generation Address||✅|
|The consensus of the participating blocks||✅|
Krona-CLI security policy
To enable an external program to access the node API, you need to open the firewall port.
To avoid the significant security risk, a whitelist or firewall must be used to block external server requests.
Krona-CLI does not provide the function to remotely switching on/off the wallet, and it does not verify the process when opening a wallet. Therefore, you should set your own security policies. The wallet must be kept open all the time to respond to the withdrawal requests of users. For security reasons, the wallets should be run in an independent server on which the firewall is configured properly, as shown below.
|Main Net||Test Net|
|JSON-RPC via HTTPS||10331||20331|
|JSON-RPC via HTTP||10332||20332|
|P2P via TCP||10333||20333|
|P2P via WebSocket||10334||20334|
For more information, please refer to test network .