You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enable the block node to be deployed with only selected services. The selection of services is not set and no individual service is required. The only limitation is that at least one service must be deployed.
Detail
Block Node must be possible to deploy with more or fewer services installed than the "default" full node deployment. This has a few implications.
A block node that is not in the "default" configuration is not required to meet "deterministic build" requirements
A block node may have a very small set of services (e.g. publisher api service and verification service only).
A block node may have a very large set of services (e.g. all "default" services plus a dozen or more add-on services).
A block node may have multiple of the same "type" of service (e.g. two archive services, one to package up blocks as zip files, another to remove any file older than 1 month, and another to copy zip files to cloud storage).
A block node should be able to determine what services are present at startup, not during compilation.
The text was updated successfully, but these errors were encountered:
Goal
Enable the block node to be deployed with only selected services. The selection of services is not set and no individual service is required. The only limitation is that at least one service must be deployed.
Detail
Block Node must be possible to deploy with more or fewer services installed than the "default" full node deployment. This has a few implications.
The text was updated successfully, but these errors were encountered: