Chris Guimarães
Chris Guimarães
Currently there is an issue with the `workers` arguments passed to the Parquet based event-replay. It is accepting any name different from `workers`. ``` $ ... from-parquet-events --workers=8 ```
This issue serves as a placeholder to add the profiling and benchmark findings to the contribution guidelines or best practice documentation. /cc @saralab @jbencin
When issuing the command `$ ordhook config new` a general error messaging is raised: ``` Aug 30 12:10:06.841 ERRO Invalid combination of arguments ``` Can we make this error more...
Several times, during the `ordhook` usage, is need to provide the target network as an argument. This makes the input a bit verbose. Proposal: Use the content of the `Ordhook.toml`...
Validate this [fix](https://github.com/hirosystems/stacks-blockchain-api/pull/1926) by running the TSV export and event-replay.
An issue has happened, in production, where the Chainhook’s chain segment became outdated. And since the code base is not prepared to handle that, only restoring the Chainhook's chain state...
When a Chainhook node is restarted, it appears to lose the Bitcoin node state. This can cause issues, like the one below, to be triggered by Grafana. ``` The Chainhook...
It is possible to generate a contract principal using ``` (principal-construct? 0x15 0x5fe781ad4656928d3f52419118cdd229d0e75566 "u7E0cd1") ``` However, decomposing the generated principal into its components is not possible. ``` (principal-destruct? 'SN1FYF0DD8SB9539ZA90S266DT8MX1STNCSV9F6Z0.u7E0cd1) ```...
Chainhook relies on an RPC library that is outdated (https://github.com/rust-bitcoin/rust-bitcoincore-rpc/tree/v0.18.0). This library does not support newer Bitcoin versions (the latest being v0.21.0), and, consequently, Chainhook is also locked to older...
WIP: Changes needed to enable block replay in the clarity-wasm runtime.