-
Notifications
You must be signed in to change notification settings - Fork 574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ERC: Wallet Call Simulation API #892
base: master
Are you sure you want to change the base?
Conversation
File
|
The commit 3ddc7fb (as a parent of 1f189dd) contains errors. |
### `traceMalicious` Capability | ||
|
||
Capability to trace malicious calls. Needs discussion. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe also a separate detectMaliciousAddresses
capability? It seems functionally separate from traceMalicious
; it'd be used to flag i.e. token transfers to known scam addresses?
### `traceMalicious` Capability | ||
|
||
Capability to trace malicious calls. Needs discussion. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can also see adding a 'stateOverride' capability
address: `0x${string}`; | ||
data: `0x${string}`; | ||
topics: `0x${string}`[]; | ||
}[]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Call traces are also useful for surfacing internal contract calls and internal eth transfers, if the simulator supports outputting them. We could mark that as an optional field in the response (or make this a capability?)
No description provided.