osmosis-labs / testnets Goto Github PK

View Code? Open in Web Editor NEW

7.0 4.0 6.0 1.4 MB

Osmosis public testnets

Home Page: https://osmotest5.osmosis.zone

Shell 100.00%

osmosis testnets

testnets's Introduction

🧪 Osmosis Testnets

This repository contains information on Osmosis public testnets and devnets

Chain ID	Type	Status	Version	Notes
osmo-test-5	`testnet`	Active	`v23.0.0-rc1`	Testnet
devnet	`devnet`	Beta	`v19.1.0`	Devnet with mainnet state

Testnets

Testnets are a type of blockchain used exclusively for testing purposes. They function as a sandbox environment, allowing developers to test new code and functionalities without worrying about affecting the live blockchain (mainnet). They are persistent environments, meaning that they remain active for extended periods of time.

Testnets come with a range of integrated services, including relayers to other testnets, frontends, explorers, and snapshot services.

🟪 osmo-test-5

Chain ID	`osmo-test-5`
Osmosisd version	`v23.0.0-rc1`
Genesis	http://genesis.testnet.osmosis.zone/genesis.json
RPC	https://rpc.testnet.osmosis.zone
gRPC	https://grpc.testnet.osmosis.zone
REST	https://lcd.testnet.osmosis.zone
Faucet	https://faucet.testnet.osmosis.zone
Explorer	https://explorer.testnet.osmosis.zone
Snapshots	https://snapshots.testnet.osmosis.zone
Frontend	https://testnet.osmosis.zone

🧪 Join the testnet

Join the testnet following the instructions on the osmo-test-5 page.

Devnets

Devnets, short for development networks, are also used for testing new functionalities and code. However, unlike testnets, devnets are temporary environments. They are essentially forks of the mainnet, created to mimic the live blockchain's conditions as closely as possible.

Devnets are ephemeral, which means they are deleted and recreated every 24 hours. This ensures that the testing environment closely mirrors the current state of the mainnet. Devnets are minimal environments, consisting only of a validator. Unlike testnets, devnets do not feature frontends or relayers to other testnets.

🟨 devnet

Chain ID	`devnet`
Osmosisd version	`v19.1.0`
Genesis	https://osmosis.fra1.digitaloceanspaces.com/devnet/genesis.json
Starting Height	https://osmosis.fra1.digitaloceanspaces.com/devnet/height
RPC	https://rpc.devnet.osmosis.zone
REST	https://lcd.devnet.osmosis.zone
gRPC	`grpc.devnet.osmosis.zone:30090`
websocket	`wss://rpc.devnet.osmosis.zone:443/websocket`
Faucet	https://faucet.devnet.osmosis.zone
Seed Node	`[email protected]:30056`

🆘 Issues and support

If you encounter any issues while joining the Osmosis network or have questions about the process, please don't hesitate to reach out for support.

For general questions and community support, join the Osmosis Discord and ask in the #testnet-discusion channel.
For technical issues or bugs related to the testnet, submit a detailed issue report on this repository with a clear description of the problem and any relevant error messages or logs.

🙋‍♀️ FAQ

1) I need some funds on the osmo-test-5 testnet, how can I get them?

You can request testnet tokens for the osmo-test-5 testnet from the faucet available at https://faucet.testnet.osmosis.zone. Please note that the faucet currently dispenses up to 100 OSMO per day per address.

2) I am an integrator on the osmo-test-5 testnet. How can I request more funds?

If you are an integrator needing additional testnet tokens for development or testing purposes, you can request them via this form. Please provide detailed information about your project and the number of tokens you require, and our team will review your request as soon as possible.

3) What are the differences between testnets and devnets?

Features	Testnets	Devnets
Persistent	✅	❌ they are deleted and recreated every 24 hours.
State	Maintains its own state.	Forks of the mainnet, mimicking its state.
Faucet	✅	✅
Explorer	✅	❌
Frontend	✅	❌
Relayers	✅	❌

testnets's People

Contributors

Stargazers

Watchers

Forkers

clemensgg ostr03 panoptisdev ashkan1987

testnets's Issues

Problems to run an clean Osmosis configuration

I am trying to run the a clean node installation, but It throws some hash validation errors... I am not sure why, and sorry but the documentation seems deprecated.

I download from here the genesis.json file:

https://osmosis.fra1.cdn.digitaloceanspaces.com/osmo-test-5/genesis.json
and from here the last snapshot:
https://snapshots.testnet.osmosis.zone
I use the source code from the repo with v21.2.1
Finally, I follow the steps from the tutorial (without cosmovisor) to run osmosid
but when it runs, it throws:

log error:
1:04PM ERR Stopping peer for error err="Reactor validation error: wrong Block.Header.AppHash.  Expected 3DA42B2DC962D1548E38BBC69BCBC0218A79FBE7A191118D2F6892A5CA063BC2, got FAA713A87EF67F2D32F02C16D355C8B0B07AC989C1049D46B50EB13E19C5FA8C" module=p2p peer="Peer{MConn{65.109.158.85:26656} c496ed7aec3d91b61cca6c80711537da1cf235f6 out}"

Add to chain-registry

Should we add testnet network info to the chain-registry?
https://github.com/cosmos/chain-registry/tree/master/osmosis

Instructions to download latest snapshot for testnet 5 are not working

System information

Osmosis version: 15.1.0-testnet
OS & Version: Linux

Expected behaviour

Download latest testnet 5 snapshot

Actual behaviour

Follow step 4 from here: https://github.com/osmosis-labs/testnets/tree/main/testnets/osmo-test-5

SNAPSHOT_URL=$(curl -sL https://snapshots.testnet.osmosis.zone/latest)
wget -q -O - $SNAPSHOT_URL | lz4 -d | tar -C $HOME/.osmosisd/ -xvf -

Downloading fails.

wget: invalid option -- 'C'
wget: invalid option -- 'f'
wget: invalid option -- '"'
wget: invalid option -- '>'
Usage: wget [OPTION]... [URL]...

Try `wget --help' for more options.
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors

SNAPSHOT URL is invalid:

echo $SNAPSHOT_URL 
<!DOCTYPE html> <html> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta http-equiv="X-UA-Compatible" content="ie=edge"> <title>Osmosis Snapshots</title> <meta property="og:type" content="website"> <meta property="og:title" content="Osmosis Snapshots"> <meta property="og:description" content="List of snapshots and 
...
...

Clients between `osmo-test-5` and `theta-testnet-001` are `Expired`

Context

My purpose is to send uatom from theta-testnet-001 to osmo-test-5 according to the specified channel info here and spinning up my own relayer.

Platform/Software

OS: MacOS Monterey
Relayer: Hermes v1.7.2

Problem

I used this command send uatom

hermes --json --config .hermes/test_config.toml  tx ft-transfer --dst-chain osmo-test-5 --src-chain theta-testnet-001 --src-port transfer --src-channel channel-2500 --amount 100 --denom uatom --timeout-seconds 100  | jq .

And here's the result I got:

{
  "result": "transfer error: failed while submitting the Transfer message to chain theta-testnet-001: gRPC call `send_tx_simulate` failed with status: status: Unknown, message: \"failed to execute message; message index: 0: cannot send packet using client (07-tendermint-1977) with status Expired: client is not active [cosmos/ibc-go/[email protected]/modules/core/04-channel/keeper/packet.go:74] With gas wanted: '0' and gas used: '87037' \", details: [], metadata: MetadataMap { headers: {\"server\": \"nginx\", \"date\": \"Thu, 30 Nov 2023 15:12:25 GMT\", \"content-type\": \"application/grpc\", \"x-cosmos-block-height\": \"19112446\", \"strict-transport-security\": \"max-age=63072000;\", \"x-content-type-options\": \"nosniff\", \"x-frame-options\": \"DENY\", \"access-control-allow-origin\": \"*\", \"access-control-allow-headers\": \"*\"} }",
  "status": "error"
}

When I read between the lines in the result, I saw:

...message: \"failed to execute message; message index: 0: cannot send packet using client (07-tendermint-1977) with status Expired: client is not active...

Then I ran this command to check the status of both clients:

hermes --config .hermes/test_config.toml  query client status --chain theta-testnet-001 --client 07-tendermint-1977
hermes --config .hermes/test_config.toml  query client status --chain osmo-test-5 --client 07-tendermint-13

They both return:

2023-11-30T15:16:24.415520Z  INFO ThreadId(01) running Hermes v1.7.2+c3210fc
SUCCESS Expired

Solution

I don't know if there's anything that can be done to fix an expired client but if there is one, do that. If not, create new client.