Namada 0.17.2

Namada 0.17.2 is a minor release featuring improvements to the client stability.

BUG FIXES

• Do not add address if it already exists in the wallet.
  (#1504)
• When processing slashes, bonds and unbonds that became active after
  the infraction epoch must be properly accounted in order to properly
  deduct stake that accounts for the precise slash amount. A bug
  is fixed in the procedure that properly performs this accounting.
  (#1520)
• Fix the message when a client is waiting for a node to sync on queries or
  transactions. (#1522)
• This change will enable usage of the Namada SDK to create MASP transactions
  from non-CLI clients. (#1524)
• Fixing how token balances are displayed in case of missing --token option.
  (#1528)
• The slashed token amounts contained inside the bond and unbond information
  returned by the PoS library fn bonds_and_unbonds are fixed and properly
  computed. (#1533)
• PoS: Fixed the client to change configuration to validator
  mode after a successful init-validator transaction.
  (#1549)
• PoS: fixed a check for whether a given address belongs to a
  validator account to work properly with newly created accounts.
  (#1553)
• Fixes the slash rate output in the query_slashes client
  command and some redundancy in misbehavior reporting logs.
  (#1558)

IMPROVEMENTS

• Add a command, namadac utils default-base-dir, to
  print the default base directory the command
  line would use were one not provided by the user.
  (#1491)
• Improve the established address in-memory representation
  and use a full SHA-256 digest for their generation.
  (#1510)
• Improve the implicit address and PKH in-memory representation.
  (#1512)
• Improve help message for address add command
  (#1514)
• PoS: make a re-usable bonds and unbonds details query.
  (#1518)

Namada 0.17.1

Namada 0.17.1 is a scheduled minor release featuring several improvements to the slashing mechanism,
wallet address derivation, transaction structure and the ledger stability.

BUG FIXES

• Persists a newly added storage field for epoch update blocks delay to be
  available after node restart when not None which may break consensus.
  (#1455)
• Client: Fixed an off-by-one error to stop waiting for start or catch-up when
  max tries are reached. (#1456)
• Include the wasm tx hash instead of the wasm blob when constructing a
  transaction (#1474)
• Fix a client block query to avoid seeing pre-committed blocks.
  (#1534)

DOCS

• Adds specs for gas and fee (#889)

FEATURES

• The implementation of the cubic slashing system that touches virtually all
  parts of the proof-of-stake system. Slashes tokens are currently kept in the
  PoS address rather than being transferred to the Slash Pool address. This PR
  also includes significant testing infrastructure, highlighted by the PoS state
  machine test with slashing. (#892)
• Implements HD wallet derivation / recovery from a given mnemonic code
  (#1110)
• PoS: Added a client command find-validator --tm-address <address>
  to find validator's Namada address by Tendermint address.
  (#1344)

IMPROVEMENTS

• Make Namada transactions signable on hardware constrained wallets by making
  them smaller. (#1093)
• Added multicore feature flag to the namada and namada_core
  crate that can be switched off for JS WASM build.
  Additionally, changed the trait ShieldedUtils to be async.
  (#1238)
• Zeroizes memory containing passphrases in wallet.
  (#1425)
• Added some missing cli option for cli wallet
  (#1432)
• Improve logging error when submiting an invalid validator commission change tx
  (#1434)
• Correct a typo in the error change commission error handling
  (#1435)
• Improve the reveal tx naming in cli
  (#1436)
• Improve computations readability when calculating inflations
  (#1444)
• Remove abci++ dependencies (#1449)
• Reorganize the structure of transactions
  (#1462)
• Improved log entries related to PoS system.
  (#1509)

Namada 0.15.4

Namada 0.15.4 is a maintenance release addressing the invalid creation of blocks due to missing replay protection checks during prepare
proposal.

BUG FIXES

• Fixed a bug in prepare_proposal causing the creation
  of blocks containing already applied transactions.
  (#1405)

IMPROVEMENTS

• Make Tendermint consensus paramenters configurable via Namada configuration.
  (#1399)
• Improved error logs in process_proposal and added more info to
  InternalStats (#1407)

Namada 0.16.0

Namada 0.16.0 is a regular release focused on providing the Namada SDK
to developers.

DOCS

• Added page table-of-contents via mdbook-pagetoc plugin for the developer
  documentation. (#1275)

IMPROVEMENTS

• Provide Namada SDK (in particular, the namada crate may now be usefully linked into user applications). (#925)
• Bump RocksDB crate to 0.21.0 to address compilation errors on certain C++
  toolchains. (#1366)

Namada 0.15.3

Namada 0.15.3 is a maintenance release addressing the creation of
incorrect data directories on Mac and Windows platforms.

The default data directories after this patch are:

• Linux: $XDG_DATA_HOME/namada, falling back to $HOME/.local/share/namada if $XDG_DATA_HOME is unset
• Mac: $HOME/Library/Application Support/Namada
• Windows: %AppDataLocal%\Namada

BUG FIXES

• Place the default data directory in the local rather than the roaming profile
  on Windows. (#1368)
• Use blank qualifier and organization, and upcased Namada, to
  construct default base directories on Mac and Windows platforms.
  (#1369)

Namada 0.15.2

Namada 0.15.2 is a bugfix release containing various fixes, including
a major improvement to storage usage.

BUG FIXES

• Fixed an issue with the iterator of LazyMap with a nested LazyVec collection
  that would match non-data keys and fail to decode those with the data decoder.
  (#1218)
• PoS: fixed a function for clearing of historical epoched data
  (#1325)

FEATURES

• Added a utility command to the CLI to compute a tendermint address from a
  namada public key. (#1152)

IMPROVEMENTS

• Changed the default base directory. On linux, the default path will be $XDG_DATA_HOME/com.heliax.namada, on OSX it will be $HOME/.local/share/com.heliax.namada.
  (#1138)
• RocksDB optimization to reduce the storage usage
  (#1333)

MISCELLANEOUS

• Enabled integer overflow checks in release build.
  (#1295)

Namada 0.15.1

Namada 0.15.1 is a patch release addressing issues with high storage
usage due to duplicative storage of wasm code.

IMPROVEMENTS

• Disable Tendermint tx_index as default
  (#1278)
• Remove wasm code from tx (#1297)

Namada 0.15.0

Namada 0.15.0 is a regular minor release featuring various
implementation improvements.

BUG FIXES

• Fix to read the prev value for batch delete
  (#1116)
• Returns an error when getting proof of a non-committed block
  (#1154)
• Fixed dump-db node utility which was not iterating on db keys correctly
  leading to duplicates in the dump. Added an historic flag to also dump the
  diff keys. (#1184)
• Fixed an issue with lazy collections sub-key validation with the Address
  type. This issue was also affecting the iterator of nested LazyMap.
  (#1212)
• Fixed various features of the CLI output for querying bonds and performing an
  unbond action. (#1239)
• PoS: Fixed an issue with slashable evidence processed
  and applied at a new epoch causing a ledger to crash.
  (#1246)
• Addresses are now being ordered by their string format (bech32m)
  to ensure that their order is preserved inside raw storage keys.
  (#1256)
• Prevent clients from delegating from a validator account to another validator
  account. (#1263)

FEATURES

• Infrastructure for PoS inflation and rewards. Includes inflation
  using the PD controller mechanism and rewards based on validator block voting
  behavior. Rewards are tracked and effectively distributed using the F1 fee
  mechanism. In this PR, rewards are calculated and stored, but they are not
  yet applied to voting powers or considered when unbonding and withdrawing.
  (#714)
• Implements governance custom proposals
  (#1056)
• Adds expiration field to transactions
  (#1123)
• Added a rollback command to revert the Namada state to that of the previous
  block. (#1187)
• Introduced a new ledger sub-command: run-until. Then, at the provided block
  height, the node will either halt or suspend. If the chain is suspended, only
  the consensus connection is suspended. This means that the node can still be
  queried. This is useful for debugging purposes.
  (#1189)

IMPROVEMENTS

• Return early in PosBase::transfer if an attempt is made to transfer zero
  tokens (#856)
• Adds hash-based replay protection
  (#1017)
• Renamed "ledger-address" CLI argument to "node".
  (#1031)
• Added a TempWlStorage for storage_api::StorageRead/Write
  in ABCI++ prepare/process proposal handler.
  (#1051)
• Added a wallet section for token addresses to replace hard-
  coded values with addresses loaded from genesis configuration.
  (#1081)
• Improved the CLI description of the start time node argument.
  (#1087)
• Adds chain id field to transactions
  (#1106)
• update help text on namadc utils join-network so that the url
  displays cleanly on a single line, instead of being cut half way
  (#1109)
• Check in the client that the ledger node has at least one
  block and is synced before submitting transactions and queries.
  (#1258)

MISCELLANEOUS

• Clean up some code relating to the Ethereum bridge
  (#796)
• Updated RocksDB to v0.20.1.
  (#1163)

TESTING

• Add utility code for working with test wasms
  (#893)

Namada 0.14.3

Namada 0.14.3 is a bugfix release addressing mainly disk usage
inefficiencies.

BUG FIXES

• Check if validators are valid in pre-genesis setup.
  (#1140)
• Now load conversions from storage even for epoch 1.
  (#1244)

IMPROVEMENTS

• Write Merkle tree stores only when a new epoch
  (#1113)
• Prune old Merkle tree stores.
  (#1237)

TESTING

• Fixed run_ledger_load_state_and_reset test in debug build.
  (#1131)

Namada 0.14.2

Namada 0.14.2 is a maintenance release addressing issues with
proof-of-stake validator logic.

BUG FIXES

• Fixed the PrefixIter order of iteration in the write-
  log to always match the iteration order in the storage.
  (#1141)
• Fixed the init-chain handler to stop committing state to the DB
  as it may be re-applied when the node is shut-down before the
  first block is committed, leading to an invalid genesis state.
  (#1182)
• Fixed an issue in which a validator's stake and validator sets
  data gets into an invalid state (duplicate records with incorrect
  values) due to a logic error in clearing of historical epoch data.
  (#1191)

FEATURES

• Added a lazy set collection.
  (#1196)

IMPROVEMENTS

• Ensure that PoS validator consensus keys are unique.
  (#1197)