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

Enable the ledger to be able to use a custom Ethereum JSON-RPC endpoint #417

Closed
james-chf opened this issue Sep 1, 2022 · 0 comments
Closed

Comments

@james-chf
Copy link
Contributor

Currently, the ledger always uses 127.0.0.1:8585 as the Ethereum JSON-RPC endpoint for listening for events from the Ethereum bridge smart contracts, which is the endpoint exposed by the local geth subprocess started by the ledger.

We should make this configurable, so that some other endpoint could be used during testing. The local geth subprocess should not be started when a custom endpoint is used.

Relates to #228

@james-chf james-chf self-assigned this Sep 1, 2022
@james-chf james-chf moved this to Todo in Namada-Old Sep 1, 2022
@james-chf james-chf moved this from Todo to WIP in Namada-Old Sep 1, 2022
@james-chf james-chf moved this from WIP to Todo in Namada-Old Sep 2, 2022
@james-chf james-chf moved this from Todo to Pending Devnet in Namada-Old Sep 9, 2022
@james-chf james-chf moved this from Pending Devnet to WIP in Namada-Old Oct 4, 2022
Repository owner moved this from WIP to Tested in Devnet in Namada-Old Oct 10, 2022
phy-chain pushed a commit to phy-chain/namada that referenced this issue Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Tested in Devnet
Development

No branches or pull requests

1 participant