You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On any upgrade of the system (and perhaps, this would be better for the security council documentation) it would be great if there was an output of system contracts that could be imported to the docs.
Essentially, a list:
bootloader: 0x.....
contract deployer: 0x...
🤔 Rationale
For mocking contracts, setting up tests, and interacting with system contracts, developers are going to need to know where to point their mocks/forks/etc. Right now, it's quite difficult to get this information. Having this repo (or security council repo) output this information will allow it to be ingested by the docs, so people can have a direct place to see where these are.
Additional Security Considerations
In the event a malicious contract attempts to rug users by using a phishing address, where their address looks like a system contract address, but is not. It would be great to quickly check if the system contract address was actually the address. Right now, it's difficult to get this information.
The text was updated successfully, but these errors were encountered:
🌟 Feature Request
On any upgrade of the system (and perhaps, this would be better for the security council documentation) it would be great if there was an output of system contracts that could be imported to the docs.
Essentially, a list:
bootloader
: 0x.....contract deployer
: 0x...🤔 Rationale
For mocking contracts, setting up tests, and interacting with system contracts, developers are going to need to know where to point their mocks/forks/etc. Right now, it's quite difficult to get this information. Having this repo (or security council repo) output this information will allow it to be ingested by the docs, so people can have a direct place to see where these are.
Additional Security Considerations
In the event a malicious contract attempts to rug users by using a phishing address, where their address looks like a system contract address, but is not. It would be great to quickly check if the system contract address was actually the address. Right now, it's difficult to get this information.
The text was updated successfully, but these errors were encountered: