Blockchain Engineering Needs Tighter Collaboration Between Protocol and Infrastructure Teams

At Futura Camp during Berlin Blockchain Week 2026, Coinspaid Dev Executive Leader Alexey Tulia highlighted a growing gap between protocol development and infrastructure engineering. His talk focused on how large-scale blockchain systems are shaped not only by design decisions at the protocol level, but also by real-world operational constraints.

As reported by Coinpedia, Coinspaid Dev executive Alexey Tulia urges closer collaboration between protocol and infrastructure teams, the discussion centered on how both sides of blockchain development often optimize for different outcomes, yet depend heavily on each other for long-term network stability and adoption. Tulia drew on more than a decade of experience across multiple blockchain networks in production environments to illustrate where the disconnect typically emerges.

He argued that protocol teams are usually focused on design evolution, scalability concepts, and long-term ecosystem direction, while infrastructure teams deal with immediate operational realities such as performance degradation, unpredictable fees, and cross-chain reliability issues. According to him, this separation limits the industry’s ability to respond quickly to problems that only become visible at scale.

A key part of his message was that many of the most critical limitations in blockchain systems do not appear during development or testing, but only once systems are under sustained real-world usage. Issues like network congestion, fee volatility, and coordination complexity across multiple chains often surface after deployment, forcing infrastructure teams to adapt without always having early input into protocol-level decisions.

Tulia emphasized that blockchain technology has already moved beyond its experimental stage. The focus, he suggested, is no longer on proving viability but on improving operational maturity. In his view, the next phase of development requires systems that remain predictable and efficient even under heavy load and complex network conditions.

He also pointed out that infrastructure operators often lack visibility into upcoming protocol changes, while protocol designers do not always receive structured feedback from production environments. This creates a feedback gap that slows down meaningful improvements across the ecosystem.

Among the practical challenges highlighted in his presentation were:

• Network congestion handling under peak load conditions

• Fee optimization and predictability across different chains

• Reliability of multi-chain operations in production environments

• Limited feedback loops between protocol updates and real-world usage

• Missing or incomplete primitives that affect scalability and usability

Tulia suggested that stronger collaboration mechanisms between both groups could help address these issues more effectively. Instead of operating in parallel tracks, protocol and infrastructure teams could benefit from more continuous exchange of operational data, architectural constraints, and roadmap visibility.

He also linked this perspective to the broader mission of Coinspaid Dev, which brings together engineers working across blockchain infrastructure, distributed systems, cloud technologies, analytics, and cybersecurity. The organization positions itself as an engineering-focused entity aimed at improving how blockchain systems are built and operated at scale.

In closing, Tulia framed the future of blockchain engineering as a coordination challenge as much as a technical one. He argued that improvements such as better tooling, clearer standards, and more consistent primitives will depend heavily on whether protocol designers and infrastructure operators can align more closely in how they define and solve system-level problems.