Skip to content
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

Reuse same JWT token from op-node for proposer op-geth #9

Open
ferranbt opened this issue Sep 27, 2024 · 3 comments
Open

Reuse same JWT token from op-node for proposer op-geth #9

ferranbt opened this issue Sep 27, 2024 · 3 comments

Comments

@ferranbt
Copy link
Collaborator

I think it makes sense that if rollup-boost is a middleware sidecar for proposer op-node/op-geth we can reuse the same JWT token we receive from proposer op-node to send the requests to proposer op-geth.

Then, the jwt-token flag would represent the jwt token between rollup-boost and builder op-geth.

@avalonche
Copy link
Collaborator

there's some issues with the jsonrpsee library to support this, will need to raise issue there

@liamaharon
Copy link
Collaborator

@avalonche could you elaborate on the issues are you're seeing with jsonrpsee, do you have a branch?

@avalonche
Copy link
Collaborator

The json rpc server proxies engine calls by using a jsonrpsee HttpClient.

The problem here is that there is no way for HttpClient to proxy / access the headers of the incoming request to the server per request. The jwt token in the header is derived from the jwt secret + timestamp so it is different for every request.

The alternative would be to instantiate a new HttpClient at the middleware layer per request, since the headers are static when the client is instantiated. One workaround could be adding a set_header function without initiating a new client per request, but still wacky.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants