Skip to content

Releases: tablelandnetwork/go-tableland

v1.0.0

19 Jan 18:57
cd9f930
Compare
Choose a tag to compare

This release is a set of changes, part of Launch Week. Check out Announcing Launch Week.

This is a mandatory upgrade of the Tableland validator.

Here’s some important information you should be aware of when upgrading your validator:

  • If the validator is running, stop it the validator with make testnet-down
  • You can delete any database.db and metrics.dbfiles in docker/deployed/testnet/api and backup files inside docker/deployed/testnet/api/backups
  • We now have two networks: mainnet and testnet. We are recommending all validators to run on mainnet. The mainnet network is the most stable one and where we want the most number of validators.
  • This version contains new specific configuration for mainnet
    • Create a .env_validator file in docker/deployed/mainnet/api folder.
      • Write into the file the following content:
        VALIDATOR_ALCHEMY_ETHEREUM_MAINNET_API_KEY=<your ethereum mainnet alchemy key>
        VALIDATOR_ETHEREUM_MAINNET_SIGNER_PRIVATE_KEY=<your ethereum mainnet hex-encoded private key>
        VALIDATOR_ALCHEMY_OPTIMISM_MAINNET_API_KEY=<your optimism mainnet alchemy key>
        VALIDATOR_OPTIMISM_MAINNET_SIGNER_PRIVATE_KEY=<your optimism mainnet hex-encoded private key>
        VALIDATOR_ALCHEMY_ARBITRUM_MAINNET_API_KEY=<your arbitrum mainnet alchemy key>
        VALIDATOR_ARBITRUM_MAINNET_SIGNER_PRIVATE_KEY=<your arbitrum mainnet hex-encoded private key>
        VALIDATOR_ALCHEMY_POLYGON_MAINNET_API_KEY=<your polygon mainnet alchemy key>
        VALIDATOR_POLYGON_MAINNET_SIGNER_PRIVATE_KEY=<your polygon mainnet hex-encoded private key>
        METRICS_HUB_API_KEY=<the value you had previously configured in docker/deployed/testnet/testnet/.env_validator >
        
    • There is no need to fund those wallets
    • Tune the docker/deployed/mainnet/api/config.json:
      • If you want a correctly configured configuration file that is only running the recommended chains, please use this one.
      • If you want to configure things manually to your own taste:
        1. Change the ExternalURIPrefix configuration attribute into the DNS (or IP) where your validator will be serving external requests.
        2. In the Chains section, only leave the chains you’ll be running.
    • Create a .env_grafana file in docker/deployed/mainnet/grafana folder.
      • Write into the file the following content:
      GF_SECURITY_ADMIN_USER=<user name you'd like to login intro grafana>
      GF_SECURITY_ADMIN_PASSWORD=<password of the user>
      
  • After everything is configured, run make mainnet-up to start your node and join the mainnet network
  • This version doesn’t contain heavy migrations, so you shouldn’t expect some delay when you start from this version for the first time
  • You should upgrade your validator to this new version before January 30, 2023

What's Changed

Full Changelog: v1.0.0-beta-2...v1.0.0

v1.0.0-beta-2

18 Jan 14:04
93ff2ee
Compare
Choose a tag to compare
v1.0.0-beta-2 Pre-release
Pre-release

What's Changed

Full Changelog: v0.0.1-alpha-3...v1.0.0-beta-2

v1.0.0-beta-1

18 Jan 13:06
bfe36a4
Compare
Choose a tag to compare
v1.0.0-beta-1 Pre-release
Pre-release

What's Changed

Read more

v0.0.1-alpha-4

13 Jan 18:59
2f86848
Compare
Choose a tag to compare
v0.0.1-alpha-4 Pre-release
Pre-release

What's Changed

Read more

v0.0.1-alpha-3

13 Dec 19:59
b720a45
Compare
Choose a tag to compare
v0.0.1-alpha-3 Pre-release
Pre-release
ci: generate binaries

Signed-off-by: Ignacio Hagopian <[email protected]>