-
Notifications
You must be signed in to change notification settings - Fork 1
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
Post-hackathon changes #1
Conversation
|
||
For Ethereum applications that can be exploited in a single transaction, this adds another form of proactive defense that can supplement traditional (off-chain) bug bounties and monitoring. | ||
For Ethereum protocols that can be exploited in a single transaction (which are often the case), this offers a novel form of proactive defense that can complement traditional (off-chain) bug bounties, threat monitoring, and in-protocol circuit breakers. |
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.
For Ethereum protocols that can be exploited in a single transaction (which are often the case), this offers a novel form of proactive defense that can complement traditional (off-chain) bug bounties, threat monitoring, and in-protocol circuit breakers. | |
For Ethereum protocols that can be exploited in a single transaction (which are often the case), this offers a novel form of defense that can complement traditional (off-chain) bug bounties, threat monitoring, and in-protocol circuit breakers. |
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.
y u hate proactive
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.
LG. Most of my suggestions are nits, feel free to dismiss
Co-authored-by: Justin Schuldt <[email protected]>
Co-authored-by: Justin Schuldt <[email protected]>
Co-authored-by: Justin Schuldt <[email protected]>
Co-authored-by: Justin Schuldt <[email protected]>
Co-authored-by: Justin Schuldt <[email protected]>
Co-authored-by: Justin Schuldt <[email protected]>
Co-authored-by: Justin Schuldt <[email protected]>
Co-authored-by: Justin Schuldt <[email protected]>
Now that the comp has wrapped up, here's a couple things I've been wanting to add/change.
verifyBountyCanPay()
, which is a sandbox around payment alone. Because the system is non-custodial, the only way to check if a bounty can pay is to actually simulate it in a sandbox.