One network. Clear information.

Understand HashNET, connect to the right environment, and find the evidence behind the technology.

Consensus and execution.
Each with a clear job.

HashNET orders transactions through its DAG-based consensus model. V2 combines that model with evmone execution for smart-contract applications and preserves legacy Tolar integration paths.

Understand the interfaces

Use TOL

Transfer the network’s native currency and pay transaction fees.

Build applications

Deploy and interact with smart contracts through documented interfaces.

Inspect the result

Follow receipts, events and available history through RPC or an explorer.

Mainnet or testnet?

Keep production activity and development separate. Configuration is maintained in one shared registry across this site.

Choose your network

Mainnet

The public Tolar network. Real TOL and applications.

Open mainnet explorer

RPC endpoint: https://jsongw.mainnet.tolar.io/jsonrpc
Chain ID: 1 (0x1)
Currency: TOL

Configuration checked 2026-10-01. This is connection information, not a live availability indicator.

Testnet

Develop and test before using real funds.

Open testnet explorer

RPC endpoint: https://jsongw.testnet.tolar.io/jsonrpc
Chain ID: 2 (0x2)
Currency: TOL

Configuration checked 2026-10-01. This is connection information, not a live availability indicator.

Tolar chain IDs overlap Ethereum network IDs. Confirm the RPC URL—not just the chain ID—before signing. Read compatibility guidance.

Performance, with context.

A TPS number is useful only with its workload and measurement conditions. HashNET V2 includes repeatable network throughput tests. Their results must not be confused with public-mainnet performance.

Read benchmark methodology

Operate with confidence.

Choose validator, full or archive mode to suit your responsibilities and retention needs. Validator membership follows Tolar’s designated-update-key model.

Read the operator guide