Skip to main content

GRT $0.01972 1.06% Market cap $217.6M

Council Vote, GIP-0076 (Issuance Allocator Contract)

GGP-0059 · Council vote #67 on The Graph

Overview

Updated

Approved

Voting ended
Apr 30, 2026
Opened Apr 15, 2026
Submitted
Apr 15, 2026
Apr 15, 16:04 UTC
Members voted
6
One vote each, on Snapshot

Put to the Council by 0x552091…58a9

Votes

  • For 6 votes
  • Against 0 votes
  • Abstain 0 votes

How BitBasic reads the result

  • Approved when more Council members chose For than Against; Abstain doesn't count either way.
  • Each member has one vote, and Snapshot keeps a member's last.

Description

Summary

This proposal requests Council approval to implement GIP-0076: Issuance Allocator contract to split issuance across distribution targets.

The Issuance Allocator introduces a governance-configurable contract that splits total GRT issuance across multiple protocol targets, laying the foundation for the economic upgrades outlined in GIP-0070.

Context

Today, all protocol issuance flows to the Rewards Manager. As The Graph expands beyond indexing rewards into indexing payments and other distribution mechanisms, a single monolithic issuance path limits flexibility.

GIP-0076 delivers an iterative step: new distribution mechanisms can operate alongside existing systems under fixed, governance-set proportions, with future iterations enabling self-balancing.

Key Components

Component Description
Total Issuance Preserves existing per-block issuance rate
Target Types Self-minting (e.g. Rewards Manager) and allocator-minting
Access Control GOVERNOR_ROLE for rate and allocation changes, PAUSE_ROLE for emergency
Operational Safety Pause and accumulation mechanisms, target removal, gas-limit recovery
Backward Compatibility When allocator address is unset, Rewards Manager behaves as today

Full specification: GIP-0076

Reviews

  • TAB: TAB members approved.
  • Indexers: Multiple Indexer Office Hour Sessions have been used to socialize the proposal and gather feedback

See the vote on Snapshot Its discussion on the forum

How the Council voted

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

Member Vote When
0xb02ce5…80b0 For Apr 16, 14:11 UTC
0x7eabe4…7fee For Apr 23, 13:17 UTC
0xccd92a…a8a5 For Apr 23, 14:45 UTC
0xdc524f…1397 For Apr 24, 18:48 UTC
0xf53f07…4011 For Apr 27, 17:19 UTC
0x325256…ad8e For Apr 27, 22:30 UTC