R3E Network reveals Neo Solidity compiler project for Neo N3

Jimmy Liao, a core developer and founding father of R3E Community, has revealed he’s engaged on a Neo Solidity Compiler, a device that compiles Solidity 0.8.x sensible contracts to Neo N3 bytecode. The mission permits builders to jot down contracts in Solidity and deploy them to the Neo N3 blockchain.

What’s Neo Solidity?

The Neo Solidity Compiler interprets Solidity sensible contracts into Neo N3-compatible bytecode and manifest recordsdata. The compiler is written primarily in Rust and contains testing infrastructure for each fundamental and superior Solidity options. The mission documentation states its aim is to allow Ethereum builders to construct on Neo N3 utilizing their present Solidity data, moderately than studying Neo’s native sensible contract languages.

The compiler accepts Solidity 0.8.x supply code and outputs Neo N3’s .nef bytecode recordsdata and .manifest.json recordsdata. It detects ERC token normal patterns (ERC-20, ERC-721) in Solidity contracts and maps them to Neo’s equal requirements (NEP-17, NEP-11).

Builders can select from 4 optimization ranges (0-3) when compiling contracts. The device operates via a command-line interface and contains scaffolding for integration with Hardhat and Foundry, two improvement frameworks generally utilized in Ethereum improvement.

Neo Solidity differs from the Neo X mission in that Neo X is an EVM sidechain the place builders deploy Solidity contracts on to that community with out modification. In distinction, Neo Solidity compiles Solidity supply code into Neo N3-compatible bytecode, permitting contracts to be deployed natively on the Neo N3 principal community moderately than a separate EVM-compatible chain.

Technical structure

The compilation course of converts Solidity supply code to Yul intermediate illustration, then performs semantic evaluation for kind checking and validation. A multi-level optimizer applies Neo-specific transformations earlier than the code generator produces NeoVM bytecode and manifest recordsdata.

The compiler features a runtime library that gives reminiscence administration, storage operations, ABI encoding, and cryptographic features designed to match EVM habits inside Neo’s execution atmosphere.

An in depth technical design specification is accessible within the mission repository for builders within the compiler’s inner structure and implementation choices.

Instance contracts

The repository contains a number of instance contracts that display the compiler’s performance. WGAS is a wrapped GAS token implementation that follows the WETH9 sample and complies with NEP-17. FlashLoan implements an Aave V2-style flash mortgage pool with 0.09% charges. SimpleAMM is a constant-product automated market maker based mostly on Uniswap V2’s design.

Further examples embrace TokenVesting, which offers linear vesting schedules just like OpenZeppelin’s VestingWallet; SimpleLending, which adapts Compound’s single-asset lending pool mechanics; and SimpleDAO, which implements MolochDAO-style governance with staking and proposals.

Based on the mission documentation, all instance contracts have been deployed and examined with state-changing operations on Neo Categorical, Neo’s native improvement atmosphere.

Growth standing

The mission documentation signifies the core compiler is roughly 85% full and described as production-ready. The runtime library is listed at 75% completion, developer tooling at 70% with a completely purposeful CLI, and documentation at 80% completion.

The mission documentation lists a number of present limitations. Operate overloading is partially supported: features might be overloaded with totally different argument counts utilizing signature-mangled names, however overloading with the identical argument depend is rejected. EVM name choices like {fuel: ...} and {worth: 0} are accepted however ignored; non-zero worth transfers require utilizing NEP-17 native calls. Gasoline accounting is approximated via per-syscall fuel hints, with opcode-level charges roughly 80% correct.

The documentation recommends TestNet validation earlier than MainNet deployment.

The technical design specification might be discovered at right here, whereas the pull mission repo might be discovered beneath:
https://github.com/r3e-network/neo-solidity/tree/principal