How Neti Upgraded Liberland’s Live Substrate Blockchain to EVM Compatibility

Summary: Neti helped Liberland upgrade its already-live Substrate-based Layer 1 blockchain to EVM compatibility without relaunching the chain or breaking existing state, history, token flows, or protocol rules. The project required custom blockchain development, Rust and Substrate engineering, Frontier adaptation, EVM genesis simulation, and careful handling of Substrate/EVM account model differences.

Upgrading a blockchain is already complex. Upgrading a live blockchain to support EVM compatibility - without relaunching the chain, losing historical state, or breaking existing rules, is a different level of custom blockchain development and protocol engineering.

Liberland needed to make its Substrate-based blockchain more interoperable with the broader Web3 ecosystem. The challenge was not to build a new chain from scratch, but to evolve an already-operational Layer 1 infrastructure while preserving continuity for existing users, data, governance logic, and token flows.

Neti helped Liberland implement one of the most significant upgrades in the chain’s history: adding EVM compatibility to a live Substrate-based blockchain.

Project Highlights

About Liberland

Liberland is a digital governance project building blockchain-based infrastructure for transparent, decentralized public administration and citizen interaction.

Neti had already supported Liberland’s blockchain infrastructure over several years, including the development of a custom Substrate-based Layer 1. Since the original blockchain launch, the collaboration has continued through separate project-based engagements, with each initiative adding new functionality and value to Liberland’s existing chain. As the ecosystem evolved, Liberland needed its chain to become more compatible with Ethereum-based tools, wallets, applications, and ecosystem partners.

The next step was clear strategically, but difficult technically: introduce EVM compatibility to a blockchain that was already live.

The Challenge: This Was Not a Greenfield EVM Integration

Most EVM compatibility work starts at the beginning of a chain’s lifecycle. The chain is designed with EVM support from genesis, tooling assumptions are clear, and the architecture can be prepared before users, state, and business logic exist.

Liberland’s case was different.

The blockchain was already operational. It had existing state, historical blocks, token logic, governance assumptions, and production infrastructure. That meant the upgrade could not be treated as a standard implementation.

The risk was especially significant because Liberland uses the blockchain as part of its governance and financial infrastructure. Existing rules, historical records, balances, and token transfers had to remain valid and secure after the upgrade.

Neti had to answer several critical questions:

• How can EVM compatibility be added without relaunching the chain?
• How can existing historical blocks and transactions remain valid?
• How should Substrate accounts and EVM accounts interact safely?
• How can third-party EVM tools recognize a chain where EVM support was introduced after launch?
• How can the upgrade be implemented without breaking existing functionality?
• How can the system remain maintainable after a major protocol-level change?

This made the project a custom blockchain development challenge, not a standard Web3 integration.

Why EVM Compatibility Mattered

Liberland’s existing blockchain was built on Substrate, which gave the project flexibility and control over its own Layer 1 infrastructure. But as the broader blockchain ecosystem became increasingly connected around Ethereum-compatible tooling, EVM support became strategically important.

EVM compatibility would make it easier for Liberland to integrate with wallets, tools, smart contract infrastructure, ecosystem partners, and Web3 applications that already operate around Ethereum standards.

It was also important for cooperation with strategic ecosystem partners, including the Tron ecosystem, which supports EVM-compatible smart-contract execution. Supporting EVM execution would make these integrations smoother and allow Liberland to deploy planned solutions based on existing EVM smart contracts without requiring those protocols to modify their codebases.

For Liberland, this was not only a technical upgrade. It was a move from a more isolated custom blockchain environment toward a more interoperable infrastructure model.

What Made the Upgrade Difficult

Although Frontier can be used to add EVM compatibility to Substrate-based chains, Liberland’s situation was more complex because the blockchain was already live.

Frontier could not simply be plugged in as if the chain were starting from zero. Neti had to adapt the existing Substrate codebase and account for the fact that most EVM tools assume EVM support exists from genesis.

One of the core technical challenges was the difference between account formats:

• Substrate uses 32-byte addresses.
• EVM uses 20-byte addresses.

Bridging those models required careful design to avoid breaking user assumptions, token transfers, or existing chain behavior.

Another challenge was EVM genesis simulation. Since the chain did not originally start as an EVM-compatible chain, Neti had to make the upgraded environment recognizable to external EVM tooling in a way that preserved continuity.

The Solution: EVM Compatibility Without Chain Relaunch

Neti’s role was first to evaluate the available technical approaches, determine what was feasible for an already-live chain, and select the safest solution for Liberland’s specific requirements. The chosen approach had to support EVM compatibility while preserving historical state, existing protocol behavior, token flows, and long-term maintainability.

The solution involved adapting Frontier to the existing Substrate-based chain, modifying the codebase where necessary, and preserving the integrity of historical transactions, blocks, rules, and existing functionality.

The work included:

• integrating EVM compatibility into an already-live Substrate chain;
• adapting Frontier to fit the existing codebase;
• solving the Substrate/EVM account format mismatch;
• simulating EVM genesis behavior for third-party compatibility;
• preserving historical blocks and chain state;
• validating token transfer continuity and protocol behavior;
• making sure the original blockchain rules remained enforced after the upgrade.

This was the most extensive upgrade since Liberland’s blockchain launch, involving more than 20,000 lines of new code.

The work was delivered in approximately two months by a small team of two experienced Substrate/Polkadot engineers. The small team size mattered: this was not a task for broad staffing, but for senior engineers who could reason about protocol behavior, historical state, upgrade risk, and long-term maintainability.

Results: A More Interoperable Live Blockchain

The upgrade opened Liberland’s blockchain to broader EVM-compatible tooling and ecosystem integrations.

By adding EVM compatibility to its live Substrate-based chain, Liberland gained a more flexible foundation for future Web3 services, partner integrations, smart contract capabilities, and ecosystem expansion.

The project delivered several important outcomes:

Live-chain EVM compatibility
Liberland’s existing blockchain was upgraded without relaunching the chain from scratch.

Preserved chain continuity
Existing chain history and protocol continuity were preserved throughout the upgrade.

EVM tooling readiness
The upgraded chain became easier to connect with EVM-based tools, wallets, applications, and external integrations.

Resolved account model differences
Neti designed the bridge between Substrate’s 32-byte account model and EVM’s 20-byte address model.

Major protocol-level upgrade
The project introduced over 20,000 lines of new code and became the most extensive upgrade since the original chain launch.

Delivery by a senior specialist team
The upgrade was completed in approximately two months by two experienced Substrate/Polkadot engineers.

Business Value Delivered

For Liberland, the value of the upgrade was not only technical.

The project made the blockchain more compatible with the broader Web3 ecosystem, reduced future integration friction, and gave Liberland a stronger foundation for ecosystem partnerships, smart contract use cases, and digital governance services.

In practical terms, the upgrade made it possible for existing EVM protocols to deploy or integrate with Liberland’s chain without modifying their underlying codebases specifically for Liberland.

Instead of remaining limited by a more isolated infrastructure model, Liberland could move toward a chain architecture that is easier to extend, integrate, and evolve.

What Blockchain Teams Can Learn From This Project

This project shows that custom blockchain development is not only about launching a new chain.

Sometimes the harder challenge is upgrading a live chain that already has users, state, history, rules, and infrastructure dependencies.

For teams operating Substrate-based or custom Layer 1 blockchains, the lesson is clear: interoperability should be designed carefully, especially when the chain is already live. A post-launch EVM compatibility upgrade requires more than adding a module. It requires protocol engineering, account model design, historical state preservation, testing, and operational readiness.

A careless upgrade can create risk. A well-designed upgrade can open the chain to a broader ecosystem without sacrificing continuity.

Conclusion

Liberland’s EVM compatibility upgrade shows how a live Substrate-based blockchain can evolve without being relaunched.

The project required deep blockchain engineering, Rust and Substrate expertise, EVM architecture understanding, and the ability to navigate undocumented territory safely.

For Neti, this was a strong example of custom blockchain software development in practice: not a greenfield build, not a simple integration, but a major protocol-level upgrade performed on live infrastructure.

For digital governance projects, blockchain foundations, and custom Layer 1 teams, the takeaway is clear: if your blockchain needs to become more interoperable, the upgrade path should be designed before development starts.

Planning a custom blockchain upgrade?

If your team operates a Substrate-based blockchain, custom Layer 1, or protocol infrastructure that needs EVM compatibility, interoperability, or production-readiness improvements, Neti can help you assess the safest upgrade path.

We support teams with custom blockchain development, protocol engineering, Substrate development, Rust engineering, EVM compatibility, infrastructure audits, and live-chain upgrade planning.

Book a custom blockchain architecture consultation.

FAQ

What is EVM compatibility?

EVM compatibility means that a blockchain can support Ethereum Virtual Machine execution, making it easier to work with Ethereum-style smart contracts, wallets, tools, and applications.

When should a company hire a custom blockchain development company?

A company should consider hiring a custom blockchain development company when its blockchain roadmap requires work beyond standard smart contracts or off-the-shelf integrations. This includes Layer 1 development, Substrate or Rust engineering, EVM compatibility upgrades, runtime modifications, protocol-level integrations, infrastructure audits, and live-chain upgrade planning.

Why is upgrading a live blockchain to EVM compatibility difficult?

It is difficult because the blockchain already has existing state, historical blocks, accounts, token logic, and protocol rules. The upgrade must add new execution capabilities without breaking continuity.

What did Neti do for Liberland?

Neti helped Liberland upgrade its live Substrate-based blockchain to support EVM compatibility by adapting Frontier, addressing Substrate/EVM account format differences, simulating EVM genesis behavior, and preserving existing chain data and functionality.

What is Frontier in Substrate?

Frontier is a Substrate framework component that enables EVM compatibility. In post-launch upgrades, it often requires additional adaptation because many tools assume EVM support exists from the chain’s genesis.

What is custom blockchain development?

Custom blockchain development involves designing, building, modifying, or upgrading blockchain infrastructure for use cases that cannot be handled by standard off-the-shelf solutions. This may include Layer 1 development, consensus modifications, runtime upgrades, EVM compatibility, protocol integrations, infrastructure tooling, and production-readiness work.

When should a blockchain team consider EVM compatibility?

A blockchain team should consider EVM compatibility when it wants easier integration with EVM wallets, tools, smart contracts, applications, and ecosystem partners, especially if interoperability is important for adoption or future product development.