Slide 26
Slide 26 text
Dynamically loaded WebAssembly
embedded inside the Aurora Engine (“JIT”)
● Just-in-time compiled WebAssembly
bytecode automatically deployed to,
stored in, and maintained by the Aurora
Engine for “hot” contracts
● Trusted-yet-sandboxed bytecode
deployed reproducibly by trusted parties
● Zero EVM compatibility issues, just a
significant speedup
● Requires a NEP process, nearcore
implementation, and protocol upgrade
for dynamic bytecode support (6
months minimum)
Standalone static NEAR contract
deployment (“AOT”)
● Ahead-of-time compiled WebAssembly
bytecode manually deployed on-chain
on NEAR, and authenticated with the
Aurora Engine registry by the deployer
● Untrusted, arbitrary bytecode deployed
directly by third parties
● Some challenges and trade-os for
interacting with other EVM contracts
(cross-shard calls)
● Doesn’t require anything in particular
from NEAR and nearcore
EVM to WebAssembly: Execution models