Comparing version 0.3.0 to 0.4.0
{ | ||
"name": "erc7656", | ||
"version": "0.3.0", | ||
"version": "0.4.0", | ||
"description": "ERC7656 Reference Implementation", | ||
@@ -5,0 +5,0 @@ "publishConfig": { |
@@ -89,6 +89,4 @@ # ERC-7656 | ||
For more elaborate example, take a look at the [Cruna Protocol](https://github.com/crunaprotocol/cruna-protocol). | ||
Notice that anyone can deploy a service owned by a specific token, usign whatever salt they prefer. To avoid troubles and security issues, any initial setup must be designed so that, despite who is the deployer, the result is what is expected to be. For example, if a service must get some information from the token, it should be the service the one that queries the token, not the other way around. In other words, passing any parameter to the service during the deploying opens to the possibility of a malicious deployer to pass a different set of data causing the service to behave unexpectedly. | ||
Notice that the plugin can be deployed by anyone, not only by the owner. Deploying it from the token itself, however, allows for more controls; for example, if executing an initializing function allowed only by the token owner. | ||
## License | ||
@@ -95,0 +93,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
21558
11
96