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
Enhance the go-zenon deployment script to support a secure sentrify topology, allowing easy configuration of pillar (validator) nodes protected by sentry nodes. This enhancement is inspired by the work of MoonBaZZe: https://github.com/MoonBaZZe/sentrify
Proposed implementation:
Extend the --deploy flag with additional options:
--deploy regular: Deploy a regular node (default behavior)
--deploy testnet: Deploy a testnet node
--deploy sentry: Deploy a sentry node
--deploy pillar: Deploy a sentrified pillar node
For the --deploy pillar option:
Require the user to specify at least two sentry node addresses
Implement automated firewall rules and peer configurations
Optimize network settings for the sentrify topology
Add configuration options for customizing:
Number of sentry nodes (minimum 2)
Connection parameters
This enhancement will improve network security and stability for pillar operators by providing a streamlined way to set up a robust validator infrastructure, while maintaining flexibility for different node types.
The text was updated successfully, but these errors were encountered:
Enhance the go-zenon deployment script to support a secure sentrify topology, allowing easy configuration of pillar (validator) nodes protected by sentry nodes. This enhancement is inspired by the work of MoonBaZZe: https://github.com/MoonBaZZe/sentrify
Proposed implementation:
Extend the --deploy flag with additional options:
--deploy regular
: Deploy a regular node (default behavior)--deploy testnet
: Deploy a testnet node--deploy sentry
: Deploy a sentry node--deploy pillar
: Deploy a sentrified pillar nodeFor the
--deploy pillar
option:Add configuration options for customizing:
This enhancement will improve network security and stability for pillar operators by providing a streamlined way to set up a robust validator infrastructure, while maintaining flexibility for different node types.
The text was updated successfully, but these errors were encountered: