Skip to content

Commit

Permalink
SIMD-XXXX: Custom Fee Collector Account
Browse files Browse the repository at this point in the history
  • Loading branch information
jstarry committed Jan 24, 2025
1 parent f757148 commit b48f3d1
Showing 1 changed file with 64 additions and 0 deletions.
64 changes: 64 additions & 0 deletions proposals/XXXX-custom-fee-collector.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
---
simd: 'XXXX'
title: Custom Fee Collector Account
authors: Justin Starry (Anza)
category: Standard
type: Core
status: Draft
created: 2025-01-24
feature: (fill in with feature tracking issues once accepted)
---

## Summary

Allow validators to specify a custom fee collector account where all earned
block fees will be deposited.

## Motivation

Validator fee collector accounts must currently be the same as their identity
hot wallet account. This means that program derived addresses are unable to be
used for fee collection adding friction to validators distributing their revenue
in custom ways. By allowing validators to specify a separate custom fee
collector address, they can use onchain programs to customize how their block
revenue is distributed.

## Alternatives Considered

NA

## New Terminology

NA

## Prerequisite Proposals

SIMD-0180 adjusts the leader schedule algorithm to make it possible to designate
a specific vote account for a given leader slot.

SIMD-0185 adds a new fee collector address field to the vote account state.

## Detailed Design

After adoption of SIMD-0180 and SIMD-0185, a given block's fee collector address
can be looked up via the designated vote account for the leader schedule slot
that the block was produced in.

In order to eliminate the overhead of tracking the latest fee collector address
of each vote account, the fee collector address should be fetched from the state
of the vote account at the beginning of the previous epoch. This is the same
vote account state used to build the leader schedule for the current epoch.

Note that the fee-collector constraints defined in SIMD-0085 still hold. The
designated fee collector must be a system program owned account that is
rent-exempt after receiving collected block fee rewards. If either of these
constraints is violated, the fees collected for that block will be burned.

## Impact

Validator identity and fee collector accounts no longer need to be the same
account. This opens up the ability to use PDA accounts for fee collection.

## Security Considerations

NA

0 comments on commit b48f3d1

Please sign in to comment.