December 2022 Conseil Release

This release broadly adds support for the Tezos Lima protocol. Details may be found at https:/Cryptonomic/Conseil/milestone/15?closed=1.

There are no database changes.

September 2022 Conseil Release

This release broadly adds support for the Tezos Kathmandu protocol. Details may be found at https:/Cryptonomic/Conseil/milestone/14?closed=1.

There are database schema changes for new operation types. One can sync from scratch or amend an existing instance with the following SQL statements:

alter table tezos.operations
    add eventtype varchar;

alter table tezos.operations
    add tag varchar;

alter table tezos.operations
    add payload varchar;

alter table tezos.operations
    add solution varchar;

alter table tezos.blocks
    add consumed_milligas numeric;

alter table tezos.operations
    add consumed_milligas numeric;

A database dump from a full resync from scratch can be found at https://conseil-snapshots.s3.amazonaws.com/conseil_20220916_directory_format.zip.

Docker tag: conseil:2022-september-release-45

July 2022 Conseil Release

This release improves fork handling and support for the Jakarta protocol.

Changes:

• Fix for fork handling issues (#1083)
• Lorre no longer stops when it encounters an unknown operation type (#1098)
• Fix for missing cycle / period information (#1099)

There are no schema changes since the June release so a re-sync is not needed.

June 2022 Conseil Release

This releases focuses on support for the Tezos Jakarta protocol.

Changes:

• Support for Jakarta (#1093, #1097)
• Fixed bug due to which some account updates were missing in accounts_history (#1095)
• Fixed bug which caused missing metadata (#1094 )

There are schema changes in the database due to which a full re-sync is required. We have provided a database dump at https://conseil-snapshots.s3.amazonaws.com/conseil_20220610 in order to shorten the sync process.

April 2022 Conseil Release

This release primarily addresses performance issues with the Conseil API.

Changes:

• Fix for API performance issue under high load (#1090)
• Fix for slow pre-caching of metadata (#1085)
• Fix for failing Docker build (#1092)
• Processing of a missing protocol I operation (#1084)
• New Conseil regression testing DSL (#1088)

There are no schema changes and a full sync is not required for this release.

March 2022 Conseil Release, part 2

This release fixes a performance issue with the original March release. The database dump and new SQL schema from the March release are still applicable to this release

Changes

• High load and 500s fix (#1087)

March 2022 Conseil Release

This is a major release with several new features and includes breaking changes to the database schema.

Changes

• General support for the Ithaca protocol (#1063,#1078,#1079,#1080, #1081 )
• Adding offset support to lorre (#1061)
• Support of the views to the micheline/michelson parser (#1054)
• Handling of chain reorganizations ( #1048, #1066, #1067, #1068)
• Bug Fixes ( #1051 , #1065,#1076,#1077,#1053)
• Code and build cleanup (#1052,#1049 , #1055, #1062 ,#1050)
• Metadata updates (#1071,#1075)

As such, existing Conseil databases are not compatible with the new release. You may create a new database using the latest schema and re-sync the whole chain from scratch yourself or download our snapshot from AWS S3 (Postgres custom format).

November 2021 Conseil Release

This is a major release with several new features and includes breaking changes to both the config file format and the database schema.

Changes

• General support for the Hangzhou protocol (#1043, #1051, #1053)
• Change to config file format (#1025)
• Handling of 'local' forks (#1048)
• Added a big_maps_contents_history table (#1012)
• Support for countDistinct aggregations (#1027)
• Added ordering to complex operations with internal elements (#1035)
• Registered tokens format change to JSON (#1021)
• Code and build cleanup (#984, #971, #1026, #1030, #1032, #1036, #1044, #1049)
• Metadata updates (#997, #998, #1001, #1004, #1005, #1007, #1008, #1009, #1037)

Handling breaking changes to the config file format

According to the existing config file format, Conseil expected details of only one database, e.g.:

conseil {
 hostname: "0.0.0.0"
 port: 1337

 db {
  dataSourceClass = "org.postgresql.ds.PGSimpleDataSource"
  properties {
    # Replace the below lines with details of your database configured with the Conseil database schema
    user = "myuser"
    password = "mypassword"
    url = "jdbc:postgresql://localhost:5432/conseil"
  }
  numThreads = 20
  maxConnections = 20
}

lorre.db = ${conseil.db}

Now we have one database per network in the config file, e.g.:

platforms: [
  {
    name: "tezos"
    network: "mainnet"
    enabled: true
    node: {
        #Replace the below entries with the address of your Tezos node
        protocol: "http",
        hostname: "127.0.0.1",
        port: 8732
        path-prefix: ""
    }
      db {
        dataSourceClass = "org.postgresql.ds.PGSimpleDataSource"
        properties {
          # Replace the below lines with details of your database configured with the Conseil database schema
          user = "myuser"
          password = "mypassword"
          url = "jdbc:postgresql://localhost:5432/conseil"
        }
        numThreads = 20
        maxConnections = 20
      }
  }
]

See https:/Cryptonomic/Conseil/wiki/Configuring-Conseil for a full spec of the latest config file format.

Handling breaking changes to the database

There is now a big_maps_contents_history table. In addition, we have added new columns to other tables to support additional fork handling behaviors. Finally, there are new tables for in-flight changes which aren't officially released yet, e.g. TZIP-16 metadata support.

As such, existing Conseil databases are not compatible with the new release. You may create a new database using the latest schema and re-sync the whole chain from scratch yourself or download our snapshot from AWS S3 (Postgres custom format).

April 2021 Conseil Release

Enhancements:

• Florence protocol support, #985 #991

Bug fixes

• Fixed handling of data from new governance periods (reported by TezBlock), #995
• Fixed parsing of pairs during Micheline to Michelson conversion, #990

There are no schema changes.

No resync is needed unless a complete dataset for all governance periods is needed in the blocks table.

March 2021 Conseil Release

Features

• The big_map_contents table has been expanded: #970
• New indexes for big_map_contents: #972
• Updates metadata for Tezos addresses

Bug fixes

• Conseil should no longer be stalled by certain queries: #968

This release has schema changes so a full resync is needed. Alternatively, a database dump can be downloaded from https://conseil-snapshots.s3.amazonaws.com/conseil_20210325_custom_format.dump to save time.