From 1a0ac776054534c060d0b2f5585ec9f9b33e2152 Mon Sep 17 00:00:00 2001 From: vishal <1117327+vishalchangrani@users.noreply.github.com> Date: Fri, 1 May 2026 16:53:29 -0400 Subject: [PATCH 1/6] FLIP 367: Remove unresponsive Lilico verification node from approved list Co-Authored-By: Claude Opus 4.6 --- ...0260501-remove-lilico-verification-node.md | 76 +++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 governance/20260501-remove-lilico-verification-node.md diff --git a/governance/20260501-remove-lilico-verification-node.md b/governance/20260501-remove-lilico-verification-node.md new file mode 100644 index 00000000..f4d1cf90 --- /dev/null +++ b/governance/20260501-remove-lilico-verification-node.md @@ -0,0 +1,76 @@ +--- +Status: Draft +Flip: 367 +Authors: Vishal Changrani +Sponsor: Vishal Changrani +Updated: 2026-05-01 +--- + +# FLIP 367: Remove unresponsive Lilico verification node from approved list + +## Objective + +Remove the Lilico-operated verification node from the approved list of nodes so that it gets unstaked in the next epoch. + +## Motivation + +Verification node `3c6519ba8be35e338df7273a895ad3abaeb0c232eb908ee7b05462018c112fe1` operated by Lilico has not been updated to the latest node software. The Flow Foundation has made multiple attempts to contact the node operator, all of which have gone unanswered. The node is running with tokens leased by the Foundation. + +An outdated verification node poses a risk to network health and reliability. Since the operator is unresponsive and the node runs on Foundation-leased tokens, the appropriate action is to remove it from the approved list. + +## User Benefit + +Improved network reliability by ensuring all verification nodes are running up-to-date software. + +## Design Proposal + +Remove node ID `3c6519ba8be35e338df7273a895ad3abaeb0c232eb908ee7b05462018c112fe1` from the approved list of nodes. This will cause the node to be unstaked at the next epoch boundary. + +### Drawbacks + +The network loses one verification node, marginally reducing verification redundancy. However, an outdated node provides limited value and may actively harm network operations. + +### Alternatives Considered + +- **Continue outreach**: The Foundation has already made multiple attempts with no response. +- **Do nothing**: Leaves an outdated node running on the network, which is undesirable. + +### Performance Implications + +No negative performance impact. Removing an outdated node may improve network performance. + +### Dependencies + +None. + +### Engineering Impact + +Minimal. This is a configuration change to the approved node list. + +### Best Practices + +Node operators running on leased tokens are expected to keep their nodes updated and remain responsive to the Foundation. + +### Tutorials and Examples + +Not applicable. + +### Compatibility + +No compatibility concerns. This is a governance action. + +### User Impact + +The Lilico verification node will be unstaked at the next epoch. No impact on other users or node operators. + +## Related Issues + +- [FLIP Tracker Issue](https://github.com/onflow/flips/issues/367) + +## Prior Art + +- [FLIP 365: Removing Blocto as a multi-signer](https://github.com/onflow/flips/blob/main/governance/20260413-removing-blocto-from-multi-sig.md) — similar governance action for an unresponsive community member. + +## Questions and Discussion + +Discussion will take place on the PR itself. From 0e557491f6b7d78452e5ece02229c9c56a6583cf Mon Sep 17 00:00:00 2001 From: vishal <1117327+vishalchangrani@users.noreply.github.com> Date: Fri, 1 May 2026 16:57:29 -0400 Subject: [PATCH 2/6] Remove Prior Art, Best Practices, and Engineering Impact sections --- .../20260501-remove-lilico-verification-node.md | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/governance/20260501-remove-lilico-verification-node.md b/governance/20260501-remove-lilico-verification-node.md index f4d1cf90..09869d12 100644 --- a/governance/20260501-remove-lilico-verification-node.md +++ b/governance/20260501-remove-lilico-verification-node.md @@ -43,14 +43,6 @@ No negative performance impact. Removing an outdated node may improve network pe None. -### Engineering Impact - -Minimal. This is a configuration change to the approved node list. - -### Best Practices - -Node operators running on leased tokens are expected to keep their nodes updated and remain responsive to the Foundation. - ### Tutorials and Examples Not applicable. @@ -67,10 +59,6 @@ The Lilico verification node will be unstaked at the next epoch. No impact on ot - [FLIP Tracker Issue](https://github.com/onflow/flips/issues/367) -## Prior Art - -- [FLIP 365: Removing Blocto as a multi-signer](https://github.com/onflow/flips/blob/main/governance/20260413-removing-blocto-from-multi-sig.md) — similar governance action for an unresponsive community member. - ## Questions and Discussion Discussion will take place on the PR itself. From adca0195750db3f6fb7a079d1bd2097cba0d3de6 Mon Sep 17 00:00:00 2001 From: vishal <1117327+vishalchangrani@users.noreply.github.com> Date: Fri, 1 May 2026 16:58:32 -0400 Subject: [PATCH 3/6] Remove Tutorials and Examples section --- governance/20260501-remove-lilico-verification-node.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/governance/20260501-remove-lilico-verification-node.md b/governance/20260501-remove-lilico-verification-node.md index 09869d12..844a702a 100644 --- a/governance/20260501-remove-lilico-verification-node.md +++ b/governance/20260501-remove-lilico-verification-node.md @@ -43,10 +43,6 @@ No negative performance impact. Removing an outdated node may improve network pe None. -### Tutorials and Examples - -Not applicable. - ### Compatibility No compatibility concerns. This is a governance action. From a2c685e01ce31d22d3044bb98a54f177ec506c1b Mon Sep 17 00:00:00 2001 From: Vishal <1117327+vishalchangrani@users.noreply.github.com> Date: Thu, 7 May 2026 18:20:04 -0400 Subject: [PATCH 4/6] Update 20260501-remove-lilico-verification-node.md --- governance/20260501-remove-lilico-verification-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/governance/20260501-remove-lilico-verification-node.md b/governance/20260501-remove-lilico-verification-node.md index 844a702a..156491c7 100644 --- a/governance/20260501-remove-lilico-verification-node.md +++ b/governance/20260501-remove-lilico-verification-node.md @@ -1,5 +1,5 @@ --- -Status: Draft +Status: Proposed Flip: 367 Authors: Vishal Changrani Sponsor: Vishal Changrani From 778404e2bd01db433764f333f400fc70061b443c Mon Sep 17 00:00:00 2001 From: Vishal <1117327+vishalchangrani@users.noreply.github.com> Date: Wed, 13 May 2026 16:22:14 -0400 Subject: [PATCH 5/6] Update 20260501-remove-lilico-verification-node.md --- governance/20260501-remove-lilico-verification-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/governance/20260501-remove-lilico-verification-node.md b/governance/20260501-remove-lilico-verification-node.md index 156491c7..5e65fc43 100644 --- a/governance/20260501-remove-lilico-verification-node.md +++ b/governance/20260501-remove-lilico-verification-node.md @@ -1,5 +1,5 @@ --- -Status: Proposed +Status: Released Flip: 367 Authors: Vishal Changrani Sponsor: Vishal Changrani From 2452b8410505a4ea225c5e561058bc5430608408 Mon Sep 17 00:00:00 2001 From: Vishal <1117327+vishalchangrani@users.noreply.github.com> Date: Wed, 13 May 2026 16:23:28 -0400 Subject: [PATCH 6/6] Update 20260501-remove-lilico-verification-node.md --- governance/20260501-remove-lilico-verification-node.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/governance/20260501-remove-lilico-verification-node.md b/governance/20260501-remove-lilico-verification-node.md index 5e65fc43..08ff73a1 100644 --- a/governance/20260501-remove-lilico-verification-node.md +++ b/governance/20260501-remove-lilico-verification-node.md @@ -3,7 +3,7 @@ Status: Released Flip: 367 Authors: Vishal Changrani Sponsor: Vishal Changrani -Updated: 2026-05-01 +Updated: 2026-05-13 --- # FLIP 367: Remove unresponsive Lilico verification node from approved list @@ -58,3 +58,6 @@ The Lilico verification node will be unstaked at the next epoch. No impact on ot ## Questions and Discussion Discussion will take place on the PR itself. + +## Transaction +https://www.flowscan.io/tx/2887ef2f221291ec49b996cb26e73f472d55887278212a85ac8e05c3a7f27cb7