Daniel Cherrett

Investigate and Fix leaks in API tests

1

### Rationale When running API tests on the UI Iteration 2 branch, we are getting the following warning:  In this ticket, we should investigate and fix these leaks. Please...

### Summary of bug The Cosmos REST API returned a proposal with invalid `voting_start_time` and `voting_end_time` fields while the proposal was in voting stage. For this reason, the Cosmos Network...

### Description In the `ui/src/components/installer/panic-installer-channel-form-modal/panic-installer-channel-form-modal.tsx` file, we currently have a single state (`groups`) for all channels. This is not ideal as it decreases maintainability and readability. This should be split...

### Rationale Investigate the use of [git hooks](https://githooks.com/ ) for preventing committing sensitive data. Specifically, pre-receive hooks might be used for this case:  This might be carried out by...

Update Cosmos Network Alerter to check for proposal votes

3

This issues tackles two aspects of the Cosmos Network Monitoring/Alerting: ### User Story As a node operator, I would like to know whether I voted on a given proposal. ###...

### Technical Story As the alert store, I want to avoid overwriting the gas bump increase over node gas price limit alert and the balance top up alert. ### Description...

### Technical Story As the alert store, I want to avoid overwriting slashed alerts and new/concluded proposal alerts. ### Description Currently, we are storing slashed alerts in a single redis...

Investigate the development of pruner component/service within PANIC

2

### Rationale We must investigate the development and use of a _pruner_ component within PANIC. This component entails the following: - Delete the keys of expired alerts from Redis -...

### Rationale Recently we have released a hot-fix which caters for the following `eth_balance` structure found in the prometheus of Chainlink-based nodes: `eth_balance{account="0x12345",evmChainID="123"} 123.456` The `evmChainID` is used to get...

Update managers to index sources by chain_id not chain name

2

Currently, managers are indexing sources/data using the base chain name and the sub chain name. This will become an issue if we are to allow users to modify the name...