-
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
Arbitrum DAO KYC #132
Arbitrum DAO KYC #132
Conversation
(cherry picked from commit 0f30e5e)
Zendragon: Are already known addresses that will not KYC, but exist in bal_addresses and have history of operating with balancer multisigs. Will ask the 3 new kyc signers to load up a transaction that sends 0 arb to the grant safe. This transaction will be executed as on-chain record of signer liveliness. |
Proof of liveliness from KYC signers. All 3 signed this TX: |
Safe and signers are verified: |
@Zen-Maxi as the other known Maxi signer on this safe, can you just review this PR and the process and make sure it all looks kosher. Then go ahead and approve/merge this PR. |
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.
Straight forward enough to me. Looks good.
Setup Multisig for handling $ARB from the DAO grant.
Requires a majority of signers to KYC with Arbitrum (but not otherwise dox).
KYCed signers will be named as kycsigner1 - kycsigner3.
I certify that these are 3 different people all of whom are connected to Balancer. The Arbitrum KYC process will do the same.