v1.3.1

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.