Update lisk.io to lisk.com - Partially closes #1184

modules/ROOT/pages/configuration/docker.adoc

@@ -44,12 +44,12 @@ services:
       FEE_EST_DEFAULT_START_BLOCK_HEIGHT: ''
       GENESIS_BLOCK_URL: ''
       GENESIS_HEIGHT: ''
-      GEOIP_JSON: https://geoip.lisk.io/json
+      GEOIP_JSON: https://geoip.lisk.com/json
       INDEX_MISSING_BLOCKS_RANGE: '1080'
       INDEX_N_BLOCKS: '0'
       LISK_CORE_HTTP: ''
       LISK_CORE_WS: ''
-      LISK_STATIC: https://static-data.lisk.io
+      LISK_STATIC: https://static-data.lisk.com
       SERVICE_BROKER: redis://redis_common:6379/0
       SERVICE_CORE_MYSQL: mysql://lisk:password@mysql_core:3306/lisk
       SERVICE_CORE_REDIS: redis://redis_core:6379/0
@@ -229,8 +229,8 @@ The following contents below will be displayed:
 ## Lisk Service custom configuration
 
 # Lisk Core node
-LISK_CORE_HTTP=https://mainnet.lisk.io
-LISK_CORE_WS=wss://mainnet.lisk.io
+LISK_CORE_HTTP=https://mainnet.lisk.com
+LISK_CORE_WS=wss://mainnet.lisk.com
 ----
 
 The two existing options `LISK_CORE_HTTP` and `LISK_CORE_WS` are examples of how to set config options in this file.

modules/ROOT/pages/configuration/source.adoc

@@ -69,11 +69,11 @@ module.exports = {
 			autorestart: true,
 			env: {
 				SERVICE_BROKER: 'redis://localhost:6379/0',
-				LISK_CORE_HTTP: 'https://mainnet.lisk.io',
-				LISK_CORE_WS: 'wss://mainnet.lisk.io',
+				LISK_CORE_HTTP: 'https://mainnet.lisk.com',
+				LISK_CORE_WS: 'wss://mainnet.lisk.com',
 				SERVICE_CORE_REDIS: 'redis://localhost:6379/1',
-				LISK_STATIC: 'https://static-data.lisk.io',
-				GEOIP_JSON: 'https://geoip.lisk.io/json',
+				LISK_STATIC: 'https://static-data.lisk.com',
+				GEOIP_JSON: 'https://geoip.lisk.com/json',
 			},
 		},
 		{

modules/ROOT/pages/index.adoc

@@ -17,7 +17,7 @@ Mona Bärenfänger <mona@lightcurve.io>
 :url_github_lisk_service_lisk: https://github.com/LiskHQ/lisk-service/blob/development/services/core
 :url_github_lisk_service_template: https://github.com/LiskHQ/lisk-service/blob/development/services/template
 :url_github_leveldb: https://github.com/google/leveldb
-:url_lisk_wallet: https://lisk.io/wallet
+:url_lisk_wallet: https://lisk.com/wallet
 :url_moleculer: https://moleculer.services/
 :url_nats: http://nats.io/
 :url_npm_socketio_client: https://www.npmjs.com/package/socket.io-client

modules/ROOT/pages/references/configuration.adoc

@@ -97,7 +97,7 @@ LISK_CORE_CLIENT_TIMEOUT=30            # Lisk Core client timeout (in seconds)
 [source,bash]
 ----
 # This setting is required only for SDK version 4 or lower.
-LISK_CORE_HTTP=https://mainnet.lisk.io # Lisk Core HTTP URL
+LISK_CORE_HTTP=https://mainnet.lisk.com # Lisk Core HTTP URL
 ----
 
 === Internal cache & persistence
@@ -128,11 +128,11 @@ MYSQL_PASSWORD=password
 
 [source,bash]
 ----
-# Lisk static assets, ie. known account lists
-LISK_STATIC=https://static-data.lisk.io
+# Lisk static assets, i.e. known account lists
+LISK_STATIC=https://static-data.lisk.com
 
 # Lisk Service geolocation backend
-GEOIP_JSON=https://geoip.lisk.io/json
+GEOIP_JSON=https://geoip.lisk.com/json
 ----
 
 === Indexing

modules/ROOT/pages/references/rpc-api.adoc

@@ -5,11 +5,11 @@
 The RPC WebSocket API can be accessed by the `ws://localhost:9901/rpc-v2`.
 
 === Access paths and compatibility
-The WebSocket API can be accessed by the `wss://service.lisk.io/rpc-v2`.
+The WebSocket API can be accessed by the `wss://service.lisk.com/rpc-v2`.
 
-The testnet network can also be accessed by `wss://testnet-service.lisk.io/rpc-v2`.
+The testnet network can also be accessed by `wss://testnet-service.lisk.com/rpc-v2`.
 
-The Lisk Service WebSocket API uses the `socket.io` library and it is compatible with JSON-RPC 2.0 standard.
+The Lisk Service WebSocket API uses the `socket.io` library and is compatible with the JSON-RPC 2.0 standard.
 The specification below contains numerous examples how to use the API in practice.
 
 === Endpoint logic

modules/ROOT/pages/references/subscribe-api.adoc

@@ -8,9 +8,9 @@ In practice, a two-way streaming connection is used, which means that not only c
 Lisk Service leverages the two-way communication approach by utilizing the WebSocket library responsible for updating users about changes in the blockchain network and markets.
 
 == Access paths and compatibility
-The blockchain update API can be accessed by the following path https://service.lisk.io/blockchain.
+The blockchain update API can be accessed by the following path https://service.lisk.com/blockchain.
 
-If you are interested in accessing the testnet network, this can be accomplished by using the https://testnet-service.lisk.io/blockchain endpoint.
+If you are interested in accessing the testnet network, this can be accomplished by using the https://testnet-service.lisk.com/blockchain endpoint.
 
 Important: The Lisk Service WebSocket API uses the `socket.io` library.
 This implementation is compatible with the version 2.0 of the socket.io library.
@@ -48,7 +48,7 @@ The blockchain dates are always expressed as integers and the epoch date is equa
 [source,js]
 ----
 const io = require('socket.io-client');
-const connection = io.connect('https://service.lisk.io/blockchain', { transports: ['websocket'] });
+const connection = io.connect('https://service.lisk.com/blockchain', { transports: ['websocket'] });
 connection.on('update.block', (block) => { (...) });
 ----