Client Setups
Running a blockchain node on LUKSO can be accomplished through different methods, depending on your experience level, use case, and available infrastructure. Whether you're looking for a simple setup or a more advanced environment with isolated containers, thereβs a suitable option available.
Setup | Difficulty | Description | Advantages |
---|---|---|---|
Platform to manage multiple blockchain clients using a preconfigured operating system and apps for node management and remote access. β DAppNode Staking Guide | - Graphical User Interface - Integrated Network Configuration - Includes Auto-Updates | ||
Command line interface to set up and maintain a LUKSO node in a home or server environment. β Server Configuration β CLI Client Setup β Client Modifications | - Simple Terminal Commands - Wide OS and Platform Support - Integrated Network Configuration - Runs All Supported Clients | ||
Container-based configuration to manage isolated nodes in a home or server environment. β LUKSO Docker Setup β Docker Configuration Factory β Docker Monitoring Setup | - Flexible Data Management - Runs Multiple Chains Simultaneously - Wide OS and Platform Support | ||
Custom client installation and setup using the public LUKSO network configuration. β LUKSO Network Configuration β Custom Client Advice | - Total Customizability - Wide OS and Platform Support - Runs All Supported Clients |
Currently, π¨ DAppNode only supports Geth as execution client, further decreasing the Client Diversity of the LUKSO Network. If you're technically skilled, consider an alternative setup using the LUKSO CLI or Docker.
None of the setups does restrict modification of the underlying blockchain clients. A whole suite of flags and settings can be added during startup or within configuration files to change service behaviour as described in the Modification chapter.
- π¨ DAppNode: You can pass down the
--<flag-name>
within the EXTRA_OPTS field of the client page. - πΎ LUKSO CLI: You can pass the superordinate
--<client>-<flag-name>
or modify theconfig
folder files. - π³ Docker: You can modify or add settings to the client container's
docker_compose.yml
files. - ποΈ Custom: Modify network configurations files or directly pass the
--<flag-name>
to the clients.
Further Sources about Client Configurations: