bbn-1: fp: registry: Update chorusone identity

[vchong]

Update chorusone Finality Provider

Checklist

• I have followed the finality provider information registry guide
• I have backed up my mnemonic
• I have read and agree to the Babylon Ecosystem Participant License and the Babylon Ecosystem Participant Agreement.

Caution

The loss of the (generated keys + mnemonic) makes the finality provider
useless and unable to provide finality, which would lead to no transition to
later phases of the Babylon network.

[vchong]

$ ./bbn-1/finality-providers/scripts/verify-valid-fp.sh chorusone
Verifying ~/babylon/bbn-1-networks/bbn-1/finality-providers/scripts/../registry/chorusone.json
Finality Provider Moniker: Chorus One
Finality Provider Security Contact: [email protected]
Finality Provider Commission: 0.05
Finality Provider EOTS Public Key: cef496d86c284f01e9cb293b5993e5e00df2116e4d7d7350d68276859561ae67
Finality Provider Signature: 3216d6db9222d418a47763ad32bd95ebe17b2f51abd24fd83d2a7b4f229d1e43531bdb07054e70ceee6a1ff222f5d1b2a004eacd88ffd26b2e9344cf1f020d79
Verifying signature with eotsd...
Verification is successful!

[filippos47]

Hey team @vchong , please include the PR description as documented here: https://github.com/babylonlabs-io/networks/tree/main/bbn-1/finality-providers#5-create-pull-request

[vchong]

Hey team @vchong , please include the PR description as documented here: https://github.com/babylonlabs-io/networks/tree/main/bbn-1/finality-providers#5-create-pull-request

ah, apologies.. updated above