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

[Testnet] Onboard New Maintainer Teams to Testnet #1586

Open
RossiNYC opened this issue Nov 21, 2023 · 3 comments
Open

[Testnet] Onboard New Maintainer Teams to Testnet #1586

RossiNYC opened this issue Nov 21, 2023 · 3 comments
Assignees
Labels
community Open to or owned by a non-core team member

Comments

@RossiNYC
Copy link

No description provided.

@RossiNYC RossiNYC self-assigned this Nov 21, 2023
@RossiNYC RossiNYC converted this from a draft issue Nov 21, 2023
@RossiNYC RossiNYC added the community Open to or owned by a non-core team member label Nov 21, 2023
@RossiNYC
Copy link
Author

RossiNYC commented Nov 21, 2023

Process is as follows:

  1. New teams to sync up testnets node(s)
  2. We will divide up the keys as listed to identify their nodes (https://github.com/pokt-network/pocket-core-internal-deployments/blob/master/testnet/KEYS.md)
  3. I will drop a Forum Post explaining Testnet switch-over is happening and will result in a short blackout
  4. We ask NodeFleet to unstake their nodes
  5. We ask the new team to stake in their nodes
  6. I update the Forum Post that Testnet is live

@icculp

@Olshansk
Copy link
Member

  1. We ask NodeFleet to unstake their nodes
  2. We ask the new team to stake in their nodes

There is no need for staking and unstaking.

  1. NodeFleet turns down their nodes.
  2. New team (with synched nodes) can validate (4) by inspecting network traffic or the mempool to make sure no new blocks are being proposed to avoid double-signing, errors, etc...
  3. New team leverages the keys w/o needing to re-stake.
  4. ...

Assumption: NodeFleet is a cooperative & non-adversarial cooperative party in the transition of TestNet. If this assumption does not hold true, the range of possibilities and scope of the problem expands greatly.

@RossiNYC
Copy link
Author

NodeFleet are actively helping the new team onboard and we're on pace to have handover by EOD Monday 11/27.

@Olshansk Olshansk added this to the Network Quality of Life milestone Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Open to or owned by a non-core team member
Projects
Status: In Progress
Development

No branches or pull requests

2 participants