I was wrong in my previous comment, changing the name of fields in protobuf files does not break compatibility for clients of Chronik.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 17 2025
Feb 16 2025
Feb 15 2025
Partial review up to and including ecash-agora (just a comment nit)
Partial review (everything cashtab)
Partial review up to and including cashtab/src/airdrop/index.ts
remove debugging print
Feb 14 2025
clippy
Feb 13 2025
Feb 12 2025
Feb 11 2025
rebase again
rebase, nit
rebase. I'm convinced the feature_assumevalid.py failure is unrelated to this diff
Feb 9 2025
Feb 8 2025
need to investigate that CI second failure (the first one is clearly unrelated)
rebase
Feb 7 2025
Feb 6 2025
squash with 26282 (more helpful error message)
Feb 5 2025
Feb 4 2025
Note that the feature_deterministic_chain_setup.py test only exists in Bitcoin ABC, Bitcoin Core does not have it. We added it to demonstrate that the hardcoded regtests chainparams (block hashes and txoutsetinfo), which differ from Core due to differences in the block header format, are actually correct.
Feb 3 2025
Feb 1 2025
rebase
Jan 31 2025
Unrelated failure, maybe fixed by https://github.com/bitcoin/bitcoin/pull/26651
rebase
The previous CI failure is unrelated
Jan 30 2025
the failure seems unrelated, this diff shouldn't affect chronik_plugins, but i'll investigate just to be sure
The getavalanchepeerinfo errors probably because a proof is not yet registered when it is called.