-
-
Notifications
You must be signed in to change notification settings - Fork 263
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
While testing #583 by setting Ethereum's defaultNetwork to another e.g mainnet to arbirtum, then run balance command observed that when testing balances without network still return mainnet which should be arbitrum
#### /chains/ethereum/balances
curl --max-time 20 -sS http://localhost:15888/chains/ethereum/balances -u "XXX:XXX" -H 'Content-Type: application/json' -d '{"network":"arbitrum","address":"0x08940dc9B5a19FAb9319b77C61DDA7B8067E6843"}' | jq
{
"balances": {
"ETH": 0.004348634416537926,
"USDT": 3.577757,
"USDC": 0.583528
}
}
logs: not found related error on logs
#### /chains/ethereum/balances w/ no network
curl --max-time 20 -sS http://localhost:15888/chains/ethereum/balances -u "XXX:XXX" -H 'Content-Type: application/json' -d '{"address":"0x08940dc9B5a19FAb9319b77C61DDA7B8067E6843"}' | jq
{
"balances": {
"ETH": 0.006855969459530184,
"USDC": 5.506011
}
}
logs: not found related error on logs
- The balance returned with no network was with
mainnetwhen it should bearbitrumsince its thedefaultNetwork?
Steps to reproduce
- Setup gateway
- Run /config/update endpoints to change defaultNetwork of ethereum namespace from mainnet to prefer e.g arbitrum, avalanche, polygon, etc
- Run /chains/ethereum/balances endpoints with or without network
Release version
v2.12, dev-2.13
Type of installation
Source
Attach required files
n/a
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working