bitcoin/master 07c59ed Casey Carter: Don't derive secure_allocator from std::allocator
[bitcoin] ismaelsadeeq opened pull request #28157: test doc: tests `acceptstalefeeestimates` option is only supported on regtest chain (master...07-2023-avoid-serving-stale-fees-follow-up) https://github.com/bitcoin/bitcoin/pull/28157
Before only maintainers could add PRs to the high prio for review (https://github.com/orgs/bitcoin/projects/1/views/4) but at some point that changed and I was able to add items myself. I assumed that's for every "member" of the org, but I see MacroFake and hebasto yesterday asked for PRs to be added to the list on their behalf which I find surprising - why not add it yourself?
I'd like to write a third party app that indexes some blockchain data but I'd like to rely on my local bitcoin-core node to handle consensus and validation, etc. Is there a guide somewhere on how to do this? basically i need the third party app to receive valid blocks from my local bitcoin-core node. i am not sure if it'd be better to use RPC for
[bitcoin] vasild opened pull request #28077: I2P: also sleep after errors in Accept() & destroy the session if we get "Session was closed" (master...i2p_accept_issue22759) https://github.com/bitcoin/bitcoin/pull/28077
https://github.com/bitcoin/bitcoin/pull/28048 is close to the finish line. Merging it would conclude the "prune the unnecessary .cpp files (and their respective headers)" (stage 1, step2) part of the project, which is nice :)