Releases: InjectiveLabs/injective-chain-releases
Mainnet-v1.11.2-1685698280
Injective Avalon Upgrade 🥷
Upgrade Guide
This is a software upgrade proposal for Injective. If passed, this proposal would commit the Injective Chain to halt at block 34775000 (approximately 14:00 UTC on June 1st 2023) and resume with the v1.11 version of the application binary.
Validators can find a step-by-step guide on the upgrade procedure in the long-form proposal.
Note: Keyring is migrated from amino to protobuf, it's recommended you backup your keyring before applying the new application binary. For more details, refer here: cosmos/cosmos-sdk#9695
Breaking Changes
- Clients utilizing simulation along with a buffer should increase the buffer from 20k to 25-30k as gas consumption will be increased. Clients specifying explicit gas limit should use simulation to find the appropriate value for their use-case when the upgrade occurs or deploy their applications on testnet which has already been upgraded and empirically find the gas difference.
- Events in CometBFT are represented in strings and are not base64-encoded as previously. If you’re using raw events in your application opposed to exposed API’s, we recommend deploying your applications on testnet and migrate to the new scheme.
- Block mode is being deprecated in the newer cosmos-sdk version, clients should migrate to sync or async mode.
- Node Operators & IBC Relayers
- Node operators must remove the wasm cache before resuming with the new application binary. Refer here for more details.
- The new application binary requires Go version 1.19 opposed to 1.18. Node operators building from source must update the version before resuming with the new application binary.
- The libwasmvm library has been changed from v1.1.1 to v1.2.3. Node operators must copy the new library provided in the official release before resuming with the new application binary.
- IBC relayers should update hermes to v1.5.0 which has support for CometBFT.
Features
- Migrate cosmos-sdk from v0.45.11 to v0.47.2 and CometBFT v0.37.0
- Add gas fee delegation for contracts in wasmx. This feature will allow contracts executing in the BeginBlocker to optionally delegate gas payment to a different address
- Add support for settling derivative markets based on the latest oracle price observed when the settlement proposal passes.
- Add new proposal to change the number of decimals in the denom metadata
- Module params:
- Change double-sign slashing fraction from 5% to 0.5%
- Set begin blocker min gas price equal to transaction min gas price
- Increase max block gas limit from 30M to 50M
- Change BinaryOptionsMarketListingFee from 20INJ to 10INJ
- Miscellaneous:
- Emit events for contract executions in BeginBlocker
- Emit events when a validator is slashed
- Set min commission for all validators below 5% to 5%
- Modify oracle price query
- Add query to retrieve orders by account address
- Return TOB & mid price for a market in the DerivativeMarkets and SpotMarkets queries
- Add optional params to the orderbook query which will allow to get only one side or orders up to a cumulative notional value or quantity
- Fix handling of scale in market trade volatility query. Opposed to returning human-scaled values, it’s more convenient to return values based on the quote scale factor (for derivatives) or quote and base scale factors (for spot).
Usage
Versions
| Binary | Version | Commit Hash |
|---|---|---|
| injectived | 1.11.2 | 3fb2b7f331551c0eacbf3edf1407fdb13cbba689 |
| peggo | 1.11 | 31785adc3cc552366816dfa1897a33f5ba89de5a |
Go version 1.19
Verify you're using the correct version by running the below commands:
injectived version
peggo versiondocker run public.ecr.aws/l9h3g6c6/injective-core:v1.11 injectived version
docker run public.ecr.aws/l9h3g6c6/peggo:v1.11 peggo version🐳 Docker
Docker images have support for both amd64 and arm64 architectures.
| Image | Description |
|---|---|
| public.ecr.aws/l9h3g6c6/injective-core:v1.11.2 | Alpine image |
| public.ecr.aws/l9h3g6c6/peggo:v1.11 | Alpine image |
🕊️ Download Binaries
wget https://github.com/InjectiveLabs/injective-chain-releases/releases/download/v1.11.1-1685698280/linux-amd64.zip
unzip linux-amd64.zip
sudo mv injectived peggo /usr/bin
sudo mv libwasmvm.x86_64.so /usr/libv1.11-1685225746
Injective Avalon Upgrade 🥷
Upgrade Guide
This is a software upgrade proposal for Injective. If passed, this proposal would commit the Injective Chain to halt at block 34775000 (approximately 14:00 UTC on June 1st 2023) and resume with the v1.11 version of the application binary.
Validators can find a step-by-step guide on the upgrade procedure in the long-form proposal.
Breaking Changes
- Clients utilizing simulation along with a buffer should increase the buffer from 20k to 25-30k as gas consumption will be increased. Clients specifying explicit gas limit should use simulation to find the appropriate value for their use-case when the upgrade occurs or deploy their applications on testnet which has already been upgraded and empirically find the gas difference.
- Events in CometBFT are represented in strings and are not base64-encoded as previously. If you’re using raw events in your application opposed to exposed API’s, we recommend deploying your applications on testnet and migrate to the new scheme.
- Node Operators & IBC Relayers
- Node operators must remove the wasm cache before resuming with the new application binary. Refer here for more details.
- The new application binary requires Go version 1.19 opposed to 1.18. Node operators building from source must update the version before resuming with the new application binary.
- The libwasmvm library has been changed from v1.1.1 to v1.2.3. Node operators must copy the new library provided in the official release before resuming with the new application binary.
- IBC relayers should update hermes to v1.5.0 which has support for CometBFT.
Features
- Migrate cosmos-sdk from v0.45.11 to v0.47.2 and CometBFT v0.37.0
- Add gas fee delegation for contracts in wasmx. This feature will allow contracts executing in the BeginBlocker to optionally delegate gas payment to a different address
- Add support for settling derivative markets based on the latest oracle price observed when the settlement proposal passes.
- Add new proposal to change the number of decimals in the denom metadata
- Module params:
- Change double-sign slashing fraction from 5% to 0.5%
- Set begin blocker min gas price equal to transaction min gas price
- Increase max block gas limit from 30M to 50M
- Change BinaryOptionsMarketListingFee from 20INJ to 10INJ
- Miscellaneous:
- Emit events for contract executions in BeginBlocker
- Emit events when a validator is slashed
- Modify oracle price query
- Add query to retrieve orders by account address
- Return TOB & mid price for a market in the DerivativeMarkets and SpotMarkets queries
- Add optional params to the orderbook query which will allow to get only one side or orders up to a cumulative notional value or quantity
- Fix handling of scale in market trade volatility query. Opposed to returning human-scaled values, it’s more convenient to return values based on the quote scale factor (for derivatives) or quote and base scale factors (for spot).
Usage
Versions
| Binary | Version | Commit Hash |
|---|---|---|
| injectived | 1.11 | f77eb5cfd7d03ee132095dc5f51699f1f1a2e7f9 |
| peggo | 1.11 | 5868c9461191ce5c3e7b11a2c4f8ec5779d15964 |
Go version 1.19
Verify you're using the correct version by running the below commands:
injectived version
peggo versiondocker run public.ecr.aws/l9h3g6c6/injective-core:v1.11 injectived version
docker run public.ecr.aws/l9h3g6c6/peggo:v1.11 peggo version🐳 Docker
Docker images have support for both amd64 and arm64 architectures.
| Image | Description |
|---|---|
| public.ecr.aws/l9h3g6c6/injective-core:v1.11 | Alpine image |
| public.ecr.aws/l9h3g6c6/peggo:v1.11 | Alpine image |
🕊️ Download Binaries
wget https://github.com/InjectiveLabs/injective-chain-releases/releases/download/v1.11-1685225746/linux-amd64.zip
unzip linux-amd64.zip
sudo mv injectived peggo /usr/bin
sudo mv libwasmvm.x86_64.so /usr/libMainnet-v1.10.1-1685036881
Injective Chain releases
This repository hosts Injective Chain releases of binary artifacts.
It also contains hassle-free guides and scripts for getting started and managing Injective Chain nodes.
Guides included
- Injective Exchange Service Setup Guide (Includes Running a Node)
- Create a new node and join the network
- Sync node from a snapshot (quickest way to sync blocks).
- Upgrade Node to the latest version
Requirements
The following requirements are required to run the node natively.
Hardware
The following table shows the minimum recommended hardware requirements for the running node on the mainnet.
| Validator Node | Sentry Node |
|---|---|
| CPU: 8 Cores | CPU: 8 Cores |
| Memory: 64Gb | Memory: 64Gb+ |
| Storage: 2Tb | Storage: 2Tb |
| Network: 5Gbps+ | Network: 5Gbps+ |
Software
- Go Installed
- Git Installed
- AWS CLI (only for snapshot sync, aws account not required)
Sentry Seed Nodes
For the testnet, find a list of seed nodes in seed.txt in the matching release folder here
Example, for testnet release 0.4.19
you will find the seed node list in 70001/seeds.txt
For the mainnet, find a list of seed nodes matching your release here
Helpful links
Get Involved
Injective Protocol is a community driven project; we welcome all contribution.
- Discuss with Discord community
- Join Injective on Telegram
- Github repositories
- Follows us on Twitter
Mainnet-v1.10.0-1679065799
Injective Chain releases
This repository hosts Injective Chain releases of binary artifacts.
It also contains hassle-free guides and scripts for getting started and managing Injective Chain nodes.
Guides included
- Injective Exchange Service Setup Guide (Includes Running a Node)
- Create a new node and join the network
- Sync node from a snapshot (quickest way to sync blocks).
- Upgrade Node to the latest version
Requirements
The following requirements are required to run the node natively.
Hardware
The following table shows the minimum recommended hardware requirements for the running node on the mainnet.
| Validator Node | Sentry Node |
|---|---|
| CPU: 8 Cores | CPU: 8 Cores |
| Memory: 64Gb | Memory: 64Gb+ |
| Storage: 2Tb | Storage: 2Tb |
| Network: 5Gbps+ | Network: 5Gbps+ |
Software
- Go Installed
- Git Installed
- AWS CLI (only for snapshot sync, aws account not required)
Sentry Seed Nodes
For the testnet, find a list of seed nodes in seed.txt in the matching release folder here
Example, for testnet release 0.4.19
you will find the seed node list in 70001/seeds.txt
For the mainnet, find a list of seed nodes matching your release here
Helpful links
Get Involved
Injective Protocol is a community driven project; we welcome all contribution.
- Discuss with Discord community
- Join Injective on Telegram
- Github repositories
- Follows us on Twitter
Mainnet-v1.10-1678709842
Injective Chain releases
This repository hosts Injective Chain releases of binary artifacts.
It also contains hassle-free guides and scripts for getting started and managing Injective Chain nodes.
Guides included
- Injective Exchange Service Setup Guide (Includes Running a Node)
- Create a new node and join the network
- Sync node from a snapshot (quickest way to sync blocks).
- Upgrade Node to the latest version
Requirements
The following requirements are required to run the node natively.
Hardware
The following table shows the minimum recommended hardware requirements for the running node on the mainnet.
| Validator Node | Sentry Node |
|---|---|
| CPU: 8 Cores | CPU: 8 Cores |
| Memory: 64Gb | Memory: 64Gb+ |
| Storage: 2Tb | Storage: 2Tb |
| Network: 5Gbps+ | Network: 5Gbps+ |
Software
- Go Installed
- Git Installed
- AWS CLI (only for snapshot sync, aws account not required)
Sentry Seed Nodes
For the testnet, find a list of seed nodes in seed.txt in the matching release folder here
Example, for testnet release 0.4.19
you will find the seed node list in 70001/seeds.txt
For the mainnet, find a list of seed nodes matching your release here
Helpful links
Get Involved
Injective Protocol is a community driven project; we welcome all contribution.
- Discuss with Discord community
- Join Injective on Telegram
- Github repositories
- Follows us on Twitter
Mainnet-10009-1673970775
Injective Chain releases
The repository hosts Injective Chain releases of binary artifacts.
It also contains hassle-free guides and scripts for getting started and managing Injective Chain nodes.
Guides included
- Create a new node and join the network
- Sync node from the snapshot (quickest way to sync blocks).
- Sync node from scratch via public sentries (better decentralization factor).
- Upgrade Node to the latest version
Requirements
The following requirements are required to run the node natively.
Hardware
The following table shows the recommended hardware requirements for the running node on the mainnet.
| Validator Node | Sentry Node |
|---|---|
| Memory: 16Gb | Memory: 16Gb+ |
| Storage: 1Tb | Storage: 1Tb |
| Network: 5Gbps+ | Network: 5Gbps+ |
Software
- Go Installed
- Git Installed
- AWS CLI (only for snapshot sync, aws account not required)
Sentry Seed Nodes
For the testnet, find a list of seed nodes in seed.txt in the matching release folder here
Example, for testnet release 0.4.19
you will find the seed node list in 70001/seeds.txt
For the mainnet, find a list of seed nodes matching your release here
Helpful links
Get Involved
Injective Protocol is a community driven project; we welcome all contribution.
- Discuss with Discord community
- Join Injective on Telegram
- Github repositories
- Follows us on Twitter
Mainnet-10009-1673640888
Injective Chain releases
The repository hosts Injective Chain releases of binary artifacts.
It also contains hassle-free guides and scripts for getting started and managing Injective Chain nodes.
Guides included
- Create a new node and join the network
- Sync node from the snapshot (quickest way to sync blocks).
- Sync node from scratch via public sentries (better decentralization factor).
- Upgrade Node to the latest version
Requirements
The following requirements are required to run the node natively.
Hardware
The following table shows the recommended hardware requirements for the running node on the mainnet.
| Validator Node | Sentry Node |
|---|---|
| Memory: 16Gb | Memory: 16Gb+ |
| Storage: 1Tb | Storage: 1Tb |
| Network: 5Gbps+ | Network: 5Gbps+ |
Software
- Go Installed
- Git Installed
- AWS CLI (only for snapshot sync, aws account not required)
Sentry Seed Nodes
For the testnet, find a list of seed nodes in seed.txt in the matching release folder here
Example, for testnet release 0.4.19
you will find the seed node list in 70001/seeds.txt
For the mainnet, find a list of seed nodes matching your release here
Helpful links
Get Involved
Injective Protocol is a community driven project; we welcome all contribution.
- Discuss with Discord community
- Join Injective on Telegram
- Github repositories
- Follows us on Twitter
Mainnet-10008-1668679102
Injective Chain releases
The repository hosts Injective Chain releases of binary artifacts.
It also contains hassle-free guides and scripts for getting started and managing Injective Chain nodes.
Guides included
- Create a new node and join the network
- Sync node from the snapshot (quickest way to sync blocks).
- Sync node from scratch via public sentries (better decentralization factor).
- Upgrade Node to the latest version
Requirements
The following requirements are required to run the node natively.
Hardware
The following table shows the recommended hardware requirements for the running node on the mainnet.
| Validator Node | Sentry Node |
|---|---|
| Memory: 16Gb | Memory: 16Gb+ |
| Storage: 1Tb | Storage: 1Tb |
| Network: 5Gbps+ | Network: 5Gbps+ |
Software
- Go Installed
- Git Installed
- AWS CLI (only for snapshot sync, aws account not required)
Sentry Seed Nodes
For the testnet, find a list of seed nodes in seed.txt in the matching release folder here
Example, for testnet release 0.4.19
you will find the seed node list in 70001/seeds.txt
For the mainnet, find a list of seed nodes matching your release here
Helpful links
Get Involved
Injective Protocol is a community driven project; we welcome all contribution.
- Discuss with Discord community
- Join Injective on Telegram
- Github repositories
- Follows us on Twitter
Mainnet-10007-1666607351
Injective Chain releases
The repository hosts Injective Chain releases of binary artifacts.
It also contains hassle-free guides and scripts for getting started and managing Injective Chain nodes.
Guides included
- Create a new node and join the network
- Sync node from the snapshot (quickest way to sync blocks).
- Sync node from scratch via public sentries (better decentralization factor).
- Upgrade Node to the latest version
Requirements
The following requirements are required to run the node natively.
Hardware
The following table shows the recommended hardware requirements for the running node on the mainnet.
| Validator Node | Sentry Node |
|---|---|
| Memory: 16Gb | Memory: 16Gb+ |
| Storage: 1Tb | Storage: 1Tb |
| Network: 5Gbps+ | Network: 5Gbps+ |
Software
- Go Installed
- Git Installed
- AWS CLI (only for snapshot sync, aws account not required)
Sentry Seed Nodes
For the testnet, find a list of seed nodes in seed.txt in the matching release folder here
Example, for testnet release 0.4.19
you will find the seed node list in 70001/seeds.txt
For the mainnet, find a list of seed nodes matching your release here
Helpful links
Get Involved
Injective Protocol is a community driven project; we welcome all contribution.
- Discuss with Discord community
- Join Injective on Telegram
- Github repositories
- Follows us on Twitter
Mainnet-10007-1665417543
Injective Chain releases
The repository hosts Injective Chain releases of binary artifacts.
It also contains hassle-free guides and scripts for getting started and managing Injective Chain nodes.
Guides included
- Create a new node and join the network
- Sync node from the snapshot (quickest way to sync blocks).
- Sync node from scratch via public sentries (better decentralization factor).
- Upgrade Node to the latest version
Requirements
The following requirements are required to run the node natively.
Hardware
The following table shows the recommended hardware requirements for the running node on the mainnet.
| Validator Node | Sentry Node |
|---|---|
| Memory: 16Gb | Memory: 16Gb+ |
| Storage: 1Tb | Storage: 1Tb |
| Network: 5Gbps+ | Network: 5Gbps+ |
Software
- Go Installed
- Git Installed
- AWS CLI (only for snapshot sync, aws account not required)
Sentry Seed Nodes
For the testnet, find a list of seed nodes in seed.txt in the matching release folder here
Example, for testnet release 0.4.19
you will find the seed node list in 70001/seeds.txt
For the mainnet, find a list of seed nodes matching your release here
Helpful links
Get Involved
Injective Protocol is a community driven project; we welcome all contribution.
- Discuss with Discord community
- Join Injective on Telegram
- Github repositories
- Follows us on Twitter