1. networks
Network Info
API Docs
Please visit the API reference to interact with these endpoints.
- testnet: 90u-4
- mainnet: morocco-1
- experimental: 120u-1
Chain ID
90u-4
RPC
https://testnet-rpc.terp.network:443
Block Explorers
ITRocket - https://testnet.itrocket.net/terp/staking
Genesis
https://raw.githubusercontent.com/terpnetwork/networks/main/testnet/90u-4/genesis.json
P2P Seed
e3f7a6a37f9b1bc7648603360b24312493c031f1@testnet-peer.terp.network:26656
Chain ID
morocco-1
RPC
https://rpc.cosmos.directory/terpnetwork:443
API
https://rest.cosmos.directory/terpnetwork:443
GRPC
https://grpc.terp.nodestake.top:443
Block Explorers
Ping.pub\ Nodestake.top\ Zenchain Labs
Genesis
https://raw.githubusercontent.com/terpnetwork/networks/main/mainnet/morocco-1/genesis.json
P2P Seed
## COMING SOON
Syncing Options
- Synchronize with state-sync: quickly sync to the current blockchain state without processing the entire blockchain history. With state-sync, the node downloads a snapshot of the current state from a trusted source and then begins validating new blocks. State-sync is faster than syncing from genesis, but it relies on trusting the source of the snapshot. This method is generally considered secure if you can trust the source, but it might be less secure than syncing from genesis.
- Synchronize from snapshot: from a snapshot is similar to state-sync but involves manually downloading a snapshot of the blockchain state and importing it into the node. This method is also faster than syncing from genesis, but it comes with the same trust issues as state-sync. It is essential to verify the integrity and authenticity of the snapshot before using it.