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.

Sign up for GitHub

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

Jump to bottom

Allow any L1 provider #272

Closed
xavier-romero opened this issue Jul 3, 2024 · 1 comment
Closed

Allow any L1 provider #272

xavier-romero opened this issue Jul 3, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@xavier-romero
Copy link
Contributor

The ENV file requires this parameter:
INFURA_PROJECT_ID
And then builds the L1 URL like that:
https://mainnet.infura.io/v3/${process.env.INFURA_PROJECT_ID}
It would be useful to just accept the whole L1 URL in a var, like this:
L1_URL
So I can use whatever provider I wish, or even my own RPC node, instead of being forced to use Infura.
@xavier-romero xavier-romero added the enhancement New feature or request label Jul 3, 2024
@krlosMata
Copy link
Contributor

you can choose your own provider with MAINNET_PROVIDER environment var.
Here to choose from your provider or infura one: https://github.com/0xPolygonHermez/zkevm-contracts/blob/main/hardhat.config.ts#L144C30-L144C46

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@invocamanman @krlosMata @xavier-romero