docs: how to update commitments when zkvm version change

Author: MarcosNicolau

examples/validating-public-input/Makefile

@@ -10,7 +10,6 @@ generate_sp1_fibonacci_proof:
 		cargo run --release && \
 		echo "Fibonacci proof, pub input and image ID generated in sp1 folder"
 
-
 submit_fibonacci_sp1_proof_devnet:
 	@cd aligned-integration && \
 	RUST_LOG=info cargo run --release -- --proving-system "SP1" --network "devnet" --rpc-url "http://localhost:8545"
@@ -44,3 +43,7 @@ deploy_fibonacci_validator:
 
 deploy_fibonacci_validator_devnet:
 	@. ./contracts/.env.devnet && . ./contracts/deploy.sh
+
+get_program_id_commitment:
+	@echo "Proof commitment for $(DATA_FILE_NAME) is:"
+	@jq '.program_id_commitment' ./aligned-integration/batch_inclusion_data/$(DATA_FILE_NAME)

examples/validating-public-input/README.md

@@ -82,6 +82,7 @@ Contract Address: 0x90d6A3E189C70E1Cce16c29151077cB9Badb2448
 Block: 2963688
 Paid: 0.000727925005095475 ETH (727925 gas * 1.000000007 gwei)
 ```
+
 > [NOTE]  
 > The `Contract Address` listed above corresponds to a current valid deployment of the examples contract on the `holesky` testnet.
 
@@ -100,3 +101,11 @@ status                  1 (success)
 transactionHash         <TX_HASH>
 ...
 ```
+
+5. If the process fails, it could be due to mismatched commitments when verifying. Ensure that the contract commitments are updated to match the values returned in the batcher's response under `aligned_verification_data`. For example, if the SP1 or Risc0 version has changed, you'll need to update the `programIdCommitment`. To regenerate the commitment, run:
+
+```shell
+make get_program_id_commitment DATA_FILE_NAME=<DATA_FILE_NAME>
+```
+
+And update the field `fibonacciProgramIdCommitmentSp1` or `fibonacciProgramIdCommitmentRisc0` in the contract with the new value.