| Page Tree | ||||
|---|---|---|---|---|
|
- Secure Node FQDN – On this row the user should ll his/her fully qualified domain name (FQDN). It means to fill a complete domain name for your Secure Node on the internet e.g. node001.example.com.
- SSH username (to access your VPS) – The user should enter a username.
- SSH password (to access your VPS) – The user should enter a password.
- Path to SSH private key file – If the user wants to use the authentication with SSH/RSA key, the file has to be chosen by clicking on Browse button. In the case the user uses this method for authentication then, options SSH username and SSH password won’t be used / needed any longer. See Figure 3.1.
- Passphrase for SSH private key file (if necessary) – If the user uses a passphrase then, this row has to be entered.
- SSH port (to access your VPS) – Defaultly it is set to 22. If the user uses a different SSH port it is possible to change it.
- Secure Node port (see zen.conf) – This is RPC port for communication with zend. You can look into your zen.conf which can be found on your Secure Node (VPS) in location /.zen/zen.conf.
- Secure Node Username – This is username for communication with zend. You can look into your zen.conf which can be found on your Secure Node (VPS) in location /.zen/zen.conf.
- Secure Node Password – This is password for communication with zend. You can look into your zen.conf which can be found on your Secure Node (VPS) in location /.zen/zen.conf.
- Ready Timeout (default 10000) (integer value) This represents how many millisecond to wait before reject with a timeout error.
- Forward Timeout (default 10000) (integer value) This represents how many millisecond to wait for the SSH handshake to complete.
Zend can receive RPC calls. Using these calls Arizen can receive and send ZEN. Settings 7,8,9 are related to the RPC functionality. The RPC calls are unencrypted, so to avoid any information leakage, an extra layer is used (SSH tunneling). Using settings 1,2,3,6,10,11 Arizen establishes an encrypted SSH tunnel to the Secure/Super Node. So the data is protected.
When user saves settings correctly the LEDs in the Total Balance bar will be switched to green. The Server LED indicates the VPS if is ON and the zend LED indicates if the zend is running, see Figure 3.2. If the node isn’t connected the LEDs are hidden, as it’s show in the Figure 3.2 again.
After correct configuration of settings (both green LEDs), Arizen starts syncing the Z addresses. There is a 1:1 copy of the Z addresses both ways. None of private keys of T addresses is imported into Arizen from Secure Node and vice versa.
You can get a new Z address as well as T address. Just click on Get new address and select the type of the address you need, see Figure 3.3. If you don’t have connected any Node you will be able to create only T address, as it’s shown in the Figure 3.4. After clicking Create the Z address will appear in your Arizen wallet, as you can see in the Figure 3.5. The new Z address is created from the Secure Node and the Private Key is on the Secure Node and the Arizen Wallet.
Please note that you can create new private Z address only if you have both LEDs light green and you are connected to your zend.
Original Content by Tigger on September 5, 2018
| Panel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
3: You can choose the Z address only if you have a connected Secure or Super Node.
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|