Missing Inscriptions / Discrepancy between chainhook and hord

[ryanwaits]

Describe the bug When running both chainhook and hord services with the same configuration, there seems to be a discrepancy in the number of triggers being emitted. (chainhook does not pick up any while hord picks up 2)

I was running through the how-to-run-chainhook-as-a-service-using-bitcoind and noticed that there might be missing inscriptions when running chainhook when compared to scanning blocks using hord for streaming activity.

Here is the ordinals.json file

{
  "uuid": "1",
  "name": "Hello Ordinals",
  "chain": "bitcoin",
  "version": 1,
  "networks": {
      "mainnet": {
          "start_block": 767430,
          "end_block": 767753,
          "if_this": {
              "scope": "ordinals_protocol",
              "operation": "inscription_feed"
          },
          "then_that": {
              "file_append": {
                  "path": "inscription_feed.txt"
              }
          }
      }

  }
}

Here is a screenshot of the results for running it with chainhook

Here is the result when scanning same blocks with hord, you'll notice it triggered 2 actions

In this particular configuration, since both services are using the same bitcoind configuration - we should expect the same 2 triggers to occur when running both chainhook and hord.

[timstackblock]

I am getting the same thing with chainhooks

[lgalabru]

The ordinals predicates are technically still available in the chainhook repo, but the ordinals indexing logic was moved to ordhook.

[ryanwaits]

got it - thanks! ill assume going forward that predicate will be removed from chainhook, and anything ordinals related will be handled by ordhook

[smcclellan]

We will track fixing the documentation drift in this ticket @LakshmiLavanyaKasturi.

[LakshmiLavanyaKasturi]

@lgalabru, Are we ready to remove Ordinals protocol documentation from the Chainhook docs?

[LakshmiLavanyaKasturi]

I prefer to remove these after the Ordhook documentation is live. @lgalabru WDYT?