Register Delegate
Once you have correctly set up your instance, installed the different programs, you can now register as a delegate of the X-Cash Public Network. You will need to have all the services already running to generate the necessary parameters to register yourself as a delegate.
You should have noted your block verifier keys during the program installation. You will need to prepare a delegate name, your server IP address or domain name, and the block verifier public key. Furthermore, you will have to register from the wallet you will be used to collect the reward.
Chose your delegate name wisely as you won't be able to change it down the line. If you want to change the name, you will have to generate a new block verifier key pair and register yourself again, but you will however lose your previous delegate stats.
First of all, the wallet service should be running in the background. Stop it by using the command:
systemctl stop xcash-rpc-wallet
Open and let synchronize your wallet generated during the node installation, either when using the auto-installer or created manually.
~/xcash-official/xcash-core/build/release/bin/xcash-wallet-cli --wallet-file ~/xcash-official/xcash-wallets/<WALLET_NAME>
Replace the <WALLET_NAME> with your own.
If you installed with the auto-installer script, the wallet name will be delegate-wallet
Once your wallet is fully synchronized, you can use the delegate_register command with the following parameters:
delegate_register <delegate_name> <IP_address|domain_name> <block_verifier_public_key>
And replace the information with:
<delegate_name>: the name that will be displayed on the delegate explorer. Cannot be updated.<IP_address|domain_name>: your server's IP address or its domain name (if you have bought a domain name and correctly set up the DNS record). It is recommended to register your delegate using your domain name, as you can redirect your server IP address to it easily in your DNS record, enabling you to change server in the future. It is however possible to change this information at a later time. Can be updated.<block_verifier_public_key>: the block verifier public key that you have generated earlier. Cannot be updated.
Example:
delegate_register my_delegate my_delegate.domain.com cf8718d638ce0a831f3538ea60d1e27c3a258c7004a1ad7c547cc5331de7d9d7
You will be prompted to wait for the next valid data interval. Once your request has been accepted, you will receive the message The delegate has been registered successfully.
You can check in the delegates explorer if your node is correctly appearing.
You can exit the wallet, and restart the wallet service:
systemctl restart xcash-rpc-wallet
Each registered delegates will be displayed in the delegates explorer, along with their statistics and information. At registration, the minimum information that is displayed is your delegate name and IP address. You can add additional instructions to help others identify you or rally to your cause and vote for you.
First of all, the wallet service should be running in the background. Stop it by using the command:
systemctl stop xcash-rpc-wallet
Open and let synchronize the wallet you used to register as a delegate, either when using the auto-installer or created manually.
~/xcash-official/xcash-core/build/release/bin/xcash-wallet-cli --wallet-file ~/xcash-official/xcash-wallets/<WALLET_NAME>
Replace the <WALLET_NAME> with your own.
If you installed with the autoinstaller script, the wallet name will be delegate-wallet
Once your wallet is fully synchronized, you can use the delegate_update command with the following parameters:
delegate_update <item> <value>
Replace the <item> with one of the lists below, and change the corresponding <value>
Item | Type | Description |
| String (1024 char. max.) | Short description about you and your motivations as a delegate. Example:
|
| String (255 char. max.) | Update the IP address or domain name of your delegate node. Must be in IPV4 format Example:
|
| String (255 char. max.) | Link to your landing page or website relating to your delegate information and statistics. Example:
|
| String (255 char. max.) | In case of delegate node managed by several persons. Can be a team name, names or GitHub profiles. Example: |
| String (255 char. max.) | solo: for a solo delegates. shared: for shared delegates. Shared delegates set up a fee and redistribute a share of the reward to their voters. group: for private groups. Private groups works as shared but the delegate decide how he/she going to distribute the votes. See how to set it up below.​ Example: |
| Number [0 - 100] with up to 6 decimals | Fees (in percentage) taken by the shared delegate on the block reward. Provide the fee you have used during the node installation. Example: |
| String (255 char. max.) | A description of the servers' specifications and hardware. Example: |
You will be prompted to wait for the next valid data interval. Once your request has been accepted, you will receive the message The delegate info has been updated successfully.
You can exit the wallet and restart the wallet service:
systemctl start xcash-rpc-wallet
A shared delegate can choose to run a private group, where the delegate decide which voters is getting a share of the block reward. This set up is favorable for people running a shared delegate group with a closed group of people, and only want to retribute this select group.
To change this setting, you will need to make some changes in the xcash-dpops.service and create a special configuration file that will list the wallet address you wish to send block reward payments to.
First, you will need to create a configuration file that will list the wallet address you will distribute to.
nano ~/xcash-official/xcash-dpops-configuration.txt
Then, you will need to add the addresses to distribute to in your list following the following format:
# Commentwallet1|voting-address|payment-addresswallet2|voting-address|payment-address
Where voting-address is the wallet address used to vote for the delegate, and payment-address is the wallet you want to distribute the share of the block reward to.
The voting-address and payment-address can be the same.
The maximum amount of payment-address that can be in the list is 100.
Once the config file is ready, save it and close. You will need to update the xcash-dpops.service so it can get the configuration file. First, run the stop program option in the installer script:
bash -c "$(curl -sSL https://raw.githubusercontent.com/X-CASH-official/xcash-dpops/master/scripts/autoinstaller/autoinstaller.sh)"
And choose option 13. Once the programs are stopped, open the xcash-dpops.service located in /lib/systemd/system/and add the parameter --private-group <path-to-configuration-file>to the ExecStart line.
nano /lib/systemd/system/xcash-dpops.service
[Unit]Description=X-Cash DPOPS Daemon background process​[Service]Type=simpleLimitNOFILE=infinityUser=rootWorkingDirectory=~/xcash-official/xcash-dpops/buildExecStart=~/xcash-official/xcash-dpops/build/xcash-dpops --private-group ~/xcash-official/xcash-dpops-configuration.txt --block-verifiers-secret-key BLOCK_VERIFIER_SECRET_KEYRestart=always​[Install]WantedBy=multi-user.target
Once done, save your changes and restart the programs by running the option 12 of the auto-installer script.
bash -c "$(curl -sSL https://raw.githubusercontent.com/X-CASH-official/xcash-dpops/master/scripts/autoinstaller/autoinstaller.sh)"
As a shared delegate (normal or private group), you will have to distribute a share of the block reward to your voters. On the first payment threshold, the program will automatically distribute the voters' share from the delegate wallet. However, the delegate wallet is empty at first and you might be missing some unspents to conveniently pay your voters.
It is recommended to pre-fund your delegate wallet when first setting it up. We recommend pre-funding between 500k to 1M XCASH into the delegate wallet.
