diff --git a/.gitignore b/.gitignore
index d8ea95a..4054205 100644
--- a/.gitignore
+++ b/.gitignore
@@ -23,6 +23,7 @@ latest_proof.json
 elf
 program.bin
 stdin.bin
+vk.bin
 
 **.csv
 
diff --git a/README.md b/README.md
index 72ee6e1..54ac05b 100644
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@ For the supported chains (Ethereum Mainnet and Sepolia, OP Stack Mainnet, and Li
 cargo run -r --bin host -- --block-number <block-number> --rpc-url <RPC> --chain-id <chain-id>
 
 # eg.
-cargo run -r --bin host -- --block-number 18884864 --rpc-url <RPC> --chain-id 1
+cargo run -r --bin host -- --block-number 25134887 --rpc-url <RPC> --chain-id 1
 ```
 
 The host CLI executes the block while fetching additional data necessary for offline execution. The same execution and verification logic is then run inside the zkVM. No actual proof is generated from this command, but it will print out a detailed execution report and statistics on the # of cycles to a CSV file (can be specified by the `--report-path` argument).
@@ -60,7 +60,7 @@ If you want to actually generate proofs, you can run the CLI using the `--prove`
 cargo run -r --bin host -- --block-number <block-number> --rpc-url <RPC> --chain-id <chain-id> --prove
 
 # eg.
-cargo run -r --bin host -- --block-number 18884864 --rpc-url <RPC> --chain-id 1 --prove
+cargo run -r --bin host -- --block-number 25134887 --rpc-url <RPC> --chain-id 1 --prove
 ```
 
 This will generate proofs locally on your machine. Given how large these programs are, it might take a while for the proof to generate.
diff --git a/bin/host/input/1/18884864.bin b/bin/host/input/1/18884864.bin
deleted file mode 100644
index a7a3f42..0000000
Binary files a/bin/host/input/1/18884864.bin and /dev/null differ
diff --git a/bin/host/input/1/25134887.bin b/bin/host/input/1/25134887.bin
new file mode 100644
index 0000000..f8ac586
Binary files /dev/null and b/bin/host/input/1/25134887.bin differ