ethereum / ethereum/keymanager-APIs

GET `/eth/v1/validator/{pubkey}/graffiti` clarification

Open
#77 4 comments 1 reaction 0 assignees View on GitHub
Dominant language
HTML
Stars
43
Forks
25
Avg merge
21h 47m
Merged PRs (30d)
4

Description

**A couple of scenarios require clarification:**

1. The graffiti is described as `"Arbitrary data to set in the graffiti field of BeaconBlockBody"`. Should we be returning the exact graffiti that will be used when creating a block including the node info appended to the graffiti? Or should we just be returning the graffiti that was set / system wide default depending on the situation?

For context, Teku appends consensus layer (CL) and execution layer (EL) clients' information to the validator graffiti. More details are linked here: [validators-graffiti-client-append-format](https://docs.teku.consensys.io/development/reference/cli#validators-graffiti-client-append-format)

This clarification relates to whether the graffiti returned from the GET should include this appended format, or just the set graffiti, without the appended information.

2. In the response, the `pubkey` is described as an optional field. In what case would this be empty, as we will always have the value from the path parameter?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.