Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add redirect in run node page #602

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

feat: add redirect in run node page #602

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
eeb5b19
feat: add redirect in run node page
swarna1101 Mar 12, 2025
206ccc8
Merge branch 'main' into add-redirects
swarna1101 Mar 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions docs/run-node/3-ftso-data-provider.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
sidebar_position: 3
slug: ftso-data-provider
title: FTSO Data Provider
description: Provide block-latency and anchor feeds for FTSOv2.
---

import { Redirect } from "@docusaurus/router";

<Redirect to="/run-node/flare-systems-provider" />

:::info

The FTSO Provider deployment is now integrated into the [`flare-systems-deployment`](https://github.com/flare-foundation/flare-systems-deployment) repository, which also supports FDC deployments. Previously, deployments were managed through the `ftso-v2-provider-deployment` repository.

The older repository is being deprecated. While it remains available for legacy deployments on Flare or Songbird, transitioning to the updated repository is strongly recommended. Active development has shifted to the new repository, where all future updates and features will be introduced. You can find the deprecation notice and detailed upgrade instructions [here](https://github.com/flare-foundation/ftso-v2-provider-deployment/tree/0.3.1-deprecation.2) until the information is merged into the official repository.

For additional information and updates, please follow us on the [Flare forum](https://forum.flare.network/).

:::
22 changes: 22 additions & 0 deletions docs/run-node/4-fdc-attestation-provider.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
sidebar_position: 4
slug: fdc-attestation-provider
title: FDC Attestation Provider
description: Provide attestations for FDC.
---

import { Redirect } from "@docusaurus/router";

<Redirect to="/run-node/flare-systems-provider" />

:::info

The FDC Provider deployment is now integrated into the [`flare-systems-deployment`](https://github.com/flare-foundation/flare-systems-deployment) repository, which also supports FTSO deployments. Previously, deployments were managed through the `ftso-v2-provider-deployment` repository.

The older repository is being deprecated. While it remains available for legacy deployments on Flare or Songbird, transitioning to the updated repository is strongly recommended. Active development has shifted to the new repository, where all future updates and features will be introduced. You can find the deprecation notice and detailed upgrade instructions [here](https://github.com/flare-foundation/ftso-v2-provider-deployment/tree/0.3.1-deprecation.2) until the information is merged into the official repository.

To run the FDC Client, you must also deploy verifiers and nodes that the client depends on. The [`fdc-suite-deployment`](https://github.com/flare-foundation/fdc-suite-deployment) repository contains comprehensive instructions for setting up and deploying these components.

If you already operate some of the required nodes, you can connect the FDC Client to those existing nodes, ensuring that the configurations remain compatible to avoid any operational issues.

:::
Loading