Bitcoin Pacifica 2015 hosted a governance discussion that brought together some of the most influential voices in the Bitcoin development community. The panel included Gavin Andresen, Chief Scientist
Bitcoin Pacifica 2015 hosted a governance discussion that brought together some of the most influential voices in the Bitcoin development community. The panel included Gavin Andresen, Chief Scientist at the Bitcoin Foundation, and Peter Todd, a researcher deeply involved in Bitcoin's evolution. Despite their reputation for holding divergent views on Bitcoin matters, both participated in exploring the technical and philosophical issues facing the network.
The conversation frequently returned to insights gained from the recent Scaling Bitcoin workshop held in Montreal. When moderator Suhas Daftuar—founder of Chaincode Labs—was asked by Andresen to summarize the rough consensus emerging from Montreal, he outlined several key areas where the developer community appeared aligned.
**Growing Block Capacity Within a Defined Window**
Daftuar indicated that participants at the Montreal gathering had tentatively agreed on moving forward with a block capacity expansion set for a specific timeframe. In his words: "It seemed like there may be consensus among kind of the core developers to — I don't want to put words in people's mouths, so I'm just going to try to describe it as I recall it too — to maybe support a plan that would allow for an increase in the block size over a relatively short timeframe. People are talking in the four-year timeframe-ish."
Many Bitcoin Core developers apparently favor this constrained window because it avoids making assumptions about how computing hardware will evolve. Projecting too far into the future introduces uncertainty about whether the network could handle larger blocks. This hesitation has been expressed by numerous contributors to the project previously.
**Rethinking How We Quantify Block Size**
Another promising avenue discussed in Montreal involved reimagining the metrics used to constrain blocks. Rather than treating block size as an isolated number, the developer community appeared interested in assessing how transaction composition within blocks influences broader network stability.
According to Daftuar: "To do so in a way that wasn't just to look at the block size directly as a single parameter of just making blocks bigger, but also maybe restate or take into account into the way you decide how big a block can be — kind of the effect of the transactions in a block on the overall network's health. The idea being that there can be costs — like unexpected costs from unexpected transaction patterns that you want to minimize."
He illustrated this concept with a concrete example: "For example, the growth of the number of unspent transaction outputs — some goal to keep that from growing just crazily large if somebody were to try to attack the network in that way. So, the idea of using a different metric to decide how to measure the block size was something that was discussed."
**Development Milestone: Hong Kong Ahead**
When attendees pressed for specifics on implementation timing, Andresen outlined the roadmap: "The plan is to have a BIP [Bitcoin Improvement Proposal], an implementation, and some testing done before [Scaling Bitcoin] Hong Kong."
The Montreal gathering functioned primarily as a workshop for identifying and debating scalability challenges. By contrast, the upcoming Hong Kong event will shift focus toward validating concrete technical solutions through rigorous assessment and real-world testing.
Based on reporting from other Montreal participants, industry observers anticipate a possible bump to block sizes reaching 2MB or 4MB. The ultimate success of any increase will hinge on the testing conducted in the months ahead, particularly results that will be presented and scrutinized at the December Hong Kong workshop.
