Skip to content

Aragon Community multisig – Beef beef 0xbeefbeef03c7e5a1c29e0aa675f8e16aee0a5fad

Required signatures: 5/7

Signers

Aragon Foundation Multisig

Address
Read more

Joe Urgo

CEO District0x & Dapp daily author.

Address
Proof
Keybase

Kenny Rowe

COO of RChain Cooperative. Formerly COO at MakerDAO.

Address
Proof
Keybase

Jake Brukhman

Cofounder of CoinFund.

Address
Proof
Keybase

Mihai Alisie

Founder of AKASHA, cofounder of Ethereum and Bitcoin Magazine

Address
Proof
Keybase

Griff Green

Founder of Giveth and cofounder of the White Hat Group

Address
Proof
Keybase

Placeholder

Placeholder is a venture capital partnership founded by Joel Monegro and Chris Burniske that invests in decentralized information networks

Address
Proof
Keybase

Proof notes

The proofs are a hex-encoded PGP signature that contains an English string representing his agreement with being part of the multisig, as well as his ownership of the address he will use for it.

To verify them (this example uses a macOS system):

  • Obtain the data attached to the Ethereum transaction from the proof. Convert it to ASCII.
  • If you have Keybase installed, just run keybase pgp verify -m "{proof_message_here}"
  • If you do not have Keybase installed, you can go to the multisig participant's Keybase profile, obtain his PGP key, and verify using GPG/PGP

Responsibilities

  • The Community multisig will serve ANT holders and the broader crypto community to ensure Aragon's stated mission is carried out.
  • The Community multisig will be responsible for deploying the Aragon Network code (provided by Aragon One or dev teams funded by the Aragon Foundation) once it is considered secure to do it and it matches the original expectations of it.
    • The Community multisig has the power to decide the ANT control power, and the power will eventually be set to the Aragon Network.
    • If needed, the Community multisig can also perform a token migration.
  • Solving hypothetic deadlock problems in the Aragon Foundation multisig to ensure resources won't get locked and the project will continue its course.

Rationale

  • Deploying the Aragon Network is a huge responsibility, and that's why we consider it a community effort. Aragon One or dev teams funded by the Aragon Foundation will provide the bytecode for such network, but without support from the community it won't be deployed.

  • The community multisig becomes a 5/6 multisig if the Foundation cannot sign. One of the key holders in the Foundation multisig + the Community multisig can solve any deadlock by replacing the other key in the Foundation multisig.