-
Notifications
You must be signed in to change notification settings - Fork 233
Open
Labels
devCritical path development tasksCritical path development taskspost-launchThings to do after first mainnet releaseThings to do after first mainnet release
Description
Currently Intel's certificate is hard-coded in the registration module. We probably should move it to be saved at genesis on-chain, and then pulled from the store when required. Would make things more transparent, and possible to upgrade when/if we need to change it via parameter (governance change).
** Need to consider that this governance change will break attestation if it isn't done at the right time (if one of the certificates becomes invalid), so no new nodes will be able to join the network (though if they change their cert, the validity times will probably overlap, making this a non-issue)
Metadata
Metadata
Assignees
Labels
devCritical path development tasksCritical path development taskspost-launchThings to do after first mainnet releaseThings to do after first mainnet release