You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I found the ledger_id and chain_id usage for integration with multiple chains quite cumbersome.
I believe it makes more sense to route messages pointed at a say optimism to the optimism ledger, as opposed to configuring the ethereum ledger with a chain_id of optimism.
This is a not hugely intuitive and afaict it also means you cannot have 1 agent controilling 2 different evm chains without carefui crafting of messages as so;
Is your feature request related to a problem? Please describe.
I found the ledger_id and chain_id usage for integration with multiple chains quite cumbersome.
I believe it makes more sense to route messages pointed at a say
optimism
to the optimism ledger, as opposed to configuring the ethereum ledger with a chain_id ofoptimism
.This is a not hugely intuitive and afaict it also means you cannot have 1 agent controilling 2 different evm chains without carefui crafting of messages as so;
In the below is the current interface;
Describe the solution you'd like
Id like to instead propose a mapping of EVM chains to ethereum ledgers within the file;
open-aea/packages/valory/connections/ledger/base.py
Line 161 in 80b4321
If we create a hashmap like so;
Then, the interface would be like so;
This would make way way more sense, and then all of the ledger configured within the ledger package would be used by default.
Additionally we wouldnt be over-riding chain_id which is commonly used else where within the industry with a different meaning.
The text was updated successfully, but these errors were encountered: