EVM++ diagram

​
Core components

​
Native scheduling

We introduce a new predeploy contract, dubbed Scheduler that enables developers to register a callback frequency at which their smart contract entry point is invoked. Block producers maintain a mapping of pending invocations and may include these transactions at the top of each block, subject to transaction validity and sufficient fees. For heterogeneous or compute-intensive scheduled transactions, Resonance ensures timely allocation and inclusion in a state-preserving manner.

Scheduled Transactions

Recurring, conditional execution of transactions without external keepers.

​
Account Abstraction

Account Abstraction attempts to blur the line between EOAs and smart contract accounts, by enabling users to replace their EOA accounts with programmatic functionality. We bring native account abstraction support via inclusion of EIP-7702: Set EOA Account Code.

Account Abstraction

Native smart contract accounts via EIP-7702: SetCodeTx.

​
EIP Extensions

Historically, Ethereum and other EVM-based chains have lagged in their support for integrating novel Ethereum Improvement Proposals (EIPs), often due to development overhead or naive gas pricing support for precompiles. EIP Extensions are our attempt to prioritize continual support and inclusion of in-demand EIPs that improve user and developer experience.

EIP-665

Adds support for Ed25519 signature verification.

EIP-5027

Removes the limit on smart contract code size with new, dynamic gas metering.

EIP-5920

Adds a new PAY opcode to send ether without transferring execution context.

EIP-7212

Adds support for secp256r1 signature verification.

​
Expressive compute

At the heart of EVM++ is our addition of heterogeneous compute precompiles that allow developers to build net-new applications. For those familiar with EVM-based smart contract development, using these compute paradigms maintains the same developer experience as interacting with a precompile contract. Behind these standard interfaces are our optimized sidecars which generate execution outputs and necessary proofs, consumed by a Ritual execution client. Because of our standardized interface, generic sidecar architecture, and novel Resonance fee mechanism, supporting new heterogeneous compute precompiles or other execution environments (SVM, MoveVM, etc.) is naturally supported.

Execution Sidecars

Optimized underlying architecture for any type of heterogeneous compute, including AI inference, ZK proof verification, TEE code execution, and beyond.

​
Looking forward

As we continue expanding the set of supported precompiles in EVM++, we’ll also enable long-running precompiles. Via native asynchronous execution, users will be able to leverage Ritual in a lazy way for more computationally demanding work, while continuing to inherit the properties of the chain.