FLIP 64 - Identifying and Ejecting Errant Access Nodes

Governance FLIPs
#1

Identifying and Ejecting Errant Access Nodes

Status Proposed
FLIP # 64
Author(s) James Lofgren ([email protected])
Sponsor @kshitij.chaudhary @vishal
FLIP Document https://github.com/onflow/flips/blob/main/governance/20230105-identify-errant-node.md

The launch of permissionless ANs is an important step in the continued decentralization of Flow, but also creates an opportunity for byzantine nodes to send malicious traffic to other staked nodes. The FLIP focuses on proposing a community-observed, community-driven and cost-effective plan for operators to communicate about errant behavior of Access Nodes, and lays out a plan for the service account administrators to eject such errant nodes once community consensus has been built.

1 Like
#2

LGTM. Looking forward to seeing it implemented!

#3

I really can’t understand this:

Individual node operators can protect network liveness through standard network monitoring and infrastructure best practices such as blocking messages, firewall rules, and rate-limiting, until the issue can be resolved.

This is great power to give to EN. We need to decide AN is inside network or not.