EVM Subnet
Also called Ethereum Virtual Machine subnet
Origin:
composes, an architectural pattern borrowed from Avalanche, paired with an existing open-source EVM implementation. Solidus status:spec, designed, not deployed. There is nothing public to connect to yet.
An EVM subnet is a separate, opt-in blockchain that runs Ethereum-compatible smart contracts (Solidity, standard tooling) while sharing validators or state with a base-layer chain, rather than every base-layer validator having to execute every Solidity contract call. The idea is to keep a base layer's own execution model unencumbered while still giving developers who want ordinary Ethereum tooling a place to deploy, without spinning up a fully separate, disconnected blockchain.
Where the pieces come from
The general "subnet" pattern, validators opting in to a specific chain that isn't the base layer, rather than every validator running every chain, is Avalanche's architecture, renamed Avalanche L1s in a December 2024 upgrade (Etna, ACP-77) that gave subnets sovereign validator sets. Solidus's plan borrows this pattern, not Avalanche's code or branding.
The EVM execution engine itself, in the plan, is REVM (bluealloy/revm), a Rust implementation of the Ethereum Virtual Machine that's already the execution engine behind Reth, Foundry, Optimism, and Scroll, and has been through independent security review by outside researchers. The plan is to use REVM as-is, the same way most serious EVM-compatible chains do, rather than write a new EVM implementation from scratch.
The honest state of it
Solidus's own architecture documentation says it plainly: subnets, including this one, "do not exist on the live network today." This is a specification, of a REVM-based subnet bridged to the base L1 through a handful of read-only "identity precompiles" (a Solidity contract could call one to check, say, whether a given DID is currently active, by verifying a Merkle inclusion proof against the L1's last finalized state root, without re-running any L1 logic), plus early, unpublished engineering exploration. There is no public endpoint, no live testnet deployment, and no independent validator set running any of it yet.
Check it yourself
There's nothing to check by running anything, no live EVM subnet endpoint exists. What you can read is the design itself, documented in Solidus's public architecture documentation under its Identity Subnets roadmap section.
Related terms: JSON-RPC · libp2p · HotStuff · Finality · Merkle Tree
Where it comes from
Someone else specified this. Solidus assembles it.
The "subnet" pattern, an opt-in chain with its own validator committee that shares security or state context with a base layer, is borrowed from Avalanche's subnet architecture (renamed Avalanche L1s after the Etna upgrade and ACP-77, December 2024); Solidus takes the pattern, not the branding or the code. The EVM execution itself is planned to run on REVM (bluealloy/revm), the widely-used, audited Rust EVM implementation that also powers Reth, Foundry, Optimism, and Scroll: the plan is to reuse it, not write a new EVM from scratch.
How to check this
Written down. No implementation yet.
None publicly runnable yet. There is no live EVM subnet endpoint to query. The design is documented in Solidus's architecture documentation (the Roadmap, Identity Subnets section).