rust
rust copied to clipboard
nomad-xyz
Rust work for nomad actors
Should not have agent run-time configuration in the network/contract JSON config files. Also want to be able to more easily override/supply agent config blocks from env. - want break agent...
- same as https://github.com/nomad-xyz/rust/issues/156 but for agent configs - see https://github.com/nomad-xyz/rust/pull/155 for example implementation of default
- we reuse all the same tx signers across networks (e.g. processor tx signer will be same on ethereum, moonbeam, evmos, and milkomeda); even though signer is the same address,...
Includes: - `accumulator` - each agent (kathy, updater, relayer, processor, watcher) - `chains/nomad-ethereum` - `nomad-base` - `nomad-core` - `nomad-test` - `nomad-types`
- `SignerConf` is an ethereum-specific type yet it sits in general crates (configuration and nomad-core) - Want to move `SignerConf` into ethereum specific folder in `configuration` and generalize with VM-based...
- Want to simply port functionality of `report_tx!` macro and move to methods under the `ChainProvider` enum - Functionally, the code will behave the same just but structurally, calling for...
- starting to decouple JSON structure from env variable namespacing - we should replace the long namespaces that match the JSON structs with names easiest for deployment
- updater crash looping makes things very difficult to debug (all grafana graphs are reset) - want to gracefully catch errors like we do relayer, processor, and kathy
- should cut ETH spend particularly in times of high traffic - want to add batching but still an open question as to implementation - One idea: - Internally track...
- once we have bindings for Gelato Relay SDK, we just need to integrate that into our `ChainProvider` enum ``` enum ChainProvider { Local(Arc), Gelato(GelatoClient), } ```