Overview
UpdatedApproved
- Voting ended
- Apr 30, 2026
- Opened Apr 15, 2026
- Submitted
- Apr 15, 2026
- Apr 15, 16:16 UTC
- Members voted
- 6
- One vote each, on Snapshot
Put to the Council by 0x552091…58a9
Votes
- For 100% 6 votes
- Against 0% 0 votes
- Abstain 0% 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-0087: On-Chain Indexing Agreements.
GIP-0087 introduces a contract-managed framework for indexing payment agreements, replacing GIP-0081's off-chain signed vouchers with on-chain offer, acceptance, and settlement, backed by protocol-issuance-funded escrow.
Context
GIP-0081 established indexing payments but left two trust gaps: payers lack slashing recourse, and indexers must trust gateways to issue valid vouchers. Curation-driven indexing rewards also create supply and demand inefficiencies.
On-chain agreements address these gaps through contract-based authorization and automated escrow management via the Recurring Agreement Manager, which receives protocol issuance through the Issuance Allocator.
Key Components
| Component | Description |
|---|---|
| Agreement Lifecycle | Offer, Accept, Collect, Cancel, Remove |
| Authorization | Callback verification via agreement manager contract, no extra signing |
| Escrow Funding | Recurring Agreement Manager funded by issuance allocation |
| Operational Modes | Full, OnDemand, JustInTime, with graceful degradation |
| Escrow Flexibility | New adjustThaw on PaymentsEscrow, no timer reset |
| Subgraph Service | New IDataServiceAgreements interface for accept, collect, cancel |
Full specification: GIP-0087
Dependencies
-
GIP-0076 (Issuance Allocator)
-
GIP-0088 (deployment and configuration)
Reviews
-
TAB: The TAB reviewed and supported the proposal
-
Indexers: Multiple Indexer Office Hour Sessions have been used to socialize the proposal and gather feedback
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:12 UTC |
| 0x7eabe4…7fee | For | Apr 23, 13:19 UTC |
| 0xccd92a…a8a5 | For | Apr 23, 14:41 UTC |
| 0xdc524f…1397 | For | Apr 24, 18:50 UTC |
| 0xf53f07…4011 | For | Apr 27, 17:20 UTC |
| 0x325256…ad8e | For | Apr 27, 22:31 UTC |
