Summary
Add the ability to monitor specific account balances and trigger alerts when they cross configurable thresholds.
Use Case
This would enable proactive monitoring of critical accounts such as treasury wallets, operational accounts, or hot wallets to detect when balances are running low (or unexpectedly high), allowing teams to take action before issues arise.
Proposed Configuration
Extend the existing account entries in networks.toml with optional threshold fields (just a suggested solution):
[networks."Autonomys Mainnet"]
accounts = [
{ name = "Operations", address = "suesYE9yAqNJrMiZPY4hKNMjMTXBkkD1rHgQrSNes1bUnw37U", alert_below = 1000 },
{ name = "Market Liquidity", address = "subTKWVig3CiwwnPfKccXZHQKwnE36vNHfNTEUx3yYja4UNR9", alert_below = 50000, alert_above = 5000000 },
# Accounts without thresholds continue to work as before
{ name = "Investors", address = "sucGPHK3b4REe2DNRvNaUrmcoXVDDZVasm7zBNtev4zUpLrp4" },
]Proposed Behaviour
alert_below: trigger alert when balance drops below this valuealert_above: trigger alert when balance exceeds this value (optional)- Thresholds in whole AI3 units (or Shannons, TBD)
- Only alert on threshold crossings (state change), not continuously while below/above
- Consider hysteresis to prevent alert flapping near the threshold boundary
Summary
Add the ability to monitor specific account balances and trigger alerts when they cross configurable thresholds.
Use Case
This would enable proactive monitoring of critical accounts such as treasury wallets, operational accounts, or hot wallets to detect when balances are running low (or unexpectedly high), allowing teams to take action before issues arise.
Proposed Configuration
Extend the existing account entries in
networks.tomlwith optional threshold fields (just a suggested solution):Proposed Behaviour
alert_below: trigger alert when balance drops below this valuealert_above: trigger alert when balance exceeds this value (optional)