docs: remove BNs from DFP

[Bidon15]

Overview

[gemini-code-assist]

Summary of Changes

Hello @Bidon15, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the documentation for the Foundation Delegation Program by removing all mentions and requirements related to bridge nodes. It streamlines the application process and participation criteria by eliminating the need for archival bridge nodes and introduces a new requirement for running Fibre when it becomes available. The changes reflect an evolution in the program's technical prerequisites.

Highlights

• Removed Bridge Node Requirements: The documentation for the Foundation Delegation Program no longer requires participants to run or maintain archival bridge nodes on Mainnet Beta.
• Added Fibre Requirement: A new requirement has been introduced, stating that participants must run Fibre once it is live.
• Updated Application Information: The 'Infrastructure' section of the application details has been revised to remove references to bridge node IDs and their setup, focusing solely on validator information.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• app/operate/consensus-validators/foundation-delegation-program/page.mdx
  • Removed two bullet points detailing bridge node requirements from the minimum participation criteria.
  • Added a new bullet point for running Fibre once it is live to the minimum participation criteria.
  • Updated the 'Infrastructure' section to remove references to 'bridge node ID' and 'setup of the 2 components (validator and bridge)', simplifying it to 'validator address' and 'setup of the validator'.
  • Removed an 'IMPORTANT' note at the end of the document regarding maintaining a fully archival bridge node.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request removes the requirement for running a Bridge Node (BN) from the Foundation Delegation Program (DFP) documentation. The changes are consistent throughout the document, updating eligibility criteria and application details. I have one suggestion to improve the clarity of a newly added requirement.

[gemini-code-assist]

The new requirement to "Run Fibre once it is live" might be unclear to users, as this is the only mention of "Fibre" in this document. To improve clarity, consider adding a brief explanation of what "Fibre" is or linking to a resource with more information. If details are not yet available, a rephrasing could manage expectations better.

- Be prepared to run Fibre once it becomes available (details to follow)

[github-actions]

🚀 Preview Deployment

Your preview is ready: https://celestiaorg.github.io/docs-preview/pr-2416/

[gbarros]

Verified! LGTM