Serhii Volovyk

Results 80 issues of Serhii Volovyk

### Description We need to make sure that this flow works and that we do not confuse signer with predecessor, etc.

Near BOS
Emerging Tech

We should specify what version of Sandbox, Relayer, etc. we are using. That should have to make our testing env consistent on all machines and CI.

Near BOS
Emerging Tech

### Description The difference is these two is that in the **Rejoining** state we are already in the participants map and have **ParticipantId**. The additional state may simplify logic in...

Near BOS
Emerging Tech

Currently, only prod (mainnet) is using CloudRun.

Near BOS
Emerging Tech

### Description Our PRs has their own tmp GCP infra deployed automatically. We can add separate job in GitHub actions that will test all the system end to end on...

Near BOS
Emerging Tech

### Description We are using LeaderNodeError::RelayerError in functions, that are not directly related to relayer. As a result, we can return a Relayer error even if it has nothing to...

Near BOS
Emerging Tech

In case we need to change one of the validationg nodes, we will need to have this functionality. Same goes for the situation when we move to treshold signing.

Near BOS
Emerging Tech

Our preferable design will include Key Derivation. Let's add a simplified logic, that generate the users key out of the root key and user internal id.

Near BOS
Emerging Tech

@itegulov seted up the infrastructure for alerts in Graphana and Slack. Let's agree an a list of alerts we want to have. Partially blocked on https://github.com/near/mpc-recovery/issues/242 since we can not...

Near BOS
Emerging Tech