# Current Testnet Parameters

This page is meant to be kept up to date with the information from the currently released Testnet. Use the information here to deploy or upgrade your node on the Testnet.

  • Genesis Document:
    • sha1: 641a88d66085dcb8f310a1564227d478ed9a524d
    • sha256: f551c11d6545deecbc26b4973bb0ea04f3f555066ba9739bd175221660f367f1
  • Oasis Seed Node Address:

    NOTE

    Feel free to use other seed nodes than the one provided here.

  • Oasis Core version:

    NOTE

    The oasis-node binary is part of the Oasis Core release.

    WARNING

    Don't use a newer version of Oasis Core since it likely contains changes that are incompatible with version of Oasis Core used by other nodes in the current Testnet.

    DEPRECATED

    We no longer recommend or support using Oasis Labs' provided oasis-node Docker images.

# Deployment Change Log

# 2020-03-05 (Latest)

# Upgrade Parameters

  • Block height to dump: 335400
  • Upgrade Window
    • Start: 2020-03-05T17:00:00Z
    • End: 2020-03-06T16:59:59Z
      • The "End" of the window is not something we can enforce unilaterally, however, if, for whatever reason, not enough people upgrade on the public testnet we may release and redeploy a new genesis block that removes inactive nodes from the validator set.

# Upgrade Procedure

  1. Dump network state at the specified block height.
  2. Download and verify the genesis document published in the 2020-03-05 release.
  3. Stop your node.
  4. Wipe Node State.
  5. Upgrade oasis-node to version 20.4.1.
  6. Start your node.

For a more in-depth explanation, see Handling Network Upgrades guide.

# 2020-02-11

# Upgrade Parameters

  • Block height to dump: 270000
  • Upgrade Window
    • Start: 2020-02-11T17:00:00Z
    • End: 2020-02-12T16:59:59Z
      • The "End" of the window is not something we can enforce unilaterally, however, if, for whatever reason, not enough people upgrade on the public testnet we may release and redeploy a new genesis block that removes inactive nodes from the validator set.

# Upgrade Procedure

  1. Dump network state at the specified block height.
  2. Download and verify the genesis document published in the 2020-02-11 release.
  3. Stop your node.
  4. Wipe Node State.
  5. Delete /serverdir/node/tls_identity.pem and /serverdir/node/tls_identity_cert.pem.
    • The format for the TLS keys have changed. This will be regenerated on restart.
  6. Update your /serverdir/etc/config.yml per the below instructions.
  7. Upgrade oasis-node to version 20.3.1.
  8. Start your node.

# /serverdir/etc/config.yml Required Changes

# Changed

The tendermint.seed field has moved to tendermint.p2p.seed

Old Version:

tendermint:
  # ... other config
  seed:
    - "{{ seed_node_address }}"

New Version:

tendermint:
  # ... other config
  p2p:
    seed:
      - "{{ seed_node_address }}"

# 2020-01-23

You should only need to do an upgrade as detailed in the Handling Network Upgrades guide.

# 2020-01-15

/serverdir/etc/config.yml Required Changes

If you've deployed before, we changed the storage backend from boltdb to badger. See the Joining the Testnet Docs for the update.

# 2019-12-17

You should only need to do an upgrade as detailed in the Handling Network Upgrades guide.

# 2019-11-26

# /serverdir/etc/config.yml Required Changes

# Changed

Format for seed nodes has changed. Previously it only accepted a string. Now it supports an array of strings.

Old Version:

tendermint:
  # ... other config
  seeds: "{{ seed_node_address }}"

New Version:

tendermint:
  # ... other config
  seed:
    - "{{ seed_node_address0 }}"
    - "{{ seed_node_address1 }}"
# Removed

This temporary configuration on the initial deployment is no longer necessary. These lines have been removed.

## THESE NEXT 3 LINES ARE TEMPORARY YOU SHOULD NOT EXPOSE THIS PORT IN ANY WAY
grpc:
  debug:
    port: "42261"

# Staking and Registration Changes

The CLI for creating and submitting staking and registration transactions have changed. If you've already staked and registered your entity, then there's no need to make any changes.

# Docker Support

We no longer document using the Docker container for setup or deployment as we now distribute oasis-node binaries. You may still use the Docker container, and we will, for now, document the current Docker image tag for a given deployment.

# 2019-11-13

This is the initial deployment.