Skip to content

Releases: hirosystems/chainhook

v1.8.0

12 Aug 21:40
fb1e9ac
Compare
Choose a tag to compare
Merge pull request #637 from hirosystems/chore/merge

chore: merge from main

v1.7.0

05 Jul 16:59
8135e5e
Compare
Choose a tag to compare

1.7.0 (2024-07-05)

New Features

  • predicate validation (#611)
  • improve chainhook-sdk interface (#608)

Bug Fixes

  • allow aborting a predicate scan (#601)

CI

  • add snapcraft.yaml (#607) - releases are now available on the snap store!
  • winget pkg version bump (#606) - releases are now available on winget!

v1.6.2

06 Jun 20:20
376a2c3
Compare
Choose a tag to compare
chore(release): publish v1.6.2 (#604)

v1.6.1

15 May 16:02
ddb1e41
Compare
Choose a tag to compare

1.6.1 (2024-05-15)

Bug Fixes

v1.6.0

09 May 00:54
Compare
Choose a tag to compare

1.6.0 (2024-05-09)

Features

  • add Bitcoin transaction index to typescript client (#568) (6f7eba4)

Bug Fixes

  • add stacks event position to ts client (#575) (3c48eeb)
  • add starting stacks height for prometheus metrics (#567) (6a8c086)
  • make bitcoin payload serialization deserializable (#569) (5f20a86)
  • set Interrupted status for streaming predicates that fail (#574) (11bde53), closes #523
  • shut down observer on bitcoin block download failure (#573) (f3530b7), closes #572

v1.5.1

12 Apr 20:31
Compare
Choose a tag to compare

1.5.1 (2024-04-12)

Bug Fixes

  • correctly track bitcoin block append metrics; add additional metrics (#563) (f85ac9e), closes #562

v1.5.0

06 Apr 03:46
Compare
Choose a tag to compare

1.5.0 (2024-04-06)

Features

Bug Fixes

  • build error (03b3938)
  • log errors on block download failure; implement max retries (#503) (3bfb0e1)
  • metrics: update latest ingested block on reorg (#515) (823713a)
  • order and filter blocks used to seed forking block pool (#534) (a2865b7)
  • revisit 7+ blocks reorg handling (#553) (184fd07)
  • seed forking handler with unconfirmed blocks to improve startup stability (#505) (b77aca2), closes #487
  • skip db consolidation if no new dataset was downloaded (#513) (b1469a6)
  • update scan status for non-triggering predicates (#511) (32cdfee), closes #498

v1.4.1

02 Apr 17:06
Compare
Choose a tag to compare

1.4.1 (2024-04-02)

Bug Fixes

  • limit scope of stacks_rw_db usage to free lock (#543) (0c287ca)
  • resolve dependencies (#548) (86334f4)
  • return unsupported kind for PoisonMicroblock (#545) (123ec9d)

v1.4.0

27 Mar 21:24
Compare
Choose a tag to compare

1.4.0 (2024-03-27)

Features

  • detect http / rpc errors as early as possible (ad78669)
  • use stacks.rocksdb for predicate scan (#514) (a4f1663), closes #513 #485

Bug Fixes

v1.3.1

14 Feb 23:35
Compare
Choose a tag to compare

1.3.1 (2024-02-14)

Thanks for using Chainhook! See our README for instructions on installing the latest version. Thank you to @janniks who contributed to this release, and to @aulneau who opened an issue that was fixed in this release.

If you're running a Chainhook node (i.e. chainhook service start ...), be sure to check out this note with some additional directions for enabling a fix.

Bug Fixes 🐛

fix: correctly determine PoX vs PoB block commitments (#499)

This fix changes some logic when parsing block data to correctly identify when a Stacks Block Commit is a PoX or PoB block commitment.

fix: add event index to transaction events (#495)

This PR adds the previously missing position field to a Stacks transaction event:

 "transactions": [
   {
     "metadata": {
       ...
       "receipt": {
         ...
         "events": [
           "position": { // new field
             "index": 0 
            },
            ...
         ]
       }
     }
  }
]
Note: Any users running a Chainhook node (i.e. `chainhook service start ...`) will not have transaction event positions stored in the database.

Because of this, all event position will have a value of:

"position": {
  "index": 0
}

To rebuild the database with this data filled in:

  • Upgrade to the latest version of Chainhook
  • Delete the stacks.rocksdb folder inside the working_dir set in your Chainhook.toml
  • Rerun Chainhook

This will rebuild your Stacks database from scratch.