Update validator behavior

stellar · Aug 10, 2023 · 4417657 · 4417657
1 parent 04a2d1a
commit 4417657
Showing 1 changed file with 4 additions and 1 deletion.
diff --git a/core/cap-0046-09.md b/core/cap-0046-09.md
@@ -102,7 +102,10 @@ used to write the proposed upgrade. The specs of the entry written is as follows
 Once the proposed upgrade is setup, you'll need to share the
 `ConfigUpgradeSetKey` with the other validators so they can vote for it. Note
 that the validators will verify that the hash in `ConfigUpgradeSetKey` matches
-the hash of the upgrade stored in the `ContractDataEntry`.
+the hash of the upgrade stored in the `ContractDataEntry`, and will only vote
+for upgrades that follow this rule. Validators should however still apply any
+valid hash the network accepts (even if that specific validator didn't vote for
+the upgrade).
 
 #### `ConfigUpgradeSet` validation