Arbitrum delegates and delegation : Overview

When participating in the Arbitrum DAO, token holders have the option to either vote directly on proposals or to give their voting power to a delegate. This concept doc explores the role of delegates and delegation within the context of the Arbitrum DAO.

What is a delegate?

A delegate is a member of the Arbitrum DAO community who has been elected to represent other token holders and vote on their behalf. Delegates are elected by token holders who choose to grant their voting power to them. Delegates are required to follow the protocols defined by the Constitution of the Arbitrum DAO, and must act in the best interest of the token holders whom they represent.

Why delegate?

Delegation allows token holders to participate in the governance of the Arbitrum DAO without having to actively keep track of every proposal and vote. By granting their voting power to a delegate, token holders can passively participate by entrusting a representative to vote on proposals in a way that aligns with their own beliefs and values.

Token holders who delegate their voting power are able to revoke this delegation and reclaim voting power back to themselves at any time. They may want to do this if, for example, there's an important proposal that they themselves want to vote on directly. Source

In this dashboard we are going to track the consolidation of voting power in Arbitrum DAO. First, we used the Tally API and obtained the top 100 representatives based on voting power, and converted the json file into a table with Python. Because the name of the delegates did not exist, we used this API and then joined with tables. We first got the votes by EVENT_NAME and CONTRACT_ADDRESS .We got the delegated addresses by EVENT_NAME from votes. We got the delegated balance by EVENT_NAME from votes. Then we joined The delegated addresses and delegated balance based on TX_HASH.

The tables used in this analysis are:

arbitrum.core.fact_event_logs , arbitrum.core.dim_labels, arbitrum.core.dim_contracts

The conditions:

• Vote: EVENT_NAME IN ('DelegateChanged', 'DelegateVotesChanged', 'VoteCast') and CONTRACT_ADDRESS IN('0x912ce59144191c1204e64559fe8253a0e49e6548')
• Delegated address: EVENT_NAME = 'DelegateChanged'
• Delegated balance: EVENT_NAME = 'DelegateVotesChanged'

key words

Priority: In the tables, there is a field called priority, which is the ranking of representatives in Tally.

API : Json Top 100 Representative