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

fix: update prover client #273

Closed

Conversation

quangtuyen88
Copy link
Contributor

Base on this PR https://github.com/taikoxyz/taiko-mono/pull/17302/files
some variables already removed and prover client need to be updated with this change

@quangtuyen88 quangtuyen88 changed the title update prover client fix: update prover client May 25, 2024
@smtmfft
Copy link

smtmfft commented May 27, 2024

Some are moved into raiko, like rpc conf.
Please refer to: https://github.com/taikoxyz/raiko/blob/release/v1.0.0/docs/README_Docker_and_RA.md#running-raiko .

Generally speaking, raiko becomes a standalone prove service provider, so user need to config raiko before proposal asks proof before it. And from client's point of view, it just tell raiko which block & which type of proof it needs.

For JWT token, default raiko does not config that, if you want, you need to customize the docker-compose.yml https://github.com/taikoxyz/raiko/blob/release/v1.0.0/docker/docker-compose.yml with a new flag. As it's error-prone, we don't support enable/config that one in raiko by default.

@quangtuyen88
Copy link
Contributor Author

https://github.com/taikoxyz/raiko/blob/release/v1.0.0/docker/docker-compose.yml

Hello @smtmfft Yes understood.. that's why i make that variable is not mandentory require RAIKO_JWT . Unless you config JWT on Raiko it's not require setting this value RAIKO_JWT on Simple Taiko Node

.env.sample Show resolved Hide resolved
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

Successfully merging this pull request may close these issues.

4 participants