Skip to content

feat: Add a new endpoint for faster uploads in relay#3300

Open
sadhansood wants to merge 2 commits into
mainfrom
sadhan/upload_relay_fast
Open

feat: Add a new endpoint for faster uploads in relay#3300
sadhansood wants to merge 2 commits into
mainfrom
sadhan/upload_relay_fast

Conversation

@sadhansood
Copy link
Copy Markdown
Contributor

@sadhansood sadhansood commented Apr 22, 2026

Description

This PR adds a session based upload relay endpoint for lower latency uploads by accepting systematic primary slivers directly from clients. The client upload workflow using upload relay is now using this experimental endpoint is:

  1. Clients create a sliver upload session
  2. Upload primary slivers in parallel
  3. Complete the session once all required systematic primary slivers are present.

The relay now validates uploaded slivers against the provided blob metadata, uploads metadata and primary slivers to storage nodes with immediate intent as they arrive, derives the remaining primary and secondary slivers during completion, and then finishes the normal storage certification flow.

It also adds support for tipped relay sessions by preflighting and reserving the paid tip transaction at session creation, then verifying the reconstructed raw blob digest against the auth package before completing the upload.

Test plan

Added unit coverage for the sliver upload session flow.


Release notes

Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that
a user might notice and any actions they must take to implement updates. (Add release notes after the colon for each item)

  • Storage node:
  • Aggregator:
  • Publisher:
  • CLI:

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 22, 2026

Warning: This PR modifies one of the OpenAPI files. Please consider the
following:

  • Make sure the API changes are backwards compatible.
  • Make sure to follow existing conventions for any added parameters, requests, and
    responses.
  • Make sure the generated HTML files do not contain errors.
  • This probably requires release notes and maybe changes to the documentation.

cc @jpcsmith @mlegner

@github-actions
Copy link
Copy Markdown
Contributor

This PR is stale because it has been open 14 days with no activity. It will be closed in 7 days unless you remove the stale label, add the do-not-close label, or comment on it.

@github-actions github-actions Bot added the stale label May 11, 2026
Copy link
Copy Markdown

@imamnugrh-web imamnugrh-web left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

commits

@github-actions github-actions Bot removed the stale label May 18, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 1, 2026

This PR is stale because it has been open 14 days with no activity. It will be closed in 7 days unless you remove the stale label, add the do-not-close label, or comment on it.

@github-actions github-actions Bot added the stale label Jun 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants