Bitcoin Core's developers have spent much of the past year defending their work to skeptical observers. The reference implementation's dev team improved its communication strategy over the last six mo
Bitcoin Core's developers have spent much of the past year defending their work to skeptical observers. The reference implementation's dev team improved its communication strategy over the last six months, yet plenty of community members say better transparency still matters. Eric Lombrozo, CEO of Ciphrex and a longtime Bitcoin Core contributor, took on the role of public face for the project. He fields questions from journalists and the broader Bitcoin audience about the work underway.
Lombrozo sat down with MiningPool to discuss where Bitcoin Core is heading and how its process might shift in coming months.
The developers building Bitcoin have come to see the blockchain's core function as a settlement system. Think of it like the final ledger that no one can reverse. Higher layers, like the Lightning Network, handle the rapid back-and-forth transactions that settlement layers weren't designed for. This architectural thinking shapes how the team approaches code changes.
"Changes to consensus rules bring serious complications and can spark real fights," Lombrozo said. "We should work toward a model where we don't have to alter them very often."
When programmers can test new ideas without breaking the underlying rules everyone relies on, more of them jump in and experiment. Lombrozo outlined his vision: "The consensus layer should handle disputes and compact proofs. Everything else should live above it." Payment channels, sidechains, and other second-layer systems let developers add features faster than they could through blockchain changes.
SegWit, BIP 9, and sidechains all point toward the same goal: a development process that moves without getting bogged down in governance questions.
Johnson Lau, new to the core contributor ranks, is working on new opcodes for the Bitcoin scripting language. He wants to unlock features like enhanced privacy and atomic swaps across blockchains. "SegWit and BIP 9 make introducing new scripting systems like MAST much simpler than they used to be," Lau told MiningPool. "We've talked about enabling new opcodes for ages. I couldn't do this work without the foundation SegWit and BIP 9 give us."
This is Lau's first C++ project. The fact that he can tackle it shows how much SegWit simplifies scripting updates.
None of this happens without agreement on how decisions get made in the first place. Bitcoin governance remains unsettled territory. Blockchain systems are so young that no one has figured out how to manage them well.
Bitcoin Core wants a more transparent development track, but Lombrozo stopped short of endorsing a model where developers push changes to miners for approval. "We need a proper review process before anything goes live. Soft forks that won't activate should never ship," he said.
In 2016, Bitcoin Core and the mining community found better ways to work together. How BIP 9's rollouts for CHECKSEQUENCEVERIFY and SegWit land over the next few weeks and months will show if this alignment sticks.
Lombrozo noted a key constraint: "Miners have the power to block soft forks. Hard forks are far tougher. Miners can't stop those." Bitcoin Classic and Bitcoin XT offer different visions, but they've failed to gain the support needed to challenge Bitcoin Core's direction.
Once developers get more room to experiment at higher protocol layers, Bitcoin innovation should accelerate.
