Releases: piplabs/story
v0.12.1
v0.12.1 is the bug fix release for the Story Odyssey network. This release shortens fixed staking periods and resolves several issues within the staking module. Node operators must ensure their client be updated to this release via a hard-fork upgrade at block 322000.
Overview
v0.12.1 shortens fixed staking periods and resolves several issues within the staking module.
Features
- Reduce fixed staking periods from 3 months, 1 year, 36 months to 1 week, 2 weeks, and 3 weeks for testnet purpose, since mainnet will launch early next year and we want to have partners and users experience all features before that. (#322)
Fixes
- Fix an issue where staking operations are not processed by the order they come (#325)
- Simply event processing (#328)
- Fix a reward distribution issue that could cause chain halt (#321)
- Fix repeat createValidator call refund issue (#330)
- Fix setWithdrawalAddress/setRewardAddress issue (#329)
Feedback & Support
We value your feedback and encourage you to report any issues or suggestions through our public issues tracker. For additional support, please message us in the developer channel of our public Discord.
Users may download the client from the attached binaries.
v0.12.0
v0.12.0 is the official client release for the Story Odyssey network. Odyssey introduces new staking mechanisms, a Genesis stake suspension phase known as the Singularity, new staking and reward distribution mechanisms, and new staking smart contract updates. Users who wish to switch to Odyssey should download the new v0.12.0 release client.
Overview
v0.12.0 introduces client support for Story's Odyssey test network. One of the major additions of Odyssey is the introduction of new mechanics for staking and reward distribution for tokens, which receive different emissions depending on whether they are locked or unlocked. These changes include the Singularity, a period immediately preceding Genesis in which anyone can create or stake tokens, but only the eight original genesis validators remain active. Another prominent new feature is UBI for validators, which allocates a percentage of inflationary rewards for validators with the highest participation rate. Odyssey also includes a bunch of consensus-level optimizations, including the addition of the evidence module, timelocks for more secure contract administration, and separation between rewards and withdrawal queues. Finally, the story
CLI has been updated to improve the developer UX and support better key management and tooling for key conversions.
Features
- Addition of the Singularity, a phase occurring during the first 1,209,600 blocks after genesis, during which everyone can create validators and stake tokens, but only the genesis validator holds voting power [#236, #265, #271)
- UBI validator support (#222, #228)
- Introduction of new staking mechanisms for locked and unlocked tokens (#189, #209, #215)
- Built-in
story
client API for period delegations (#232) - Introduction of the wrapped IP token and pre-deploy (#282)
- Reservation of timelock-controlled proxy addresses for future pre-deploys (#278)
- Addition of the ERC-6551 registry as a predeploy (#276)
- Customization of a mint module for new inflation mechanics (#169)
- Addition of create3 and timelock contracts (#242)
- CLI support for the Odyssey network, including better key management tooling (#174, #239)
Fixes
- Various optimizations and fixes around reward distribution claims, notably separation between rewards and withdrawal queues (#260, #277)
- Different fixes around staking validation and delegation (#251, #257)
- Porting of various security fixes (#212)
Feedback & Support
We value your feedback and encourage you to report any issues or suggestions through our public issues tracker. For additional support, please message us in the developer channel of our public Discord.
Users may download the client from the attached binaries.
v0.11.0
v0.11.0 is a new major release for the story
consensus client that enables the unjail feature along with miscellaneous improvements around unstaking and node operations. Node operators must ensure their client be updated to this release via a hard-fork upgrade at block 1,325,860.
Overview
v0.11.0 introduces a major upgrade (requiring a hard-fork) for enabling the unjail feature and improving how unstaking operations work.
Fixes
- Enables the unjail feature, which allows validators which were automatically unbonded due to downtime to rejoin the bonded set
- Fixes a bug on how unbonding checks triggered by unstaking operators are processed (#163)
- Adds scripts for deploying the story token slashing contracts (#159)
- Adds a CLI validator subcommand for unjailing
Feedback & Support
We value your feedback and encourage you to report any issues or suggestions through our public issues tracker. For additional support, please message us in the developer channel of our public Discord.
Binaries
Users may download the client from our set of pre-built binaries:
v0.10.2
v0.10.2 is a maintenance release for the story
consensus client that enables clients to roll back state by a single block.
Overview
v0.10.2 addresses a story
client issue faced by operators who fail to upgrade their execution client before a geth
hardfork. Previously, in such situations, even if the operator were to upgrade their geth
client, the story
consensus client would remain in an invalid state, with the only way of re-syncing requiring clearing the data and syncing all the way from genesis. This releases provides a remedy for such situations in allowing story
nodes to roll back a block.
Fixes
- Adds a
rollback
command to thestory
CLI, allowing operators to rollback their consensus state by a single block
Feedback & Support
We value your feedback and encourage you to report any issues or suggestions through our public issues tracker. For additional support, please message us in the developer channel of our public Discord.
Binaries
Users may download the client from our set of pre-built binaries:
v0.10.1
v0.10.1 is a hotfix release for the story
consensus client that addresses a critical bug related to unstaking with inadequate balances. Existing operators should upgrade directly (e.g. using cosmovisor) to this version. New operators syncing from scratch should first upgrade from v0.9.13 to v0.10.1.
Overview
v0.10.1 is a hotfix release that addresses a critical bug related to unstaking. Previously, if on unstaking the unbonding threshold was reached and the delegator's balance had decreased since the original unstaking request — such as from slashing — it would erroeously trigger a system panic. This fix ensures that in such scenarios only the remaining available balance is ultimately unbonded.
Fixes
- Updates unbonding queue processing to prevent system panics in cases of delegator balance changing during the unbonding time period
Feedback & Support
We value your feedback and encourage you to report any issues or suggestions through our public issues tracker. For additional support, please message us in the developer channel of our public Discord.
Binaries
Users may download the client from our set of pre-built binaries:
v0.10.0
v0.10.0 is a key release for the story
consensus client that introduces some key enhancements for improving validator performance. Validators should update to this latest stable version for running a node on the iliad
network.
Overview
v0.10.0
is a major release that optimizes validator sweeping logic, enhances the server capabilities to support more queries across story's customized modules, and adds more testing for internal testing for upgrades. In addition, it adds to the validator CLI subcommand the ability to check for the block height via a new story validator status
subcommand.
Fixes
- Changes withdrawal queue processing to sweep based only on validator accounts instead of delegator accounts (#74)
- Fixes a typo contained within one of the internal Story CI jobs (#99)
Other Updates
- Adds more testing for handling client upgrades (#86)
- Adds a new
story validator status
subcommand for querying the latest block height via CLI (#108)
Feedback & Support
We value your feedback and encourage you to report any issues or suggestions through our public issues tracker. For additional support, please message us in the developer channel of our public Discord.
Binaries
Users may download the client from our set of pre-built binaries:
v0.9.13
Version 0.9.13 is an optional release before the 0.10.0 hard fork upgrade, which enables node operators to perform 0.10.0 upgrades through Cosmovisor. Operators planning to use Cosmovisor to upgrade their clients to 0.10.0 should first update their current story client to to 0.9.13, then upgrade to 0.10.0. Alternatively, they may ignore this release and upgrade directly to 0.10.0 using their preferred upgrade method.
Overview
v0.9.13
is a optional feature release that adds the status
command to the story
CLI to provide the ability to perform automated upgrades for story
clients using cosmovisor. This release version was packaged purely for the sake of enabling operators who want to use cosmovisor for client upgrades to migrate to 0.10.0.
Fixes
- Adds the
status
command to thestory
CLI, which returns the latest block height, enabling cosmovisor to work with automatedstory
upgrades (#108)
Feedback & Support
We value your feedback and encourage you to report any issues or suggestions through our [public issues tracker](https://github.com/piplabs/story/issues). For additional support, please message us in the developer channel of our [public Discord](https://discord.gg/storyprotocol).
Binaries
Users may download the client from our set of pre-built binaries:
v0.9.12
v0.9.12 is a hotfix release for the story consensus client. Validators can optionally update to this stable version for running a node on the latest iliad
network.
Overview
v0.9.12
fixes a logging issue that was adversely affecting block times for a lot of nodes running in DEBUG
mode, and adds a comprehensive set of tests to the staking module.
Fixes
- Removes delegation messages that induced massive log bloating for nodes running in
DEBUG
mode (#72) - Update various ABCI log messages to print in
INFO
mode as opposed toDEBUG
(#73)
Other Updates
- Adds test cases for validator withdrawals (#55)
- Adds test cases for staking contract interactions (#56)
- Adds test cases for the withdrawal queue (#61)
- Adds test cases for validator operations (#66)
- Adds test cases for setting of addresses (#67)
- Adds test cases for validator deposits (#71)
- Adds test cases for contract upgrades (#82)
Feedback & Support
We value your feedback and encourage you to report any issues or suggestions through our public issues tracker. For additional support, please message us in the developer channel of our public Discord.
Binaries
Users may download the client from our set of pre-built binaries:
v0.9.11
v0.9.11 is a maintenance release for the story
consensus client. All validators should use this stable version for running a node on the latest iliad
network and setting up their own validators.
Overview
v0.9.11
adds better validator CLI tooling for simplifying the process of running your own validator and interacting with others- This change also finalizes all
iliad
network and genesis configurations - A bug fix was added that caused occasional errors during validator key exports generated on client initialization
Users may download from the client from our set of pre-built binaries:
v0.9.10
v0.9.10 is the first official public release for the story
consensus client. For interactions with the Iliad
public testnet, users should install this version.
Overview
v0.9.10
introduces a fully working consensus client and network that allows for validator creation, deposits, withdrawals, rewards re-delegation, slashing, and a pipeline for node upgrades- All validator logic is supported through the
IPTokenStaking
andIPTokenSlashing
contracts - All transactions are fully EVM equivalent, supported via an Engine-API powered communication layer between the consensus and associated execution client
- Supports automatic distribution of staking rewards via partial withdraws
Users may download from the client from our set of pre-built binaries: