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