corydickson

Hey, I'm corydickson and I have contributed to the MACI Small v2 MPC Phase2 Trusted Setup ceremony.
The following are my contribution signatures:

Circuit # 1 (process_messages_small)
Contributor # 3
Contribution Hash: fc3f2487 25671d71 fd932826 19d84eab
		4d39ca0a 5a906432 81f198cc 2c51525b
		1e0807cb 88595580 5efeddf5 1694978a
		8ef3484d 8f967b21 d1fdb6a8 2b16d30c

corydickson

I contributed to the ZKOPRU Trusted Setup Multi-Party Ceremony.
The following are my contribution signatures:
Circuit: zk_transaction_1_2 
          Contributor # 140
          Hash: 03bac0a7 3f6b5fd0 21d888b7 43723163
 0af3e665 d0c0c9d7 9ed3fc32 0058b4ce
 dcf36c91 beb8dafa 133326a5 a2e7c3a1
 75de23d3 82992265 77b9dbcd 8238974e

corydickson

Keybase proof

I hereby claim:

• I am corydickson on github.
• I am gh1dra (https://keybase.io/gh1dra) on keybase.
• I have a public key ASBqDI2NWBuzSVes0RNX4LnD8nZirjB3MPESnZVBjqYuxwo

To claim this, I am signing this object:

corydickson

The DAO Registry

This scheme contract interacts with the DAORegisty inside of the arc-hive repo. It leverages the generic call contract scheme to interact with a registry contract that the DAOAvatar owns.

Specification

The user interface for this scheme will take the address of the registry contract, the address of the DAO to be added/removed, and the associated name to be registered. On the client-side of Alchemy it should generate the callData field to be set inside of the proposal storage by encoding the parameters supplied by the user.

For example, if the user is trying to register another DAO avatar, they will supply its address, and the name as type string, as well as the registry address they are trying to access. The scheme will call the registry contracts' register function.

corydickson

### Keybase proof

I hereby claim:

  * I am gh1dra on github.
  * I am gh1dra (https://keybase.io/gh1dra) on keybase.
  * I have a public key ASBqDI2NWBuzSVes0RNX4LnD8nZirjB3MPESnZVBjqYuxwo

To claim this, I am signing this object:

corydickson