We are proud to announce the initial outcomes of the third month of the Delegate Incentive Program. We can now share results with the Arbitrum ecosystem.
May Participants
For May’s iteration of the program, 48 participants enrolled, out of which 44 met the necessary requirements to qualify.
You can see the full list here.
Parameters Breakdown
Snapshot Voting
During the month, there were a total of 40 Snapshot Votes, which were considered for the assignment of scores by SV. It is important to note that only those proposals that ended in May were counted. These are the proposals that were taken into account:
- 15 LTIPP Votations.
- 18 STIP Votations.
- GovHack at ETH CC (Brussels)
- Grant Request - Curve Finance
- Proposal for Approval of DeDaub as the ADPC Security Advisor
- Pilot Phase: M&A for Arbitrum DAO
- Arbitrum Multi-sig Support Service (MSS)
- Streamlining the LTIPP Bounties
- Kwenta x Perennial: Arbitrum Onboarding Incentives
Tally Voting
For this month, there were a total of 3 Tally Votes considered for TV scoring. It is important to note that only those proposals that ended in May were counted. These are the proposals that were considered:
- Grant Request - Curve Finance
- GovHack at ETH CC (Brussels)
- Double-Down on STIP Successes (STIP-Bridge)
Communication Rationale
As stated in our forum post, LTIPP Communication Rationales won’t be taken into consideration for this parameter.
For the CR, the published rationals of all the votes of the month were considered, taking into account Snapshot and Tally, that is to say, that to obtain the maximum qualification in this aspect a delegate had to express his rational of all the votes of the month, in other words, 28 (25 Snapshot + 3 Tally).
Commenting in proposals
25 proposals were considered. These proposals were the ones that went through Snapshot excluding the LTIPP proposals.
May Results
You can see the dashboard with the results implemented by Karma here.
Of all the participating delegates, 29 were eligible to receive compensation.
| Delegate | Address | Tally Profile | PARB |
|---|---|---|---|
| mcfly | 0x821f2b40d965b81202b181Aba1c7a380C49Ed675 | mcfly profile | 4.740,00 |
| cp0x | 0x6f9BB7e454f5B3eb2310343f0E99269dC2BB8A1d | cp0x Profile | 4.590,00 |
| 404DAO | 0xe93d59cc0bcecfd4ac204827ef67c5266079e2b5 | 404DAO Profile | 4.340,00 |
| Bob-Rossi | 0xb29A655f3D67B2B6724Fb22B2C2303cB660c946B | Bob Rossi Profile | 4.330,00 |
| BlockworksResearch | 0xA160b58a0108BC139Aafc1dC67846fcc2aD6D4Cd | BlockworksResearch Profile | 4.290,00 |
| MaxLomu | 0xd333Bc5c9670C9cEb18f9A2CF02C6E86807a8227 | MaxLomu Profile | 4.270,00 |
| PGov | 0x3fb19771947072629c8eee7995a2ef23b72d4c8a | PGov Profile | 4.230,00 |
| UADP | 0x8326D18edfC50B4335113C33b25116ec268FF3fE | UADP Profile | 4.210,00 |
| BristolBlockchain | 0x43D3938Ebd74106e2d177f9A304C1E9f914f2b52 | BristolBlockchain Profile | 4.083,75 |
| DAOplomats | 0xd4879f876eE383067F80ACAdBE283B93141908e9 | DAOplomats | 4.031,96 |
| 0x_ultra | 0x04330a444F9D051713b13c934d478a552165C205 | 0x_Ultra Profile | 4.030,00 |
| StableLab | 0x9c489E4efba90A67299C1097a8628e233C33BB7B | StableLab Profile | 4.015,36 |
| Jojo | 0x1de39f894c2DC773C8A11862F58165EcC7611C91 | Jojo Profile | 3.840,00 |
| L2BEAT | 0x41626BA92c0C2a1aD38fC83920300434082B1870 | Profile L2beat | 3.835,30 |
| Gauntlet | 0xFd2892eFf2615C9F29AF83Fb528fAf3fE41c1426 | Gauntlet Profile | 3.810,00 |
| HiringDevs.eth | 0x22aA1F4173b826451763EbfCE22cf54A0603163c | hiringdevs.eth Profile | 3.786,25 |
| jameskbh | 0x714D8b5874b3a6a69f289f4e857F4C9670074296 | Jameskbh Profile | 3.780,71 |
| Tane | 0xB79294D00848a3A4C00c22D9367F19B4280689D7 | Tane Profile | 3.765,36 |
| PrincetonBlockchain | 0x18BF1a97744539a348304E9d266aAc7d446a1582 | PrincetonBlockchain Profile | 3.743,04 |
| 0xCasio | 0x47E98aA12dB2017295d33e94002521820442F827 | 0xCasio profile | 3.730,00 |
| Karpatkey | 0x583E3EDc26E1B8620341bce90547197bfE2c1ddD | Karpatkey Profile | 3.660,00 |
| TreasureDAO | 0x0eB5B03c0303f2F47cD81d7BE4275AF8Ed347576 | TreasureDAO Profile | 3.644,05 |
| Frisson | 0xb5B069370Ef24BC67F114e185D185063CE3479f8 | Frisson Profile | 3.381,25 |
| ITUblockchain | 0xBEC643BD5b7F5e9190617CA4187ef0455950C51C | ITUblockchain profile | 3.200,12 |
| Bobbay | 0x5a35923ed6950eff4412ef6d27cea8b1d405a844 | Bobbay Profile | 3.144,05 |
| Savvy DeFi | 0x4f54Cab19B61138e3c622a0bD671C687481eC030 | Savvy DeFi Profile | 3.128,45 |
| olimpio | 0xF4B0556B9B6F53E00A1FDD2b0478Ce841991D8fA | olimpo Profile | 3.115,18 |
| GFXLabs | 0xa6e8772af29b29B9202a073f8E36f447689BEef6 | GFX Labs Profile | 3.039,05 |
| Kuiqian.eth | 0xf3FE8c6c75bE4afB2F8200Fc77339abE4D7CFF33 | Kuiqian Profile | 3.000,00 |
| Total | 110.808,51 |
Bonus Points
There were no qualified delegates to receive Bonus Points this month.
Costs
We track all cost data for greater transparency in our Payment Distribution Thread.
Incentives to delegates (May)
According this the results presented before the total cost destined to the delegates this month will it be 110.808,51 ARB
Why haven’t they finished paying for the months of March and April?
That’s because there are some delegates that still haven’t completed their KYC process and they still remain unpaid.
When the kyc will be completed, the remaining payments will be sent to the delegates.
New Members of the Program
As we said in previous posts, any delegate can apply to the program anytime.
We have two new participants that will be part of it from the next month:
[CALL TO ACTION!] Dispute Period
As stated in the proposal, delegates have 2 days to express their disagreement with the results presented by the Incentive System Administrator.
To raise a dispute, delegates should do so by posting a message in the forum using the following template:
Title: Dispute
User name
Reason for dispute (please detail)
Conclusions
This month has been the busiest so far in terms of data collection for the Delegate Incentive Program. We are delighted to see how delegate activity has evolved, demonstrating increased engagement and participation in governance processes.
Given the high volume of Communication Rationales (CR) collected this month, we acknowledge the possibility of errors. We invite all delegates to double-check our table (link tabla publica) their recorded CRs to ensure accuracy.
Here you can see all the information related to CP and CR.
If you want to give any feedback, don’t hesitate to do it in this thread.
