executive high priest of blowing your mind
What would Bitcoin validation look like if it were truly side-effect free and built from first principles? This series explores the real boundary between consensus logic and node implementation details.
What would Bitcoin validation look like if it were truly side-effect free and built from first principles? This series explores the real boundary between consensus logic and node implementation details.
It's one of the most fundamental types in Bitcoin Core - and it's not a Regular C++ type. It can't be assigned and the comment explaining it is wrong. Here's how to fix it, one refactoring step at a time.
My opinionated vision on language bindings and ABI stability
A familiar pattern hidden in plain sight inside Bitcoin Core turns out to raise a surprisingly fundamental question about modern C++ API design.
A deep dive into rethinking Bitcoin Bitcoin serialization from first principles: ditching overloaded C++ machinery in favor of explicit, composable encoders that make every byte intentional, visible, and consensus-safe.
What would Bitcoin validation look like if it were truly side-effect free and built from first principles? This post explores the real boundary between consensus logic and node implementation details.
The BlockTreeEntry type leaks internal details and couples clients to Bitcoin Core's implementation. The Kernel API is leaner, more stable and more robust without it.
While reviewing and refactoring the Bitcoin Kernel API, I wrote several design documents . One topic I have not yet covered is the concept of "interfaces."
As a student, I wanted to become a game programmer. I learned C++ with the goal of writing a computer game. My vision was to create something like a decentralized version of "Ultima Online."
In the following, I will try to address all your questions regarding import/export with CMake. To aid in this task, I have set up four example projects, which form a so-called diamond of death dependency graph.
Ranges, ranges everywhere. Or why I should definitely meet TheCharlatan on a regular basis.
There are too many ways to build and test a project with CMake. On the other hand, there is too little knowledge out there about those ways. As a consequence, people wrap the CMake invocation in custom scripts written in Bash, Python, TypeScript, etc.
The FindGTest module that ships with CMake provides the command GTEST_ADD_TESTS , which registers all the test cases from a test executable with CMake so they are listed individually in the report generated by CTest.
There are formatting options that are a matter of taste and there are formatting options that severely affect readability and maintenance.
Moving my blog from GitHub Pages to Nostr Long-form Content notes
It really saddens me whenever I see code like this.
Previously, I wrote about the four different ways of configuring a dashboard client script with CTest.
My presentation at C++Now 2017 won the "Most Educational Session" award.
Slides of a presentation I gave 21 May 2015 for the C++ user group meeting.
There are too many ways to build and test a project with CMake. On the other hand, there is too little knowledge out there about those ways. As a consequence, people wrap the CMake invocation in custom scripts written in Bash, Python, Typescript etc.
