Environments & networks

Search…
More detail about environments and networks
Depending on which environment your application is connecting, your blockchain transactions will be directed to a specific blockchain network. 
Details
Production
Endpoints
Service
Description
URL
Authentication
Endpoint to authenticate
​https://login.arkane.network​
Wallet
Wallet user interface
​https://wallet.venly.io​
API
Endpoint for API calls
​https://api-wallet.venly.io​
Connect
Endpoint used by the Widget
​https://connect.venly.io​
​
🧙 To connect with a personalised Client ID, and access our production environment, please request access one using this form.
Blockchain networks
Blockchain
Network
Ethereum
mainnet
Binance Smart Chain
mainnet
Bitcoin
mainnet
VeChain
mainnet
Litecoin
mainnet
GoChain
mainnet
Hedera
mainnet
Tron
mainnet
Aeternity
mainnet
NEO
mainnet
Matic
mainnet
You are able to use your own nodes by making use of the network parameter.
Staging
Endpoints
Service
Description
URL
Authentication
Endpoint to authenticate
​https://login-staging.arkane.network​
Wallet
Wallet user interface
​https://wallet-staging.venly.io​
API
Endpoint for API calls
​https://api-wallet-staging.venly.io​
Connect
Endpoint used by the Widget
​https://connect-staging.venly.io​
Blockchain networks
Blockchain
Network
Ethereum
testnet (Rinkeby)
Binance Smart Chain
testnet
Bitcoin
testnet (testnet3)
VeChain
testnet
Litecoin
testnet
GoChain
testnet
Hedera
testnet
Tron
testnet (shasta)
Aeternity
testnet
NEO
testnet
Matic
testnet (mumbai)
How to select an environment
By default, you will connect to our production environment  
1
// use production environment
2
const venlyConnect = new VenlyConnect('CLIENT_ID');
Copied!
To connect to the staging environment you add the parameter  environment
1
// use staging environment
2
const venlyConnect = new VenlyConnect('CLIENT_ID', { environment: 'staging'});
Copied!
How to select a network
By default, you will connect to the blockchain network as described above. Mainnet when connecting to our production environment and a certain testnet when connecting to staging.
1
//Using the default Kovan Ethereum testnet
2
{
3
  "walletId" : "cdc4c08a-b8fa-4e4c-z5a2-92c87b80f174",
4
  "to" : "0xdc71b72db51e227e65a45004ab2798d31e8934c9",
5
  "secretType" : "ETHEREUM",
6
  "data" : "0x",
7
  "value" : 1.15
8
}
Copied!
By making use of the network object, you can change the node endpoint. In the example below we are connecting to the Rinkeby Ethereum testnet, instead of the default Kovan testnet.
1
//Using a custom node to connect to the Rinkeby Ethereum testnet
2
{
3
  "walletId" : "cdc4c08a-b8fa-4e4c-z5a2-92c87b80f174",
4
  "to" : "0xdc71b72db51e227e65a45004ab2798d31e8934c9",
5
  "secretType" : "VECHAIN",
6
  "data" : "0x",
7
  "value" : 1.15
8
}
Copied!
Switching networks using the web3 provider
Switching Networks
​
Deep Dive - Previous
Contract calls
Last modified 1mo ago
Copy link
Contents
Details
Production
Staging
How to select an environment
How to select a network
Switching networks using the web3 provider