-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(BIDS 3226) API: Block Details v2 (Internal) #637
Conversation
2cc3f17
to
d2e2cd6
Compare
Deploying beaconchain with
|
Latest commit: |
189f0be
|
Status: | ✅ Deploy successful! |
Preview URL: | https://8155019b.beaconchain.pages.dev |
Branch Preview URL: | https://bids-3226-api-blocks.beaconchain.pages.dev |
d2e2cd6
to
c8f6185
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm so far, pls make one of everything for slots too 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, don't forget to let FE team approve structs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good from the FE point of view, just have one remark
/** | ||
* General | ||
*/ | ||
block: number /* uint64 */; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some properties overlap between the BlockOverview
and the BlockExecutionPayload
.
Wouldn't it be enough to have them just in the BlockExecutionPayload
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was just done because of our approach to design the internal api closely tailored to the designs and keep the frontend as simple as possible. But you're right, that information is redundant and can be removed, see the new changes; I've kept the duplicates in the base BlockOverview
though because BlockExecutionPayload
is intended to be present for POS blocks only
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.