Do you want #30955 next?

There for it!

Bitcoin Core just got its first proper useful ipc interface. If used externaly, it is more performant than querying templates through rpc, which may result in more efficient mining operations. https://github.com/bitcoin/bitcoin/pull/30510#event-14405793595

Ok, getting rid of it.

for (bool fLoaded = false; !fLoaded && !ShutdownRequested(node);) {

Probably the worst piece of code remaining in the Bitcoin Core codebase. Produced two bugs this year that went into master and countless more during review cycles. And it is just there for the gui!

Ten guys jump one, what a man

You fight each other, the police state wins

Stab your backs when you trash our halls

Trash a bank if you've got real balls

How is it getting and submitting work?

Yeah, the spam is starting to make this less fun again.

Found some new future directions to take for enabling better use cases for the kernel library. Going to be refactoring some more code over the next few weeks to make implementing them a bit easier.

I don't think this makes much sense.

The spambots are really here now.

Gave up again, the interface is just too specialized, but maybe I can eventually find a way to aggregate some of the operations.

2, and a couple of branches

Amazing! Can't believe you people are pulling off what all these shitcoin foundations have been droning on about for the last decade and never executed on.

Sorted.

A lot of time being spent on refactoring PRs at the moment. Not sure how I feel about that. There are so many feature PRs starving for reviews and the benefits of some of these refactors are questionable.

My first deep dive into libmultiprocess led to some pull requests and discussions on what to improve.I also contributed some high-level docs for the internal components. Now that I have an idea of the components involved, the next time I revisit it I want to focus on the serialization hooks and the thread context passing. Those still puzzle me a bit.

Amethyst, because it is convenient on my mobile.

Like what are the expected runtime and memory complexities, how can I trust its output, does it need a root of trust to guarantee stuff is validated against the chain tip, how much "system-dependent" stuff is allowed in the binaries, if none, can I inject system-dependent data models for storage somehow?

I need to find someone to explain the use cases behind risc0 and its potential applications for validating Bitcoin transactions and blocks. The important information is still all over the place and I am having a hard time grasping the actually important parts.