You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upload blobs for confirmed certificates separately. (#3108)
## Motivation
Including blobs with the gRPC message that contains a block proposal or
certificate severely limits the total size of the blobs. (See #3048.)
## Proposal
As a first step, remove the blobs from the
`handle_confirmed_certificate` functions and messages.
Instead, when a validator sees a fully signed confirmed block it creates
the blob states in its local storage even if it doesn't have the blobs
yet. The client can then upload the blobs one by one, and the validator
will accept them. Finally, the client can retry sending the certificate.
We don't do this for block proposals or validated blocks yet: These will
need to be handled differently, because in these cases the blob has not
necessarily been successfully published yet, so we should _not_ create a
blob state. Instead, we will put these blobs into a temporary cache.
## Test Plan
The existing tests are now using the new flow for confirmed block
certificates.
## Release Plan
- Nothing to do / These changes follow the usual release cycle.
## Links
- Part of #3048
- [reviewer
checklist](https://github.com/linera-io/linera-protocol/blob/main/CONTRIBUTING.md#reviewer-checklist)
0 commit comments