[Join the Cosmos Stargate announcements channel!](Cosmos Stargate announcements channel!)
If you’re running a block explorer, wallet, exchange, validator, or any other service (eg. custody provider) that depends upon the Cosmos Hub or Cosmos ecosystem, you’ll want to pay attention, because this upgrade will involve substantial changes.
- Inter-Blockchain Communication (IBC)– cross-chain transactions
- Protobuf Migration – blockchain performance & dev acceleration
- State Sync – minutes to sync new nodes
- Full-Featured Light Clients
- Chain Upgrade Module – upgrade automation
Help us to get the word out–this is a major leap for the Cosmos Network and we want everyone on board 🚀
We've launched the third public alpha testnet stargate-3 for the Stargate Upgrade on Monday September 21th.
Stargate-3 is a big testnet milestone for the Stargate initiative.
This release fixes issues with Legacy Amino that were discovered in stargate-1/2. We believe that this version is now good to test for exchanges and wallets.
The following features are live on the testnet.
- Legacy Amino
- IBC
- State-Sync
This testnet is intended for:
- Testing wallets, exchanges and block explorers against the legacy Amino REST interface
- Giving node operators and validators an opportunity to test their integrations against a work in progress version
- Playing with new Stargate features including IBC is possible now with the Akash realyer! Try it out at https://github.com/ovrclk/relayer/releases/tag/stargate-3
We anticipate restarting this testnet with future integration targets. Once we have a migration script, we will launch a testnet with a simulated upgrade from cosmoshub-3.
Our validator node for a persistent peer is available at
[email protected]:26656For users who want to test state sync, our validator node has tendermint rpc open on 34.123.10.100:26657and we are snapshotting every 1000 blocks.
As of 09/21/2020, the tagged gaia version is stargate-3
Remember this version now has a single binary instead of gaiacli/gaiad and much more configurable app.toml
git clone https://github.com/cosmos/gaia
git checkout stargate-3
make buildThe genesis file is available here The sha256sum of the genesis is
❯ sha256sum genesis.json
346dac9029a686845ee7ffd711a0c2479a6422c10f92f31ded6da8c6f4efbbc5 genesis.jsonState sync rapidly bootstraps a new node by discovering, fetching, and restoring a state machine snapshot from peers instead of fetching and replaying historical blocks. Requires some peers in the network to take and serve state machine snapshots. State sync is not attempted if the node has any local state (LastBlockHeight > 0). The node will have a truncated block history, starting from the height of the snapshot.
In the Tendermint config file there is a state-sync section. Some of these fields must be filled in order to use state-sync.
To find out how to fill in this information please visit: https://docs.tendermint.com/master/tendermint-core/state-sync.html
Additionally, some nodes in the network must take state sync snapshots, which are configured in app.toml:
Snapshot-interval specifies the block interval at which local state sync snapshots are taken (0 to disable). Must be a multiple of pruning-keep-every.
NOTE: Please set this value to a non-zero value. This is required in order for other nodes to be able to utilize state-sync.
snapshot-interval = {{ .StateSync.SnapshotInterval }}Snapshot-keep-recent specifies the number of recent snapshots to keep and serve (0 to keep all).
snapshot-keep-recent = {{ .StateSync.SnapshotKeepRecent }}These are disabled by default, out of caution - this is new code, and we wouldn't want it to cause a chain-wide halt or data corruption. Eventually we can consider enabling them by default.