or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing
xxxxxxxxxx
Ethereum Protocol Fellowship - The Third Cohort (Update 10)
Long term topic I'm working on
Rewrite the validator client code to be compatible with the Beacon API instead of prysmaticlabs' internal API.
Ticket here.
Actions done
GetFeeRecipientByPubKey
I wrote this (merged) PR:
What does this PR do? Why is it needed?
This PR introduces two main changes:
FeeRecipientconfig
In
ProposerOption
, a new wrapperFeeRecipientConfig
aroundFeeRecipient
is created:This change enables the fact that
FeeRecipient
could be undefined whileBuilderConfig
is defined.This fixes https://github.com/prysmaticlabs/prysm/issues/11948.
This PR ensures
PrepareBeaconProposer
andSubmitValidatorRegistrations
are called only for pubkeys with a (custom or default) fee recipient.==> We can call POST setGasLimit on a pubkey without fee recipient without automatically defined the corresponding fee recipient to burn address.
GetFeeRecipientByPubKey
Before this PR,
GetFeeRecipientByPubKey
gRPC call is called in:SetGasLimit
,SetFeeRecipientByPubkey
, andListFeeRecipientByPubkey
There is no (direct or indirect) equivalent of
GetFeeRecipientByPubKey
in Beacon API.The idea of this PR is to reduce usage of
GetFeeRecipientByPubKey
gRPC call as low as possible.After this PR,
GetFeeRecipientByPubKey
gRPC is only used inListFeeRecipientByPubkey
.A next PR will handle this last case in order to be fully Beacon API compatible.
Also, I wrote this (not yet merged) PR:
What does this PR do? Why is it needed?
This PR deals with the (lack of) implementation for the
GetFeeRecipientByPubKey
method in beacon API.With gRPC implementation, if, for a given
{pubkey}
:{pubkey}
specific fee recipient is set in validator client, ANDGetFeeRecipientByPubKey
gRPC beacon API call responds on error, then:Before this PR, the call to
GET /eth/v1/validator/{pubkey}/feerecipient
returns the burn address0x0000....
After this PR the call to
GET /eth/v1/validator/{pubkey}/feerecipient
returns:With gRPC implementation, if, for a given
{pubkey}
:{pubkey}
specific fee recipient is set in validator client, ANDGetFeeRecipientByPubKey
gRPC beacon API call responds with anil
value or with an empty value, then:Before this PR, the call to
GET /eth/v1/validator/{pubkey}/feerecipient
returns the burn address0x0000....
After this PR the call to
GET /eth/v1/validator/{pubkey}/feerecipient
returns:With beacon API implementation, if, for a given
{pubkey}
:{pubkey}
specific fee recipient is set in validator client, ANDthe call to
GET /eth/v1/validator/{pubkey}/feerecipient
returns:Warning:
The 400 and 500 code listed above will cause, in Prysm validator WebUI, the following error:
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More →Because this PR breaks the Prysm validator client WebUI, it is marked as
blocked
waiting for the Prysm validator client WebUI (which is in another git repo) update.