Any reason why rewards endpoints are not in the Beacon section?

[nalepae]

• All endpoints in the Beacon section begin with /eth/v{1,2}/beacon/...
• All endpoints in the Builder section begin with /eth/v1/builder/...
• All endpoints in the Config section begin with /eth/v1/config/...
• ...

I understand there is some exceptions for ValidatorRequiredApi and Experimental sections.

However, since all rewards endpoint are also prefixed by /eth/v1/beacon/, is there any reason why they are not stored in the Beacon section as well?

(@kevinbogner)

[rolfyone]

Purely because it's a clean grouping... they could be in the beacon section, but is there value?

[nalepae]

The value would be to have all the endpoints in any <Xxx> section beginning with /eth/v{i}/xxx/..., which is currently the case for all sections, except for the Rewards section.

(And the ValidatorRequiredApi and Experimental sections as well, but all endpoints in these two sections are duplicate of other sections)

[mcdee]

The /beacon endpoints are meant to be those that contain beacon chain structures. Rewards are derived information, so should sit outside of this namespace.

(Also beacon endpoints are mandatory for support whereas I don't believe that rewards are, but that's secondary.)