Environments & networks

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://app.arkane.network

API

Endpoint for API calls

https://api.arkane.network

Connect

Endpoint used by the Widget

https://connect.arkane.network

🧙 To connect with a personalized 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

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://staging.arkane.network/

API

Endpoint for API calls

https://api-staging.arkane.network/

Connect

Endpoint used by the Widget

https://connect-staging.arkane.network/

Blockchain networks

Blockchain

Network

Ethereum

testnet (Rinkeby)

Binance Smart Chain

testnet

Bitcoin

testnet (testnet3)

VeChain

testnet

Litecoin

testnet

GoChain

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

// use production environment
const arkaneConnect = new ArkaneConnect('CLIENT_ID');

To connect to the staging environment you add the parameter environment

// use staging environment
const arkaneConnect = new ArkaneConnect('CLIENT_ID', { environment: 'staging'});

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.

//Using the default Kovan Ethereum testnet
{
"walletId" : "cdc4c08a-b8fa-4e4c-z5a2-92c87b80f174",
"to" : "0xdc71b72db51e227e65a45004ab2798d31e8934c9",
"secretType" : "ETHEREUM",
"data" : "0x",
"value" : 1.15
}

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.

//Using a custom node to connect to the Rinkeby Ethereum testnet
{
"walletId" : "cdc4c08a-b8fa-4e4c-z5a2-92c87b80f174",
"to" : "0xdc71b72db51e227e65a45004ab2798d31e8934c9",
"secretType" : "VECHAIN",
"data" : "0x",
"value" : 1.15
}

Switching networks using the web3 provider