more details for contract types

near · Feb 21, 2025 · bfad2e3 · bfad2e3
1 parent 610dbc4
commit bfad2e3
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/neps/nep-0591.md b/neps/nep-0591.md
@@ -35,6 +35,8 @@ Additionally global contracts cover the underlying use case for [NEP-491](https:
 Global contract can be deployed in 2 ways: either by its hash or by owner account id.
 Contracts deployed by hash are effectively immutable and cannot be updated.
 When deployed by account id the owner can redeploy the contract updating it for all its users.
+Users can use contracts deployed by hash if they prefer having control over contract updates. In order to update the contract user would have to explicitly switch to a different version of the contract deployed under a different hash.
+Contracts deployed by account id should be used when user trusts contract developers to update the contract for them. For example if user accounts are created specifically for some application to be onchain.
 
 We introduce new receipt action for deploying global contracts: