-
Notifications
You must be signed in to change notification settings - Fork 671
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
Nakamoto[Block Validation]: Comms channels for RPC handler and block template/validation #3864
Comments
This was referenced Aug 30, 2023
Merged
I think this can be dropped |
I’m not sure that this can be dropped. Stackers still need to use a block validation endpoints, right? |
Ah, yes - the validation endpoint would be necessary. My head was caught up
thinking about the block producer needs when I wrote that comment.
…On Tue, Sep 5, 2023, 7:50 AM Aaron Blankstein ***@***.***> wrote:
I’m not sure that this can be dropped. Stackers still need to use a block
validation endpoints, right?
—
Reply to this email directly, view it on GitHub
<#3864 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADQJK4ZA6M5WLRWM3UQ4JTXY4GZDANCNFSM6AAAAAA32IECHY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
saralab
changed the title
Nakamoto: Comms channels for RPC handler and block template/validation
Nakamoto[Block Validation]: Comms channels for RPC handler and block template/validation
Jan 8, 2024
This was implemented in #4228 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
RPC methods for assembling a block template and validating a block must
be asynchronous: block assembly and validation are slow operations, and
the network stack should not stall while processing them. In order to
facilitate this, the RPC handler will send a request for template
generation or block validation over a comms channel. A different
thread will handle the work and then pass the result via the event
interface.
The text was updated successfully, but these errors were encountered: