[Request for Comments (RFC)][RGP - 29] - Migrate Drips oracle to Lit protocol

👩‍⚖️ Governance 👀 Active Proposals
1
Author(s): @igor
Type: executeable
Created: 2026-03-02
Status: active
Request for Comments: [Request for Comments (RFC)][RGP - 29] - Migrate Drips oracle to Lit protocol
Formal Review: —
Submission: —
Snapshot Vote: —

Purpose

The purpose of this proposal is to future-proof and improve Drips protocol’s oracle.

Overview & Background

RepoDriver smart contracts on Ethereum, Filecoin, Metis and Optimism will be updated to the latest version using an oracle running on Lit network.

This is a drop-in replacement that doesn’t disrupt or limit the protocol and all the user funds, configurations and account ownerships are unaffected.

Implementation

  1. Upgrade RepoDriver on Ethereum under 0x770023d55D09A9C110694827F1a6B32D5c2b373E. This upgrades the implementation to address TBD deployed from commit 73c0857c18fcd506552b61357087c7d31fc386db and configures it to use oracle implementation from the same commit.

  2. Send a message to LZBridgedGovernor on Metis under 0x07791819560264627e9c4B1308e546667E83B564. The message will trigger execution of the following steps by the governor:

    1. Upgrade RepoDriver on Metis under 0xe75f56B26857cAe06b455Bfc9481593Ae0FB4257. This upgrades the implementation to address TBD deployed from commit 73c0857c18fcd506552b61357087c7d31fc386db and configures it to use oracle implementation from the same commit.

  3. Send a message to LZBridgedGovernor on Optimism under 0x07791819560264627e9c4B1308e546667E83B564. The message will trigger execution of the following steps by the governor:

    1. Upgrade RepoDriver on Optimism under 0xe75f56B26857cAe06b455Bfc9481593Ae0FB4257. This upgrades the implementation to address TBD deployed from commit 73c0857c18fcd506552b61357087c7d31fc386db and configures it to use oracle implementation from the same commit.

  4. Send a message to AxelarBridgedGovernor on Filecoin under 0xE9B15C572EB7Ba2E2856cc5eFaAb8fe1d0e34116. The message will trigger execution of the following steps by the governor:

    1. Upgrade RepoDriver on Filecoin under 0xe75f56B26857cAe06b455Bfc9481593Ae0FB4257. This upgrades the implementation to address TBD deployed from commit 73c0857c18fcd506552b61357087c7d31fc386db and configures it to use oracle implementation from the same commit.

The exact addresses where the new implementations are deployed will be determined after the audit of those changes is complete. The current git commit hashes are tentative and will be updated too when the upgrade script gets the final new implementation addresses set.

Reasoning & Analysis

There are multiple reasons to migrate to Lit:

  1. The current implementation will stop working at the end of March 2026 because it relies on Gelato Web3 Functions service which will be retired.

  2. The new oracle running on Lit adds support for many user identity types on top of the currently supported:

    • HuggingFace models, datasets and users
    • GitHub users and orgs
    • GitLab users and groups
    • Codeberg repositories and users
    • Radicle repositories

  3. Relying on Lit makes Drips more robust. Unlike Gelato, Lit network is a permissionless, decentralized network of worker nodes owned by multiple parties.

  4. Metis deployment of RepoDriver will become usable again after Gelato removed support for Web3 Functions on that chain.

Reporting & Success Criteria

This proposal should result in a successful contracts upgrade across 4 chains. The upgrade should fulfill all goals listed in the “Overview & Background” section, most critically the lack of disturbance for the users of the protocol.

Fund Management

Some of the DAO’s WETH will be used to cover the cross-chain messages fees.

Timeline & Budget

The budget is capped at 0.03 ETH. Those funds will be used to cover the fees for sending cross-chain messages. The fees set to be paid in the proposal are highly overestimated and most of them will be refunded to the DAO shortly after the messages are delivered and the actual costs are determined. The proposal will have all of its effects fulfilled across all chains in about 20 minutes from its execution.

Proposal Code

The proposal is generated with code found in commit 73c0857c18fcd506552b61357087c7d31fc386db, specifically the Propose contract in file UpgradeProposal.sol, which ensures auditability, reproducibility and testability.

This proposal description does not include the usual list of calls because it would contain multiple large binary blobs with no clear meaning.