External master node for Karbo cryptocurrency allows drastically decrease time-to-start for light and mobile wallets
Hi! You've discovered one of Karbo master nodes. Karbo positions itself as a decentralized exchange medium with strong team of developers, so it basically have all chances to become top-used cryptocurrency. That resource is commited to cryptonetwork maintenance.
Current master node version:
Current blockchain height:
For now Karbo has 4 types of wallets: command-line (CLI), classic (GUI), light and mobile.
For CLI and GUI remote node is just a useful option for boosting up synchronization process and saves your HDD space :) But for light and mobile wallets it's a must-have feature as a blockchain is pretty heavy.
"How to use" for each type:
For wallet operation CLI contains utility called simplewallet. Simplewallet has an argument --daemon-address for working with remote node, e.g.: simplewallet.exe --daemon-address karbo.xyz:32348.
You can run simplewallet.exe --help for more details (same args for both Windows and Linux).
You can switch GUI to remote node in "Settings - Connection" by selecting "Remote daemon" option. After that you need to press "Add node" and write "karbo.xyz" in "address" field. After saving the new remote node you can select it in previous window.
You need to restart software for applying changes!
For changing default remote node you need to open "Settings - Preferences", check that "remote daemon" mode is selected and write "karbo.xyz" as a host. After wallet's reload (runs automatically) you will be connected to external node.
For switching that wallet to remote node you need to open "Settings - Preferences", select "Remote daemon" option and set karbo.xyz as a "Host". After pressing "Save" button wallet will automatically shut down. From next startup you will work with remote node.
For mobile wallet remote node is the only possible option to operate. If you want to change default remote node (defined by developer) you need to go into "Settings - Connection" and set "karbo.xyz" as a host. After that you can switch the toggle "Connect to your own server".
For other enthusiasts I've developed scripts for node dockerizing ( container, compose). There is a manual how to use it.
My recommendation is to use docker-compose - it's much more easier in deploying and maintaining. Instruction can be found in repository itself.
Feel free to ask :)