James

At the moment, the ledger always starts up `geth` on `http://127.0.0.1:8545` and then the oracle component connects to it via that endpoint. We could allow the setting of a custom...

The best way to do this (imo) may be to use something like `npx hardhat node` and then automatically deploy all the smart contracts, then start up the ledger pointing...

Currently WIP in this PR - https://github.com/anoma/ethereum-bridge/pull/44 - also tracked in this issue - https://github.com/anoma/ethereum-bridge/issues/24

Closed by https://github.com/anoma/ethereum-bridge/pull/44

[cargo llvm-cov](https://github.com/taiki-e/cargo-llvm-cov) works with our codebase, we could use that. It can export the coverage in lcov format which can then be used with IDE plugins like like [Coverage Gutters](https://marketplace.visualstudio.com/items?itemName=ryanluker.vscode-coverage-gutters)...

I see we already run coverage in CI and publish it as an artifact - https://github.com/anoma/namada/blob/076e0162047091d9c19051ed05fb3c74363d14e3/.github/workflows/build-and-test-bridge.yml#L225-L235 We could probably upload the coverage file as well to a service like https://codecov.io...

pls update wasm

It looks like we don't need our Tendermint fork anymore - the only differences between v0.37.0-rc1 and our fork is the addition of the events endpoint - https://github.com/tendermint/tendermint/compare/v0.37.0-rc1...heliaxdev:tendermint:ledger-main - which...

pls update wasm

pls update wasm