Network
  • Welcome
  • Getting Started
    • Deployment Comparison
    • Using Docker Image
    • Standalone
    • Cluster Setup
    • Verify Connection
    • Node Interaction
  • NETWORKs
    • DevNet
    • ETH L2 Rollup
    • Benchmarking
Powered by GitBook
On this page
  • Install Tools
  • Check Network Status
  • Run The Examples
  1. Getting Started

Verify Connection

Once the network setup is complete, you need to check the connectivity to ensure the network is running properly.

Install Tools

Begin by installing the frontend tools:

sudo npm install -g @arcologynetwork/frontend-tools

Check Network Status

If the Arcology network is deployed as an L1 and the node is operating at 192.168.1.108 with the RPC port set to 8545:

npx arcology.net-monitor http://192.168.1.108:8545

If the Ethereum L1 node is running at192.168.1.108with RPC port 7545:

npx arcology.net-monitor http://192.168.1.108:7545

If the Arcology L2 rollup node is running at192.168.1.108with RPC port 8545:

npx arcology.net-monitor http://192.168.1.108:8545

The network monitor frequently queries multiple RPC methods, which may impact overall performance.

If the network runs as expected, you should see output similar to this:

height = 37583, empty block, timestamp = 1717291679, maxTps = 0, realtimeTps(1m) = 0
height = 37584, empty block, timestamp = 1717291680, maxTps = 0, realtimeTps(1m) = 0
height = 37585, empty block, timestamp = 1717291681, maxTps = 0, realtimeTps(1m) = 0
height = 37586, empty block, timestamp = 1717291682, maxTps = 0, realtimeTps(1m) = 0
height = 37587, empty block, timestamp = 1717291683, maxTps = 0, realtimeTps(1m) = 0
height = 37588, empty block, timestamp = 1717291684, maxTps = 0, realtimeTps(1m) = 0
height = 37589, empty block, timestamp = 1717291685, maxTps = 0, realtimeTps(1m) = 0
height = 37590, empty block, timestamp = 1717291686, maxTps = 0, realtimeTps(1m) = 0

Run The Examples

PreviousCluster SetupNextNode Interaction

Last updated 8 months ago

The concurrent programming guide includes several examples that you can utilize once the devNet is operational. Please check for more information.

the link