-
When Chainhook fails to ingest a stacks block, it logs the error [`Unable to process Stacks Block #...`](https://github.com/hirosystems/chainhook/blob/f85ac9e56718264c48a4af33e7d2514319022a2d/componen…
-
With the he current circular dependency between the chainhook and clarinet. (Not at the component level but at repo level.)
Which can make it difficult to upgrade certain components such as clarity-v…
-
I executed the predicate for Contract call and wanted to verify that it runs successfully and that it finds accurate data.
I am searching the BNS contract and looking for name revoked because I can s…
-
Simplifying the chainhook-sdk would be helpful for helping developers building new indexers on top of the chainhook-sdk.
Something like:
```
let indexer = Indexer::new();
indexer.apply_block…
-
When a chainhook-node is re-processing blocks (for whatever reason), it should avoid re-sending blocks to observers when they have been sent in the past.
Data from Redis could help.
-
We need to specify in our documentation that a version of 24.0+ of bitcoind is required to use Chainhook to index a bitcoin node. We should update our readme and this guide: https://docs.hiro.so/chain…
-
It'd be pretty useful to provide a docker compose file, spinning up:
- bitcoind
- chainhook
- ordinals-api
- postgres
-
I am currently trying to package clarinet for NixOS like I talked about in #1515 .
I have the following package definition:
``` Nix
{
lib,
rustPlatform,
fetchFromGitHub,
pkg-config,
…
-
Context:
> would be great to have a testing guide to know how one can use chainhook with CI/CD testing
-
so notes: a ranged chain hook is really cool and should exist, but it should exist in a way that does not lead to a slimeguy situation (mainly due to how the chainhook also can have all the other man…