Skip to content

Confusion Regarding Pubkey Authorization for ShredStream Service #49

@iciker

Description

@iciker

Hello Jito Team,
I am working on setting up the Jito ShredStream Proxy and have encountered some confusion regarding the public key authorization process specifically for the ShredStream service.
I initially found the form at https://web.miniextensions.com/WV3gZjFwqNqITsMufIEp. The message at the top of this form states: "Block engine access is no longer gated and cannot be requested here."
Despite this message, when I configure and run the shredstream-proxy client using a dedicated public key (for which I hold the private key, as per the form's instructions for ShredStream), I consistently encounter the following PermissionDenied error from the Jito Block Engine:

[2025-05-14T06:47:45Z WARN jito_shredstream_proxy::heartbeat] Failed to connect to block engine, retrying. Error: BlockEngineConnectionError client error: status: PermissionDenied, message: "The supplied pubkey is not authorized to generate a token.", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "server": "jito-block-engine", "x-request-received-at": "2025-05-14T06:47:45.800Z", "content-length": "0", "date": "Wed, 14 May 2025 06:47:44 GMT", "x-envoy-upstream-service-time": "0"} }
[2025-05-14T06:47:45Z WARN solana_metrics::metrics] datapoint: shredstream_proxy-heartbeat_client_error,block_engine_url=https://mainnet.block-engine.jito.wtf errors=1i error_str="BlockEngineConnectionError client error: status: PermissionDenied, message: "The supplied pubkey is not authorized to generate a token.", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "server": "jito-block-engine", "x-request-received-at": "2025-05-14T06:47:45.800Z", "content-length": "0", "date": "Wed, 14 May 2025 06:47:44 GMT", "x-envoy-upstream-service-time": "0"} }"

This error, "The supplied pubkey is not authorized to generate a token.", suggests that an authorization step is still required for the public key to be used with the ShredStream service, which seems to conflict with the "no longer gated" message on the form for general Block Engine access.
Could you please clarify the current and correct procedure for authorizing a new public key specifically for use with the Jito ShredStream service?
Is there a different process or form I should be using for ShredStream authorization?
What are the current steps to get a public key recognized and authorized for ShredStream?
Any guidance on how to proceed would be greatly appreciated.
Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions