Skip to content

feat: configurable block proposal graffiti - #483

Open
erl-100 wants to merge 1 commit into
ObolNetwork:mainfrom
erl-100:custom-graffitti
Open

feat: configurable block proposal graffiti#483
erl-100 wants to merge 1 commit into
ObolNetwork:mainfrom
erl-100:custom-graffitti

Conversation

@erl-100

@erl-100 erl-100 commented Aug 15, 2026

Copy link
Copy Markdown

Description

Adds support for custom block proposal graffiti, so node operators can set their own graffiti per validator. This exposes charon's two existing flags as environment variables.

The default stays charon/<version>-<commit>, and charon's OB<CL> suffix is still appended. Operators who don't touch .env see no change.

Verification

Against obolnetwork/charon:v1.10.3, Compose v5.4.0:

  • docker compose config: '""' reaches the container as two characters; bare "" is stripped to empty.
  • Byte limits confirmed: a 29-character graffiti is rejected as "greater than maximum size" with the client append on, accepted with it off.
  • Against a 1-validator cluster, one,two fails in NewGraffitiBuilder with "graffiti length must match the number of validators"

Expose charon's --graffiti and --graffiti-disable-client-append as
CHARON_GRAFFITI and CHARON_GRAFFITI_DISABLE_CLIENT_APPEND, so operators can set
a custom graffiti, a per-validator list,
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant