Skip to content

Releases: forbole/callisto

v4.0.0

26 Jun 17:35
Compare
Choose a tag to compare

Notes

This version is thought to be used with Cosmos SDK v0.47.x.

Changes

Parse Command

  • (#492) Add parse command for periodic tasks: x/bank total supply, x/distribution community pool, x/mint inflation, pricefeed token price and price history, x/staking staking pool

Upgrade Module

  • (#467) Store software upgrade plan and refresh data at upgrade height

Staking Module

  • (#443) Remove tombstone status from staking module(already stored in slashing module)
  • (#455) Added unbonding_tokens and staked_not_bonded_tokens values to staking pool table
  • (#536) Fix PoolSnapshot tokens type from sdk.Int to sdkmath.Int

Gov Module

  • (#461) Parse x/gov genesis with genesisDoc.InitialHeight instead of the hard-coded height 1
  • (#465) Get open proposal ids in deposit or voting period by block time instead of current time
  • (#489) Remove block height foreign key from proposal_vote and proposal_deposit tables and add column timestamp
  • (#499) Check if proposal has passed voting end time before marking it invalid
  • (#523) Update proposal snapshots handling on block

Daily refetch

  • (#454) Added daily refetch module to refetch missing blocks every day

Hasura

  • (#473) Improved Hasura permissions
  • (#491) Add host address to Hasura actions

Dependencies

  • (#542) Updated Juno to v5.1.0

v3.2.0-stargate

03 Aug 13:25
Compare
Choose a tag to compare

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos Stargate. If you want to integrate with a chain running Cosmos v0.43.0 or later, please use v3.2.0 instead.

Changes

Mint module

  • (#432) Update inflation rate when mint param change proposal is passed

Gov module

  • (#401) Update the proposal status to the latest in bdjuno parse gov proposal [id] command
  • (#430) Update the proposals that have invalid status but can still be in voting or deposit periods

Dependencies

  • (#440) Updated Juno to v3.3.0

v3.2.0

03 Aug 13:24
Compare
Choose a tag to compare

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos v0.43.0 or later. If you want to integrate with a chain running Cosmos Stargate, please use v3.2.0-stargate instead.

Changes

Mint module

  • (#432) Update inflation rate when mint param change proposal is passed

Gov module

  • (#401) Update the proposal status to the latest in bdjuno parse gov proposal [id] command
  • (#430) Update the proposals that have invalid status but can still be in voting or deposit periods

Dependencies

  • (#440) Updated Juno to v3.3.0

v3.1.0-stargate

27 May 13:43
Compare
Choose a tag to compare

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos Stargate. If you want to integrate with a chain running Cosmos v0.43.0 or later, please use v3.1.0 instead.

Dependencies

  • (#412) Updated Juno to v3.2.1

Changes

Hasura

  • (#395) Remove time label from Hasura Prometheus monitoring

Bank module

  • (#410) Change total supply query from only 1 page to all pages

v3.1.0

27 May 13:42
Compare
Choose a tag to compare

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos v0.43.0 or later. If you want to integrate with a chain running Cosmos Stargate, please use v3.1.0-stargate instead.

Dependencies

  • (#412) Updated Juno to v3.2.1

Changes

Hasura

  • (#395) Remove time label from Hasura Prometheus monitoring

Bank module

  • (#410) Change total supply query from only 1 page to all pages

v3.0.1-stargate

12 Apr 13:58
Compare
Choose a tag to compare

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos Stargate. If you want to integrate with a chain running Cosmos v0.43.0 or later, please use v3.0.1 instead.

Changes

This version replaces v3.0.0-stargate with a minor update to solve an initialization bug.

v3.0.1

12 Apr 13:54
Compare
Choose a tag to compare

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos v0.43.0 or later. If you want to integrate with a chain running Cosmos Stargate, please use v3.0.1-stargate instead.

Changes

This version replaces v3.0.0 with a minor update to solve an initialization bug.

v3.0.0-stargate

12 Apr 07:11
Compare
Choose a tag to compare

⚠️ PLEASE DO NOT USE ⚠️

This version contains a bug which makes it impossible to be used due to different IBC version being used at the same time. Please use v3.0.1-stargate instead.

Notes

This version introduces breaking changes to transaction and message PostgreSQL tables. It implements PostgreSQL table partitioning to fix slow data retrieval from database that stores large amount of transactions and messages. Read more details about migrating to v3.0.0

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos Stargate. If you want to integrate with a chain running Cosmos v0.43.0 or later, please use v3.0.0 instead.

Changelog

New features

CLI

  • (#356) Implemented migrate command to perform easy migration to higher BDJuno versions
  • (#356) Updated parse-genesis command to parse genesis file without accessing the node

Database

  • (#356) Added PostgreSQL table partition to transaction and message table
  • (#356) Created new messages_by_address function

Changes

Hasura

  • (#377) Updated Hasura metadata
  • (#381) Hasura actions are now a module

Dependencies

  • (#356) Updated Juno to v3.0.0

v3.0.0

12 Apr 07:15
Compare
Choose a tag to compare

⚠️ PLEASE DO NOT USE ⚠️

This version contains a bug which makes it impossible to be used due to different IBC version being used at the same time. Please use v3.0.1 instead.

Notes

This version introduces breaking changes to transaction and message PostgreSQL tables. It implements PostgreSQL table partitioning to fix slow data retrieval from database that stores large amount of transactions and messages. Read more details about migrating to v3.0.0

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos v0.43.0 or later. If you want to integrate with a chain running Cosmos Stargate, please use v3.0.0-stargate instead.

Changelog

New features

CLI

  • (#356) Implemented migrate command to perform easy migration to higher BDJuno versions
  • (#356) Updated parse-genesis command to parse genesis file without accessing the node

Database

  • (#356) Added PostgreSQL table partition to transaction and message table
  • (#356) Created new messages_by_address function

Changes

Hasura

  • (#377) Updated Hasura metadata
  • (#381) Hasura actions are now a module

Dependencies

  • (#356) Updated Juno to v3.0.0

v2.0.2-stargate

11 Mar 06:47
Compare
Choose a tag to compare

Notes

Version v2.0.2 fully replaces v2.0.0 due to a wrong tagging being done (see #357). Please **do not use v2.0.0 anymore and use v2.0.2 instead.

Cosmos compatibility

This tag is thought to be used with chains that are running Cosmos Stargate. If you want to integrate with a chain running Cosmos v0.43.0 or later, please use v2.0.2 instead.

Hasura actions

Starting with v2.0.0, certain address-specific data are no longer periodically parsed from the node and stored in the database.
Instead, those data are obtained directly from the node when necessary thanks to the Hasura Actions service.

Here's the list of data which are acquired through Hasura Actions:

  • Of a certain address/delegator:
    • Account balance
    • Delegation rewards
    • Delegator withdraw address
    • Delegations
    • Total delegations amount
    • Unbonding delegations
    • Total unbonding delegations amount
    • Redelegations
  • Of a certain validator:
    • Commission amount
    • Delegations to this validator
    • Redelegations from this validator
    • Unbonding delegations

To activate Hasura actoins, simply run:

$ bdjuno hasura-actions

It is also recommended to run Hasura Actions as a system service:

$ sudo tee /etc/systemd/system/hasura-actions.service > /dev/null <<EOF
[Unit]
Description=BDJuno Hasura Actions
After=network-online.target
[Service]
User=$USER
ExecStart=$GOPATH/bin/bdjuno hasura-actions
Restart=always
RestartSec=3
LimitNOFILE=4096
[Install]
WantedBy=multi-user.target
EOF

Migrate

If you are running BDJuno v1, you can run the following command to migrate to v2:

bdjuno migrate