-
Notifications
You must be signed in to change notification settings - Fork 29
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
[BIP-726] Adopt SEAL Whitehat Safe Harbor Agreement #1433
Conversation
FILENAME:
|
FILENAME:
|
… reports) + reformat JSON
@DicksonWu654 is there somewhere official to verify the contract at address |
Thank you for reviewing! Yep it's in the official github legal document here: https://github.com/security-alliance/safe-harbor/blob/main/documents/agreement.pdf It's on page 9 or 1.1 c Would you like it to be more explicit / more easily accessible? |
Not sure why the tenderly simulation failed. I simulated it after I inputted the fields in the Gnosis Safe UI and it seemed to work: https://dashboard.tenderly.co/public/safe/safe-apps/simulator/dba0a8d3-cba7-4057-a583-be2320bb569a |
The auto tenderly code doesn't always work on complex payloads. Also the address decoding isn't working with all the special characters in the calldata. We'll do a little work and see if we can improve things, but will of course check tenderly and addresses manually if we can't get our reporting to work. |
We add all known addresses to our address book. The PR to add involves a verification process. At best there is somewhere I can link, and copypasta the same address from on an official safe harbor site. I wasn't able to copy-paste the address easily in this PDF. If it's not a hassle a slightly easier to handle reference would be nice :) |
Ah let me try to do the payload without the \n :) |
Got it I got it! |
… reports) + reformat JSON
Alright just pushed something to remove all the extra spaces & remove the / from the "N/A". Not sure if that'll fix it though 😓 |
Alrighty does this work? https://github.com/security-alliance/safe-harbor/blob/main/documents/deployment.txt |
… reports) + reformat JSON
Hey fellas, our in-house counselor had some bits to add on the agreement - I left a comment of the forum proposal. Also, please add that you will abide to the DAO standards and accountability guidelines. |
Hi! I replied on the forum! |
Just updated the payload to reflect the new state. The changes are: Identity Verification from Simulated on tenderly here: https://dashboard.tenderly.co/public/safe/safe-apps/simulator/d21db244-0ead-4a1b-8803-fe5b5e768cc8/logs Here are the parameters too balancerAdoption.json |
… reports) + reformat JSON
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.
current payload translates to:
- 10% bounty
- in $bal
- on chains ethereum, arbitrum, avalanche, base, fraxtal, gnosis, mode, optimism, polygon and zkevm
- requires kyc
- balancer vault as the account in question
balancer vault and dao msig addresses check out for all chains
@DicksonWu654 can you please move the payload to week 44? |
Yes will do! |
… reports) + reformat JSON
@gosuto-inzasheru |
@DicksonWu654 i just numbered this bip. if you can reflect that change in this pr we can approve it and include it in this week's gov round! sorry for all the admin, appreciate the efforts! prop: https://forum.balancer.fi/t/bip-726-adopt-the-seal-safe-harbor-agreement/6087 |
Thank you so much @gosuto-inzasheru! I just changed the BIP numbers! |
… reports) + reformat JSON
@DicksonWu654 you payload executes this from our lm (liquidity mining) multisig, not the dao multisig. is this correct? (does it matter?) |
Oh no I didn't mean to do that 😓. Is it possible to change it, or would we need to re-do a DAO vote. But I think it's fine if it's from the lm multisig - as long as the DAO approved of it |
0x8f72fcf695523A6FC7DD97EafDd7A083c386b7b6
. CallingadoptSafeHarbor
with the these parameters balancerAdoptionParameters.json