aelf elf

aelf is an AI-enhanced Layer 1 blockchain network founded in 2017 and headquartered in Singapore. Its implementation is written primarily in C#, using the .NET ecosystem as a foundation for scalable, cloud-oriented blockchain development and AI integration. The native asset is ELF.

aelf uses a multi-chain design centered on a MainChain connected to multiple dAppChains. Rather than putting every contract on one general-purpose chain, its stated model is "one chain to one type of contract," allowing workloads to be separated and processed in parallel. dAppChains can be tailored to application requirements while the MainChain coordinates the broader ecosystem and cross-chain operations.

The project positions this architecture for digital assets, DeFi, marketplaces, games, and other decentralized applications. Developer tooling includes SDKs, a CLI, smart-contract templates, and C#-based contract development; the official repository is open source under the MIT license.

Whitepaper 2.0 extends aelf's direction with AI-assisted smart-contract optimization/auditing, congestion prediction, intelligent load balancing, AI oracles, NLP-assisted contract creation, and chatbot support. The roadmap also describes a modular blockchain and a ZK-rollup/validium design intended to improve throughput, EVM compatibility, costs, and privacy.

Traditional single-chain architectures put unrelated contracts and transactions into the same execution environment. This can create congestion, performance bottlenecks, rising fees, and difficulty tailoring a chain to different application workloads. aelf's MainChain/dAppChain approach is designed to isolate workloads and distribute processing.

The project also identifies data complexity and the limitations of conventional blockchain developer/user experiences as barriers to broader adoption. C#/.NET tooling, chain customization, and AI-assisted development are intended to make building, auditing, and interacting with dApps more accessible.

The architecture is not risk-free: aelf's own Whitepaper 2.0 says the current MainChain-dAppChain model has TPS bottlenecks, and its proposed modular/ZK-rollup work is intended to address those limitations. Users must also distinguish Mainnet ELF from ERC-20 and BEP-20 representations when bridging or depositing.

At the base layer, aelf runs a MainChain and multiple dAppChains. The MainChain acts as the backbone and indexes dAppChain block information for cross-chain transfers and verification. Separating contracts and workloads across dAppChains enables parallel processing and application-specific customization; consensus functionality is described as a pluggable/replaceable module.

ELF pays transaction fees and dAppChain block-index fees. Candidate block producers deposit ELF to participate in node elections; voters use ELF for voting, with one ELF equating to one vote according to the official token documentation. Mainnet ELF is distinct from bridged Ethereum ERC-20 and BNB Smart Chain BEP-20 forms.

The planned/introduced modular path uses a Polygon CDK-based ZK-rollup in validium mode. Its components include a zkEVM/ZKProver executor-verifier, external data availability with a Data Availability Committee, an on-chain consensus contract, sequencer, aggregator, and bridge. Sequencers order transactions and propose batches; aggregators generate and submit validity proofs; the Layer 1 verifier accepts valid proofs.

On that rollup, users bridge ELF from L1 for gas. Transactions move through pre-validated (L2), committed (batch posted to L1), and verified (proof accepted on L1) states. Sequencers and aggregators both pay/earn ELF gas fees in the described design.