RPIP-82: Enable pDAO Spending of ETH and ERC-20 Source

Introduce pDAO proposals for one-time and recurring ETH and ERC-20 payments.
⚠️ This RPIP is not recommended for general use or implementation as it is likely to change.
RPIP82
Authorknoshua
StatusDraft
TypeProtocol
Created2026-05-21
DiscussionLink
Category (*only required for protocol )Core

Contents

RPIP-82: Enable pDAO Spending of ETH and ERC-20 Source

Introduce pDAO proposals for one-time and recurring ETH and ERC-20 payments.

Abstract

RPIP-72 introduced a pdao_share, which allows the protocol to direct part of ETH staking rewards of megapools to the pDAO. This proposal enables the pDAO to spend this ETH by voting on one-time spends and recurring payments in ETH. It also generalizes these mechanisms to payments for any ERC-20.

Specification

This RPIP extends the functionality of two proposal types of the on-chain pDAO voting system introduced in RPIP-33.

One-Time Spend

This proposal type deals with one-time spends of ETH or ERC-20 tokens from the protocol’s treasury.

A proposal of this type comprises the following:

  1. Invoice ID: An arbitrary string associated with the payment used for bookkeeping purposes.
  2. Recipient Address: The Ethereum address of the beneficiary of this payment.
  3. Type: Whether this is an ETH spend or a token spend.
  4. Token Address (if type is ERC-20): In case of a token spend, the token address.
  5. Amount: An amount of ETH or token to send to the beneficiary.

Upon execution of a successful proposal of this type, the protocol SHALL send the provided amount of ETH or token from its treasury to the recipient.

Recurring Payments

This proposal type deals with the creation and modification of recurring ETH or ERC-20 token payment contracts.

A payment contract comprises:

  1. Contract Name: An arbitrary string associated with this contract used for bookkeeping purposes.
  2. Recipient Address: The Ethereum address of the beneficiary of this payment.
  3. Period Length: The length (in seconds) of periods of this contract.
  4. Start Date: A unix timestamp specifying when payments should begin.
  5. Number of Periods: The number of periods the protocol will pay the beneficiary.
  6. Type: Whether the recurring payment is in ETH or an ERC-20 token.
  7. Token Address (if type is ERC-20): In case of a token spend, the token address.
  8. Amount Per Period: The amount of ETH or token to send per period.

A proposal of this type can perform one of these actions:

  1. Create: Creates a new recurring payment contract.
  2. Update: Modifies an existing recurring payment contract.

The protocol SHALL allow the recipient address of a recurring payment to execute a claim at any time. The protocol SHALL calculate all unpaid payments up to that point and transfer the required amount from its treasury to the recipient.

Rationale

This proposal aims to enable spending of ETH with as little complexity as possible, by mirroring the existing implementation of spending RPL from the treasury. Generalizing this mechanism to ERC-20 tokens does not appear to introduce additional complexity and is included to provide future-proofing.

Copyright and related rights waived via CC0.

Citation

knoshua, "RPIP-82: Enable pDAO Spending of ETH and ERC-20 [DRAFT]," Rocket Pool Improvement Proposals, no. 82, May 2026. [Online serial]. Available: https://rpips.rocketpool.net/RPIPs/RPIP-82.