Skip to main content

GRT $0.02018 2.79% Market cap $222.6M

Epoch Block Oracle and Data Edge for Arbitrum One

GGP-0020 · Council vote #21 on The Graph

Overview

Updated

Approved

Voting ended
Feb 6, 2023
Opened Jan 23, 2023
Submitted
Jan 23, 2023
Jan 23, 14:58 UTC
Members voted
6
One vote each, on Snapshot

Put to the Council by 0xd201c9…22aa

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

GGP: 0020 Scope: Smart Contracts Created: 2023-01-19

GIPs

GIP: 0038 Title: Epoch Block Oracle Authors: Adam Fuller (adam@edgeandnode.com), Ariel Barmat (ariel@edgeandnode.com), Zachary Burns Created: 2022-02-11 Updated: 2022-11-01 Category: Protocol Interfaces

Link to GIP-0038 on IPFS.

Graph Governance Proposal 0020

GGP 0016 introduced an "Epoch Block Oracle" to specify the currentEpochBlock on other chains, unlocking indexing rewards and network growth, as per GIP-0038.

As the protocol now also runs on Arbitrum One (since GGP 0017), a separate instance of the Epoch Block Oracle will specify the current epoch blocks to be used on the Arbitrum One protocol.

This also requires a DataEdge contract on Arbitrum One.

Arbitrum nodes don’t support trace_filter calls, so the DataEdge contract must emit events with the data that is posted to it for the subgraph to work.

The Council specifies that the protocol will use the following Data Edge contract instance on Arbitrum One:

0x633bb9790d7c4c59991cebd377c0ed6501a35ebe

See the vote on Snapshot

How the Council voted

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

Member Vote When
0x17118d…2c21 Yes Jan 23, 15:09 UTC
0xb02ce5…80b0 Yes Jan 24, 16:06 UTC
0x38fa68…4da8 Yes Jan 24, 22:11 UTC
0x37bc95…b391 Yes Jan 25, 03:56 UTC
0x7c1b13…297d Yes Jan 27, 08:23 UTC
0xc23efd…54e6 Yes Jan 27, 15:43 UTC