Skip to content
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.

SMASH 1.2.0
Compare
Choose a tag to compare
@tatyanavych tatyanavych released this 27 Oct 19:51
· 106 commits to master since this release
1.2.0
f4a179a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

This update includes new functionality to help stake pools:

  • An interface to get the errors that have caused SMASH to not list the pool metadata. This will help SPOs to diagnose the problem with their pool metadata not showing up in wallets.
  • An interface to get the list of pool ids that have been delisted by the SMASH server operator's policy.
  • A health-check interface to confirm that a SMASH server is operating.

It also includes improvements in logging, DB migration when upgrading, optimisation with data caching.

The underlying database has no breaking changes, therefore the database does not need to be dropped and re-created. All the user has to do is run SMASH, as usual; it will take care of the migration.

Compatible with cardano-node 1.21.1.

New Features

  • [CAD-1823] - Stake pools has issues list #90
  • [CAD-1824] - Delisted stake pools are provided #83
  • [CAD-1838] - Whitelisting (listing) returns delisted stake pools to be visible #87
  • [CAD-2074] - Health check endpoint provides the status and the version from the SMASH server, currently, the status is always OK when SMASH is up and running #101

Improvements

  • [CAD-1926] - Retired pools are ignored #89
  • [CAD-2061] - Logs are improved; information about cause of an error occurred is added #79
  • [CAD-1358] - The caching headers for the HTTP server are returned #80
  • [CAD-2093] - Qualified module names are used to ensure the reuse of the SMASH library #103
  • [CAD-2085] - Migration scripts for SMASH upgrade are used to avoid database drop

Resolved issues

  • [CAD-2088] - Made paths relative to the configuration file, not the executable #100

Known issues

  • There are known issues regarding UX when using the SMASH admin commands
  • There are no delete commands, and all actions must be cleared from the database

Documentation

Smash documentation

Supported Platforms

  • Linux 64-bit

Sign off

Role Approval
Technical Lead ✔️
QA Engineer ✔️
Operations ✔️
Release Manager ✔️
Assets 2