Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bbn 1 fp registry for wizz #12

Closed

Conversation

tyleryu12
Copy link

New wizz Finality Provider

Follow the [README.md](xxx new link) instructions
to generate information.

Checklist

  • [Create EOTS Key](xxx new link)
  • Backup Mnemonic
  • Generate Finality Provider Information
  • Input the information into a file under bbn-1/finality-providers/registry/{nickname}.json
  • [Sign the file](xxx new link)
  • Input the signature into a file under bbn-1/finality-providers/sigs/{nickname}.sig
  • Accept terms and conditions

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 networks.

@RafilxTenfen RafilxTenfen deleted the branch babylonlabs-io:bbn-1-fp-registry August 8, 2024 16:20
@RafilxTenfen
Copy link
Collaborator

Thank you for your submission. The pull request has been closed automatically due to not using main as its base branch.
For the submission to be accepted you need to create a new pull request based on the main branch containing the pull request description outlined in the pull request template. Alternatively, you can rebase the commits of this pull request on the main branch, update your pull request description to include the latest pull request template, and reopen the pull request. Note that only finality providers that have successfully completed the KYB process can be accepted.

@tyleryu12
Copy link
Author

I create a new pull request based on the main branch containing the pull request description outlined in the pull request template #132 .
Can you help check if it is ok?
Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants