Skip to main content

GRT $0.01972 up 1.06% Market cap $217.6M

Increase L2 rewards to 95%

GGP-0033 · Council vote #39 on The Graph

Overview

Updated

Approved

Voting ended
Dec 29, 2023
Opened Nov 29, 2023
Submitted
Nov 29, 2023
Nov 29, 11:45 UTC
Members voted
6
One vote each, on Snapshot

GGP-0033 was also put to a vote as #38.

Put to the Council by 0xff1588…ba47

Votes

  • Yes 6 votes
  • No 0 votes

How BitBasic reads the result

  • Approved when more Council members chose Yes than No.
  • Each member has one vote, and Snapshot keeps a member's last.

Description

(This proposal has already been executed on November 27th, so this GGP is a means to officially ratify the action)

GIP: 0052

Title: Timeline and requirements to increase rewards in L2

Authors: Pablo Carranza Vélez, Ariel Barmat, Tomás Migone

Since GIP-0031 and GIP-0040 have been deployed, The Graph now runs the protocol on both Ethereum Mainnet (L1) and Arbitrum One (L2). Participants are free to perform actions on either chain, and as GIP-0037 and GIP-0043 have been rolled out, indexing rewards in L2 are enabled and set at 50% of total issuance.

Transfer tools have also been deployed as per GIP-0046 to allow participants to transfer their stake, delegation, subgraphs and curation to L2.

GIP-0052 depends on GIP-0046 and proposes increasing the indexing rewards in L2, in several steps until fully transitioning protocol issuance to Arbitrum One. This GGP proposes approving the third step, increasing issuance in Arbitrum One to 95% of total issuance (and reducing it in L1 accordingly), on November 27th, 2023, if no blocking issues are reported before then.

Following a successful vote of this proposal, the following transactions will be executed:

  • The increase of L2 rewards to 95% of total issuance (114.6935 GRT per block) will be on Arbitrum One on November 27th.
  • Reducing L1 issuance to 5% (i.e. 6.0365 GRT per block) will be executed at the same time.
  • The L1 bridge mint allowance will be adjusted accordingly afterwards.

How the Council voted

In the order they voted. Snapshot knows members by address only, so BitBasic doesn't name them.

Member Vote When
0x38fa68…4da8 Yes Dec 4, 19:19 UTC
0x17118d…2c21 Yes Dec 5, 11:36 UTC
0xc23efd…54e6 Yes Dec 5, 15:36 UTC
0x7eabe4…7fee Yes Dec 5, 15:39 UTC
0xd201c9…22aa Yes Dec 5, 15:43 UTC
0xb02ce5…80b0 Yes Dec 5, 15:43 UTC