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
* feat(agent): Add config toggle for Horizon functionality
Introduces a `horizon_enabled` boolean flag within `SenderAccountConfig`, populated from the main application configuration (`config.horizon.enabled`).
This flag gates Horizon-specific functionality within the TAP agent:
- In `SenderAccount`:
- Database operations (fetching RAVs, querying/updating denylist) for `SenderType::Horizon` are now conditional on this flag being true.
- The `todo!()` for querying unfinalized V2 transactions is now only relevant if Horizon is enabled.
- A temporary check (`FIXME`) is added to `deny_sender_if_insolvent` to bypass denial logic for Horizon senders if the feature is disabled via config.
- In `SenderAccountsManager`:
- Fetching pending V2 (Horizon) sender allocations is skipped if the flag is false.
- The `new_receipts_watcher` task for V2/Horizon is only spawned if the flag is true.
This allows Horizon-related features, which may still be under development, to be effectively disabled via configuration, simplifying testing and allowing for incremental rollout without impacting existing functionality if Horizon support is not desired or ready.
* fix(test): Remove database migration by default
* fix(config): Add missing horizon setting to config files
fix(config): add missing config field
* chore(test): Change test function name to indicate it works for RAV V1 only
* fix(testnet): Remove commented code
0 commit comments