I want the bounty contract to be updated again with the new ssh keys. It is unacceptable for us to be deprived of rewards and kicked out of the community because of old ssh keys.
Deleted or missing SSH keys As a security precaution, GitHub automatically deletes SSH keys that haven’t been used in a year.
GitHub automatically deletes inactive SSH keys to help keep accounts safe, such as after someone leaves a job or loses a computer.
You can check if you haven’t used an SSH key in a year by reviewing your account’s security log. For more information, see “Reviewing your security log.”
After your inactive SSH key is deleted, you must generate a new SSH key and associate it with your account. For more information, see “Generating a new SSH key and adding it to the ssh-agent” and “Adding a new SSH key to your GitHub account.”
As a result, we met the criteria of the fluence network team. I have a similar problem too. We see the snapshot in the metadata.json file they received. I found the backups, but a warning appears that a previously used SSH key cannot be used again on github. At least let us define a new ssh key and send a pull request.
I want the bounty contract to be updated again with the new ssh keys. It is unacceptable that we are deprived of rewards and kicked out of the community because of old keys. Deleted or missing SSH keys As a security precaution, GitHub automatically deletes SSH keys that have not been used for a year. GitHub automatically deletes inactive SSH password…
If we are truly going to be a fluence community, the team will find a solution to this. Because most people are victims of this issue, I trust the team and they will take this into consideration.