ACE separates identity from authorization, so classical and post-quantum keys become replaceable authorization tools instead of permanent account identities. Current devnet measurements show Ed25519 and ML-DSA-44 running in the same throughput band under the same chain configuration. PQC becomes a deployable operating mode, not a slow emergency migration.
MEV is execution quality leaking from applications into ordering. ACE targets the part a chain can control: insertion, reordering, and omission by the block-production path. Traders, market makers, wallets, aggregators, and protocols get a fairer execution venue.
ACE is not just another EVM-compatible chain. Native, EVM, SVM, BVM, TVM, and Move-style execution can settle into one L1 state model. Users should not manage five fragmented balance sheets just because developers need different execution models.
Cross-chain DeFi often fragments the same economic asset into wrappers, pools, and bridge-specific risk buckets. OMNILIQUID maps supported external assets into canonical oAssets while risk compartments keep assets, mappings, markets, routes, relayers, and oracles explicit. Liquidity can be shared without making every failure domain global.
Most chains make validators, RPC nodes, indexers, and light clients repeat authorization work forever. ZK-ACE moves toward compact proofs that attest to valid authorization for batches or blocks. This matters even more when post-quantum credentials are larger than classical signatures.
The public repository is packaged so external operators can build and run a non-validator full node. It syncs blocks, serves local JSON-RPC, participates in P2P relay, and does not vote or produce blocks. Useful participation starts before validator admission opens.
Digital assets have a private-key inheritance trilemma: inheritance, self-custody, and long-term asset continuity are hard to preserve together. ACE treats this as a protocol problem, not only a custody product problem. Assets should remain self-custodied while still having a verifiable release path.
When public keys become permanent identities, algorithm migration, key rotation, post-quantum upgrades, and recovery all become ecosystem-wide coordination problems.
VM-specific ecosystems force assets, balances, integrations, and user journeys into separate ledgers. Bridges then become a substitute for shared settlement.
Shared liquidity is valuable, but unbounded shared risk is not. Assets, external mappings, markets, routes, relayers, and oracle feeds need explicit failure domains.
The current codebase and whitepaper now point to a wider protocol surface than a single PQC chain:
ACE treats Ed25519 and ML-DSA-44 as interchangeable authorization modes above a stable identity layer. For long-lived assets, RWA, treasury systems, and high-value DeFi accounts, PQC can become an operational choice before quantum migration turns into an emergency.
MEV-ACE focuses on insertion, reordering, and omission inside the block-production path. The business value is execution quality: better fills for users, lower risk margins for market makers, and a more credible venue for wallets and aggregators.
Native, EVM, SVM, BVM, TVM, and Move-style execution can settle into one L1 state model. Developers keep familiar programming models; users avoid fragmented balances; liquidity, identity, and finality remain unified instead of being bridged after the fact.
Supported external assets can map into canonical oAssets on ACE. Shared liquidity improves depth and routing, while deterministic risk compartments make assets, external mappings, markets, routes, relayers, and oracle feeds explicit failure domains.
Instead of asking every verifier to repeat authorization checks forever, ACE moves toward compact proofs for batches or blocks. This is especially important when post-quantum credentials are larger and independent verification must remain affordable.
Useful nodes should not need validator-grade equipment. ACE's public full-node path lets external operators sync, relay, serve local RPC, and help observe the network from ordinary infrastructure before validator admission opens.
Digital assets face a trilemma between private-key inheritance, self-custody, and long-term asset continuity. ACE treats this as a protocol problem so assets can remain self-custodied while still having a verifiable release path.
ACE Chain is open to protocol engineers, cryptographers, security reviewers, infrastructure operators, documentation contributors, and testnet builders. Discussions and issues are public so technical knowledge compounds instead of disappearing into private chats.
| Area | ACE Chain | Typical L1 Pattern | User / Industry Impact |
|---|---|---|---|
| PQC authorization | Classical and ML-DSA-44 authorization modes | Retrofit after identity is already key-bound | Long-lived assets can prepare before migration becomes urgent |
| Execution model | N-VM shared state tree | Single VM or bridge-connected VM islands | Less fragmented liquidity, identity, and onboarding |
| Ordering | MEV-ACE fair-ordering hook | Private routing or app-level mitigations | Lower block-local manipulation surface |
| Liquidity | oAssets with risk compartments | Many wrappers, pools, and bridge risk buckets | Deeper shared liquidity without unbounded shared risk |
| Verification cost | ZK-ACE O(n) toward O(1) direction | Repeated per-transaction authorization checks | Cheaper independent verification and lighter clients |
| Public nodes | Full-node operation and discovery | Often underdocumented or validator-centric | More operators can contribute before validator admission |
| Custody lifecycle | Self-custody inheritance primitive direction | Custodial services or fragile dead-man switches | Inheritance, self-custody, and asset continuity can be addressed together |
The cryptographic foundation — identity-authorization separation, deterministic multi-algorithm key derivation, and zero-knowledge identity commitments.
O(1) verification through recursive STARK proofs, batch credential verification, and post-quantum-secure proof composition.
The execution runtime that unifies identity verification, ZK proof generation, and transaction processing into a single sub-second pipeline.
Multi-virtual-machine execution with a unified state tree — EVM, SVM, BVM, and TVM sharing identity and token balances natively.
Lightweight mempool propagation without on-path proofs — solving the bandwidth challenge of 2420-byte ML-DSA-44 signatures at scale.
Serverless wallet recovery using on-chain encrypted artifacts and human-memorable identifiers, with enumeration-resistant addressing.
Crypto-asset inheritance without key exposure — dormant authorization paths that activate only upon verifiable trigger conditions.
Agent economic sovereignty — policy-bounded spending, privacy-preserving micro-settlement, and A2A interoperability on-chain.
The public repository includes operator docs and focused technical notes that connect protocol design to user and industry benefits.
Use Discussions for architecture questions, testnet feedback, contribution proposals, and deeper protocol review.
Updated June 16, 2026. Covers post-quantum authorization, shared-state execution, fair ordering, liquidity compartments, and the current public testnet direction.
A natively post-quantum secure Layer 1 blockchain without performance trade-offs. Includes ACE-GF foundations, N-VM shared state, ZK-ACE, MEV-ACE, OMNILIQUID direction, and public infrastructure strategy.
Download PDF