diff --git a/README.md b/README.md
index 1ead5ae9..212df6c0 100644
--- a/README.md
+++ b/README.md
@@ -18,7 +18,7 @@ Furthermore, Arbiter provides containment and management for simulations. For a
 The Arbiter workspace has three crates:
 - `arbiter`: The binary crate that exposes a command line interface for initializing simulations via a templated repository and generating contract bindings needed for the simulation.
 - `arbiter-core`: The lib crate that contains the core logic for the Arbiter framework including the `RevmMiddleware` discussed before, the `Environment` which envelopes simulations, and the `Manager` who controls a collection of environments.
-- `arbiter-derive`: The lib crate that contains custom derive macros for more succinct simulation building.
+- `arbiter-engine`: The lib crate that provides abstractions for building simulations and more.
 
 The purpose of Arbiter is to provide a toolset to construct arbitrary agents (defined in Rust, by smart contracts, or even other foreign function interfaces) and have these agents interact with an Ethereum-like environment of your design. 
 All contract bytecode is run directly using a blazing-fast EVM instance `revm` (which is used in live RPC nodes such as [`reth`](https://github.com/paradigmxyz/reth)) so that your contracts are tested in the exact same type of environment that they are deployed in.