Support adding validators to remote L1s (Fuji)

[meaghanfitzgerald]

Goal

Enable users to create a new local node and add it as a validator to an L1 that is already deployed and running on a remote machine. This simulates the workflow for users who wish to validate proof of stake networks.

For Example

Michael has created and deployed a PoS L1, and Raymond wants to add his local node as a Validator to said L1.

Requirements:

CLI must fetch or require the user provide:

1. Fuji RPC endpoint
2. L1 RPC endpoint
3. The BlockchainID and SubnetID of the L1 the user wishes to join
4. the NodeID and BLSPublicKey
5. The address of the validator manager contract
6. The type of validator manager contract being used (NativeTokenStakingManager, ERC20StakingManager, or PoAValidatorManager). This MVP assumes NativeTokenStakingManager.
7. The user's address funded with:

• P-Chain AVAX for the balance
• staking tokens

8. The amount the user wishes to stake
9. The minimum delegation fee
10. The desired stake duration

Assumptions for a MVP Functionality

• This flow is able to add a PoS validator to an L1 that uses the NativeTokenStakingManager standard validator manager contract.

Current limitations

Nice to Have, but Not Required

• This flow is also able to add a PoS validator to an L1 that uses the ERC20TokenStakingManager standard validator manager contract.
  • Important: A potential validator must already have called increasedAllowance on the ERC20 staking token contract before attempting to stake that allowed amount of the token into the ERC20TokenStakingManager contract.

[meaghanfitzgerald]

#2548