feat(rpc): remove v04 config option, v03 and v04 specs, update Readme

README.md

@@ -240,10 +240,9 @@ This can be used to interact with a custom Starknet gateway, or to use a gateway
 
 You can interact with Starknet using the JSON-RPC API. Pathfinder supports the official Starknet RPC API and in addition supplements this with its own pathfinder specific extensions such as `pathfinder_getProof`.
 
-Currently, pathfinder supports `v0.4`, `v0.5`, and `v0.6` versions of the Starknet JSON-RPC specification.
+Currently, pathfinder supports `v0.5`, and `v0.6` versions of the Starknet JSON-RPC specification.
 The `path` of the URL used to access the JSON-RPC server determines which version of the API is served:
 
-- the `v0.4.0` API is exposed on the `/rpc/v0.4` and `/rpc/v0_4` path
 - the `v0.5.1` API is exposed on the `/`, `/rpc/v0.5` and `/rpc/v0_5` path
 - the `v0.6.0` API is exposed on the `/rpc/v0_6` path
 - the pathfinder extension API is exposed on `/rpc/pathfinder/v0.1`

crates/pathfinder/src/bin/pathfinder/config.rs

@@ -229,7 +229,6 @@ impl Color {
 
 #[derive(clap::ValueEnum, Debug, Clone, Copy, PartialEq)]
 pub enum RpcVersion {
-    V04,
     V05,
     V06,
 }

crates/pathfinder/src/bin/pathfinder/main.rs

@@ -185,7 +185,6 @@ Hint: This is usually caused by exceeding the file descriptor limit of your syst
     };
 
     let default_version = match config.rpc_root_version {
-        config::RpcVersion::V04 => pathfinder_rpc::DefaultVersion::V04,
         config::RpcVersion::V05 => pathfinder_rpc::DefaultVersion::V05,
         config::RpcVersion::V06 => pathfinder_rpc::DefaultVersion::V06,
     };