diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index f607c25b82..f59ab950df 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -103,7 +103,7 @@ jobs:
       - name: Generate coverage report
         run: |
           go test ./... -coverprofile=coverage.out -covermode=atomic -timeout=20m
-      - uses: codecov/codecov-action@v5.1.1
+      - uses: codecov/codecov-action@v5.1.2
         with:
           files: ./coverage.out
           flags: unit-tests
diff --git a/.github/workflows/dispatch-baremetal.yml b/.github/workflows/dispatch-baremetal.yml
index 84bf19fe1f..e8030dc3c1 100644
--- a/.github/workflows/dispatch-baremetal.yml
+++ b/.github/workflows/dispatch-baremetal.yml
@@ -22,6 +22,17 @@ on:
         options:
           - paseo
           - westend
+      instance:
+        description: 'Instance'
+        required: true
+        default: ''
+        type: choice 
+        options:
+          - hetzner-gossamer-westend
+          - hetzner-gossamer-westend-2
+          - hetzner-gossamer-paseo
+          - hetzner-gossamer-paseo-2 
+          - hetzner-gossamer-polkadot
       gossamerStartArgs:
         description: 'Arguments'
         required: false
@@ -50,6 +61,7 @@ jobs:
                 "commit": "${{ github.event.inputs.commit }}",
                 "nodeType": "${{ github.event.inputs.nodeType }}",
                 "chain": "${{ github.event.inputs.chain }}",
+                "instance": "${{ github.event.inputs.instance }}",
                 "gossamerStartArgs": "${{ github.event.inputs.gossamerStartArgs }}"
               }
             }
diff --git a/.github/workflows/staging.yml b/.github/workflows/staging.yml
deleted file mode 100644
index f2aadc34b1..0000000000
--- a/.github/workflows/staging.yml
+++ /dev/null
@@ -1,54 +0,0 @@
-name: staging
-on:
-  push:
-    branches:
-      - staging
-
-jobs:
-  update:
-    strategy:
-      matrix:
-        chain: [polkadot, kusama, westend]
-    runs-on: buildjet-4vcpu-ubuntu-2204
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Configure AWS Credentials
-        uses: aws-actions/configure-aws-credentials@v4
-        with:
-          aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
-          aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-          aws-region: us-east-2
-
-      - name: Login to Amazon ECR
-        id: login-ecr
-        uses: aws-actions/amazon-ecr-login@v2
-
-      - name: Build, tag, and push image to Amazon ECR
-        id: build-image
-        env:
-          ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }}
-          ECR_REPOSITORY: gossamer-${{ matrix.chain }}
-          IMAGE_TAG: ${{ github.sha }}
-          CHAIN: ${{ matrix.chain }}
-          DD_API_KEY: ${{ secrets.DD_API_KEY }}
-        run: |
-          docker build -f=Dockerfile.staging . --progress=plain -t=$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG --build-arg chain=$CHAIN --build-arg DD_API_KEY=$DD_API_KEY
-          docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG
-          echo "::set-output name=image::$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG"
-
-      - name: Render Amazon ECS task definition
-        id: task-def
-        uses: aws-actions/amazon-ecs-render-task-definition@v1
-        with:
-          task-definition: .github/workflows/staging/${{ matrix.chain }}-taskdef.json
-          container-name: gossamer-${{ matrix.chain }}
-          image: ${{ steps.build-image.outputs.image }}
-
-      - name: Deploy Amazon ECS task definition
-        uses: aws-actions/amazon-ecs-deploy-task-definition@v2
-        with:
-          task-definition: ${{ steps.task-def.outputs.task-definition }}
-          service: gossamer-${{ matrix.chain }}-svc
-          cluster: gossamer-stg
-          wait-for-service-stability: true
diff --git a/.github/workflows/staging/kusama-taskdef.json b/.github/workflows/staging/kusama-taskdef.json
deleted file mode 100644
index 3bbc41b41c..0000000000
--- a/.github/workflows/staging/kusama-taskdef.json
+++ /dev/null
@@ -1,49 +0,0 @@
-{
-    "containerDefinitions": [
-        {
-            "logConfiguration": {
-                "logDriver": "awslogs",
-                "options": {
-                    "awslogs-group": "gossamer-staging-CWLogsGroup-wPH0S1xHYmq7",
-                    "awslogs-region": "us-east-2",
-                    "awslogs-stream-prefix": "ecs"
-                }
-            },
-            "portMappings": [
-                {
-                    "containerPort": 7001,
-                    "protocol": "tcp"
-                },
-                {
-                    "containerPort": 8546,
-                    "protocol": "tcp"
-                },
-                {
-                    "containerPort": 8540,
-                    "protocol": "tcp"
-                },
-                {
-                    "containerPort": 6060,
-                    "protocol": "tcp"
-                }
-            ],
-            "environment": [],
-            "image": "500822580415.dkr.ecr.us-east-2.amazonaws.com/gossamer-kusama",
-            "essential": true,
-            "name": "gossamer-kusama"
-        }
-    ],
-    "placementConstraints": [
-        {
-            "type": "memberOf",
-            "expression": "attribute:ecs.availability-zone==us-east-2a"
-        }
-    ],
-    "memory": "12288",
-    "family": "gossamer-kusama",
-    "networkMode": "host",
-    "requiresCompatibilities": [
-        "EC2"
-    ],
-    "cpu": "4096"
-}
\ No newline at end of file
diff --git a/.github/workflows/staging/openmetrics.d/kusama-conf.yaml b/.github/workflows/staging/openmetrics.d/kusama-conf.yaml
deleted file mode 100644
index 5b2d2f8b85..0000000000
--- a/.github/workflows/staging/openmetrics.d/kusama-conf.yaml
+++ /dev/null
@@ -1,486 +0,0 @@
-## All options defined here are available to all instances.
-#
-init_config:
-
-    ## @param proxy - mapping - optional
-    ## Set HTTP or HTTPS proxies for all instances. Use the `no_proxy` list
-    ## to specify hosts that must bypass proxies.
-    ##
-    ## The SOCKS protocol is also supported like so:
-    ##
-    ##   socks5://user:pass@host:port
-    ##
-    ## Using the scheme `socks5` causes the DNS resolution to happen on the
-    ## client, rather than on the proxy server. This is in line with `curl`,
-    ## which uses the scheme to decide whether to do the DNS resolution on
-    ## the client or proxy. If you want to resolve the domains on the proxy
-    ## server, use `socks5h` as the scheme.
-    #
-    # proxy:
-    #   http: http://<PROXY_SERVER_FOR_HTTP>:<PORT>
-    #   https: https://<PROXY_SERVER_FOR_HTTPS>:<PORT>
-    #   no_proxy:
-    #   - <HOSTNAME_1>
-    #   - <HOSTNAME_2>
-
-    ## @param skip_proxy - boolean - optional - default: false
-    ## If set to `true`, this makes the check bypass any proxy
-    ## settings enabled and attempt to reach services directly.
-    #
-    # skip_proxy: false
-
-    ## @param timeout - number - optional - default: 10
-    ## The timeout for connecting to services.
-    #
-    # timeout: 10
-
-    ## @param service - string - optional
-    ## Attach the tag `service:<SERVICE>` to every metric, event, and service check emitted by this integration.
-    ##
-    ## Additionally, this sets the default `service` for every log source.
-    #
-    # service: <SERVICE>
-
-## Every instance is scheduled independent of the others.
-#
-instances:
-
-    ## @param prometheus_url - string - required
-    ## The URL where your application metrics are exposed by Prometheus.
-    #
-  - prometheus_url: http://127.0.0.1:9876/metrics
-
-    ## @param namespace - string - required
-    ## The namespace to be prepended to all metrics.
-    #
-    namespace: gossamer.staging.kusama
-
-    ## @param metrics - (list of string or mapping) - required
-    ## List of metrics to be fetched from the prometheus endpoint, if there's a
-    ## value it'll be renamed. This list should contain at least one metric.
-    #
-    metrics:
-      - gossamer_*
-      - go_*
-
-    ## @param prometheus_metrics_prefix - string - optional
-    ## Removes a given <PREFIX> from exposed Prometheus metrics.
-    #
-    # prometheus_metrics_prefix: <PREFIX>_
-
-    ## @param health_service_check - boolean - optional - default: true
-    ## Send a service check reporting about the health of the Prometheus endpoint.
-    ## The service check is named <NAMESPACE>.prometheus.health
-    #
-    # health_service_check: true
-
-    ## @param label_to_hostname - string - optional
-    ## Override the hostname with the value of one label.
-    #
-    # label_to_hostname: <LABEL>
-
-    ## @param label_joins - mapping - optional
-    ## Allows targeting a metric to retrieve its label with a 1:1 mapping.
-    #
-    # label_joins:
-    #   target_metric:
-    #     label_to_match: <MATCHED_LABEL>
-    #     labels_to_get:
-    #     - <EXTRA_LABEL_1>
-    #     - <EXTRA_LABEL_2>
-
-    ## @param labels_mapper - mapping - optional
-    ## The label mapper allows you to rename labels.
-    ## Format is <LABEL_TO_RENAME>: <NEW_LABEL_NAME>
-    #
-    # labels_mapper:
-    #   flavor: origin
-
-    ## @param type_overrides - mapping - optional
-    ## Override a type in the Prometheus payload or type an untyped metric (ignored by default).
-    ## Supported <METRIC_TYPE> are `gauge`, `counter`, `histogram`, and `summary`.
-    ## The "*" wildcard can be used to match multiple metric names.
-    #
-    # type_overrides:
-    #   <METRIC_NAME>: <METRIC_TYPE>
-
-    ## @param send_histograms_buckets - boolean - optional - default: true
-    ## Set send_histograms_buckets to true to send the histograms bucket.
-    #
-    # send_histograms_buckets: true
-
-    ## @param send_distribution_buckets - boolean - optional - default: false
-    ## Set `send_distribution_buckets` to `true` to send histograms as Datadog distribution metrics.
-    ##
-    ## Learn more about distribution metrics: https://docs.datadoghq.com/developers/metrics/distributions/
-    #
-    # send_distribution_buckets: false
-
-    ## @param send_monotonic_counter - boolean - optional - default: true
-    ## Set send_monotonic_counter to true to send counters as monotonic counter.
-    #
-    # send_monotonic_counter: true
-
-    ## @param send_distribution_counts_as_monotonic - boolean - optional - default: false
-    ## If set to true, sends histograms and summary counters as monotonic counters (instead of gauges).
-    #
-    # send_distribution_counts_as_monotonic: false
-
-    ## @param send_distribution_sums_as_monotonic - boolean - optional - default: false
-    ## If set to true, sends histograms and summary sums as monotonic counters (instead of gauges).
-    #
-    # send_distribution_sums_as_monotonic: false
-
-    ## @param exclude_labels - list of strings - optional
-    ## A list of labels to be excluded
-    #
-    # exclude_labels:
-    #   - timestamp
-
-    ## @param bearer_token_auth - boolean - optional - default: false
-    ## If set to true, adds a bearer token authentication header.
-    ## Note: If bearer_token_path is not set, the default path is /var/run/secrets/kubernetes.io/serviceaccount/token.
-    #
-    # bearer_token_auth: false
-
-    ## @param bearer_token_path - string - optional
-    ## The path to a Kubernetes service account bearer token file. Make sure the file exists and is mounted correctly.
-    ## Note: bearer_token_auth should be set to true to enable adding the token to HTTP headers for authentication.
-    #
-    # bearer_token_path: <TOKEN_PATH>
-
-    ## @param ignore_metrics - list of strings - optional
-    ## A list of metrics to ignore, use the "*" wildcard can be used to match multiple metric names.
-    #
-    # ignore_metrics:
-    #   - <IGNORED_METRIC_NAME>
-    #   - <PREFIX_*>
-    #   - <*_SUFFIX>
-    #   - <PREFIX_*_SUFFIX>
-    #   - <*_SUBSTRING_*>
-
-    ## @param ignore_metrics_by_labels - mapping - optional
-    ## A mapping of labels where metrics with matching label key and values are ignored.
-    ## Use the "*" wildcard to match all label values.
-    #
-    # ignore_metrics_by_labels:
-    #   <KEY_1>:
-    #   - <LABEL_1>
-    #   - <LABEL_2>
-    #   <KEY_2>:
-    #   - '*'
-
-    ## @param ignore_tags - list of strings - optional
-    ## A list of regular expressions used to ignore tags added by autodiscovery and entries in the `tags` option.
-    #
-    # ignore_tags:
-    #   - <FULL:TAG>
-    #   - <TAG_PREFIX:.*>
-    #   - <TAG_SUFFIX$>
-
-    ## @param proxy - mapping - optional
-    ## This overrides the `proxy` setting in `init_config`.
-    ##
-    ## Set HTTP or HTTPS proxies for this instance. Use the `no_proxy` list
-    ## to specify hosts that must bypass proxies.
-    ##
-    ## The SOCKS protocol is also supported, for example:
-    ##
-    ##   socks5://user:pass@host:port
-    ##
-    ## Using the scheme `socks5` causes the DNS resolution to happen on the
-    ## client, rather than on the proxy server. This is in line with `curl`,
-    ## which uses the scheme to decide whether to do the DNS resolution on
-    ## the client or proxy. If you want to resolve the domains on the proxy
-    ## server, use `socks5h` as the scheme.
-    #
-    # proxy:
-    #   http: http://<PROXY_SERVER_FOR_HTTP>:<PORT>
-    #   https: https://<PROXY_SERVER_FOR_HTTPS>:<PORT>
-    #   no_proxy:
-    #   - <HOSTNAME_1>
-    #   - <HOSTNAME_2>
-
-    ## @param skip_proxy - boolean - optional - default: false
-    ## This overrides the `skip_proxy` setting in `init_config`.
-    ##
-    ## If set to `true`, this makes the check bypass any proxy
-    ## settings enabled and attempt to reach services directly.
-    #
-    # skip_proxy: false
-
-    ## @param auth_type - string - optional - default: basic
-    ## The type of authentication to use. The available types (and related options) are:
-    ##
-    ##   - basic
-    ##     |__ username
-    ##     |__ password
-    ##     |__ use_legacy_auth_encoding
-    ##   - digest
-    ##     |__ username
-    ##     |__ password
-    ##   - ntlm
-    ##     |__ ntlm_domain
-    ##     |__ password
-    ##   - kerberos
-    ##     |__ kerberos_auth
-    ##     |__ kerberos_cache
-    ##     |__ kerberos_delegate
-    ##     |__ kerberos_force_initiate
-    ##     |__ kerberos_hostname
-    ##     |__ kerberos_keytab
-    ##     |__ kerberos_principal
-    ##   - aws
-    ##     |__ aws_region
-    ##     |__ aws_host
-    ##     |__ aws_service
-    ##
-    ## The `aws` auth type relies on boto3 to automatically gather AWS credentials, for example: from `.aws/credentials`.
-    ## Details: https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html#configuring-credentials
-    #
-    # auth_type: basic
-
-    ## @param use_legacy_auth_encoding - boolean - optional - default: true
-    ## When `auth_type` is set to `basic`, this determines whether to encode as `latin1` rather than `utf-8`.
-    #
-    # use_legacy_auth_encoding: true
-
-    ## @param username - string - optional
-    ## The username to use if services are behind basic or digest auth.
-    #
-    # username: <USERNAME>
-
-    ## @param password - string - optional
-    ## The password to use if services are behind basic or NTLM auth.
-    #
-    # password: <PASSWORD>
-
-    ## @param ntlm_domain - string - optional
-    ## If your services use NTLM authentication, specify
-    ## the domain used in the check. For NTLM Auth, append
-    ## the username to domain, not as the `username` parameter.
-    #
-    # ntlm_domain: <NTLM_DOMAIN>\<USERNAME>
-
-    ## @param kerberos_auth - string - optional - default: disabled
-    ## If your services use Kerberos authentication, you can specify the Kerberos
-    ## strategy to use between:
-    ##
-    ##   - required
-    ##   - optional
-    ##   - disabled
-    ##
-    ## See https://github.com/requests/requests-kerberos#mutual-authentication
-    #
-    # kerberos_auth: disabled
-
-    ## @param kerberos_cache - string - optional
-    ## Sets the KRB5CCNAME environment variable.
-    ## It should point to a credential cache with a valid TGT.
-    #
-    # kerberos_cache: <KERBEROS_CACHE>
-
-    ## @param kerberos_delegate - boolean - optional - default: false
-    ## Set to `true` to enable Kerberos delegation of credentials to a server that requests delegation.
-    ##
-    ## See https://github.com/requests/requests-kerberos#delegation
-    #
-    # kerberos_delegate: false
-
-    ## @param kerberos_force_initiate - boolean - optional - default: false
-    ## Set to `true` to preemptively initiate the Kerberos GSS exchange and
-    ## present a Kerberos ticket on the initial request (and all subsequent).
-    ##
-    ## See https://github.com/requests/requests-kerberos#preemptive-authentication
-    #
-    # kerberos_force_initiate: false
-
-    ## @param kerberos_hostname - string - optional
-    ## Override the hostname used for the Kerberos GSS exchange if its DNS name doesn't
-    ## match its Kerberos hostname, for example: behind a content switch or load balancer.
-    ##
-    ## See https://github.com/requests/requests-kerberos#hostname-override
-    #
-    # kerberos_hostname: <KERBEROS_HOSTNAME>
-
-    ## @param kerberos_principal - string - optional
-    ## Set an explicit principal, to force Kerberos to look for a
-    ## matching credential cache for the named user.
-    ##
-    ## See https://github.com/requests/requests-kerberos#explicit-principal
-    #
-    # kerberos_principal: <KERBEROS_PRINCIPAL>
-
-    ## @param kerberos_keytab - string - optional
-    ## Set the path to your Kerberos key tab file.
-    #
-    # kerberos_keytab: <KEYTAB_FILE_PATH>
-
-    ## @param auth_token - mapping - optional
-    ## This allows for the use of authentication information from dynamic sources.
-    ## Both a reader and writer must be configured.
-    ##
-    ## The available readers are:
-    ##
-    ##   - type: file
-    ##     path (required): The absolute path for the file to read from.
-    ##     pattern: A regular expression pattern with a single capture group used to find the
-    ##              token rather than using the entire file, for example: Your secret is (.+)
-    ##
-    ## The available writers are:
-    ##
-    ##   - type: header
-    ##     name (required): The name of the field, for example: Authorization
-    ##     value: The template value, for example `Bearer <TOKEN>`. The default is: <TOKEN>
-    ##     placeholder: The substring in `value` to replace by the token, defaults to: <TOKEN>
-    #
-    # auth_token:
-    #   reader:
-    #     type: <READER_TYPE>
-    #     <OPTION_1>: <VALUE_1>
-    #     <OPTION_2>: <VALUE_2>
-    #   writer:
-    #     type: <WRITER_TYPE>
-    #     <OPTION_1>: <VALUE_1>
-    #     <OPTION_2>: <VALUE_2>
-
-    ## @param aws_region - string - optional
-    ## If your services require AWS Signature Version 4 signing, set the region.
-    ##
-    ## See https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html
-    #
-    # aws_region: <AWS_REGION>
-
-    ## @param aws_host - string - optional
-    ## If your services require AWS Signature Version 4 signing, set the host.
-    ##
-    ## Note: This setting is not necessary for official integrations.
-    ##
-    ## See https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html
-    #
-    # aws_host: <AWS_HOST>
-
-    ## @param aws_service - string - optional
-    ## If your services require AWS Signature Version 4 signing, set the service code. For a list
-    ## of available service codes, see https://docs.aws.amazon.com/general/latest/gr/rande.html
-    ##
-    ## Note: This setting is not necessary for official integrations.
-    ##
-    ## See https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html
-    #
-    # aws_service: <AWS_SERVICE>
-
-    ## @param tls_verify - boolean - optional - default: true
-    ## Instructs the check to validate the TLS certificate of services.
-    #
-    # tls_verify: true
-
-    ## @param tls_use_host_header - boolean - optional - default: false
-    ## If a `Host` header is set, this enables its use for SNI (matching against the TLS certificate CN or SAN).
-    #
-    # tls_use_host_header: false
-
-    ## @param tls_ignore_warning - boolean - optional - default: false
-    ## If `tls_verify` is disabled, security warnings are logged by the check.
-    ## Disable those by setting `tls_ignore_warning` to true.
-    ##
-    ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration.
-    ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set
-    ## to true.
-    #
-    # tls_ignore_warning: false
-
-    ## @param tls_cert - string - optional
-    ## The path to a single file in PEM format containing a certificate as well as any
-    ## number of CA certificates needed to establish the certificate's authenticity for
-    ## use when connecting to services. It may also contain an unencrypted private key to use.
-    #
-    # tls_cert: <CERT_PATH>
-
-    ## @param tls_private_key - string - optional
-    ## The unencrypted private key to use for `tls_cert` when connecting to services. This is
-    ## required if `tls_cert` is set and it does not already contain a private key.
-    #
-    # tls_private_key: <PRIVATE_KEY_PATH>
-
-    ## @param tls_ca_cert - string - optional
-    ## The path to a file of concatenated CA certificates in PEM format or a directory
-    ## containing several CA certificates in PEM format. If a directory, the directory
-    ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
-    ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
-    #
-    # tls_ca_cert: <CA_CERT_PATH>
-
-    ## @param headers - mapping - optional
-    ## The headers parameter allows you to send specific headers with every request.
-    ## You can use it for explicitly specifying the host header or adding headers for
-    ## authorization purposes.
-    ##
-    ## This overrides any default headers.
-    #
-    # headers:
-    #   Host: <ALTERNATIVE_HOSTNAME>
-    #   X-Auth-Token: <AUTH_TOKEN>
-
-    ## @param extra_headers - mapping - optional
-    ## Additional headers to send with every request.
-    #
-    # extra_headers:
-    #   Host: <ALTERNATIVE_HOSTNAME>
-    #   X-Auth-Token: <AUTH_TOKEN>
-
-    ## @param timeout - number - optional - default: 10
-    ## The timeout for accessing services.
-    ##
-    ## This overrides the `timeout` setting in `init_config`.
-    #
-    # timeout: 10
-
-    ## @param connect_timeout - number - optional
-    ## The connect timeout for accessing services. Defaults to `timeout`.
-    #
-    # connect_timeout: <CONNECT_TIMEOUT>
-
-    ## @param read_timeout - number - optional
-    ## The read timeout for accessing services. Defaults to `timeout`.
-    #
-    # read_timeout: <READ_TIMEOUT>
-
-    ## @param log_requests - boolean - optional - default: false
-    ## Whether or not to debug log the HTTP(S) requests made, including the method and URL.
-    #
-    # log_requests: false
-
-    ## @param persist_connections - boolean - optional - default: false
-    ## Whether or not to persist cookies and use connection pooling for increased performance.
-    #
-    # persist_connections: false
-
-    ## @param tags - list of strings - optional
-    ## A list of tags to attach to every metric and service check emitted by this instance.
-    ##
-    ## Learn more about tagging at https://docs.datadoghq.com/tagging
-    #
-    # tags:
-    #   - <KEY_1>:<VALUE_1>
-    #   - <KEY_2>:<VALUE_2>
-
-    ## @param service - string - optional
-    ## Attach the tag `service:<SERVICE>` to every metric, event, and service check emitted by this integration.
-    ##
-    ## Overrides any `service` defined in the `init_config` section.
-    #
-    # service: <SERVICE>
-
-    ## @param min_collection_interval - number - optional - default: 15
-    ## This changes the collection interval of the check. For more information, see:
-    ## https://docs.datadoghq.com/developers/write_agent_check/#collection-interval
-    #
-    # min_collection_interval: 15
-
-    ## @param empty_default_hostname - boolean - optional - default: false
-    ## This forces the check to send metrics with no hostname.
-    ##
-    ## This is useful for cluster-level checks.
-    #
-    # empty_default_hostname: false
diff --git a/.github/workflows/staging/openmetrics.d/polkadot-conf.yaml b/.github/workflows/staging/openmetrics.d/polkadot-conf.yaml
deleted file mode 100644
index 27ac44bce0..0000000000
--- a/.github/workflows/staging/openmetrics.d/polkadot-conf.yaml
+++ /dev/null
@@ -1,486 +0,0 @@
-## All options defined here are available to all instances.
-#
-init_config:
-
-    ## @param proxy - mapping - optional
-    ## Set HTTP or HTTPS proxies for all instances. Use the `no_proxy` list
-    ## to specify hosts that must bypass proxies.
-    ##
-    ## The SOCKS protocol is also supported like so:
-    ##
-    ##   socks5://user:pass@host:port
-    ##
-    ## Using the scheme `socks5` causes the DNS resolution to happen on the
-    ## client, rather than on the proxy server. This is in line with `curl`,
-    ## which uses the scheme to decide whether to do the DNS resolution on
-    ## the client or proxy. If you want to resolve the domains on the proxy
-    ## server, use `socks5h` as the scheme.
-    #
-    # proxy:
-    #   http: http://<PROXY_SERVER_FOR_HTTP>:<PORT>
-    #   https: https://<PROXY_SERVER_FOR_HTTPS>:<PORT>
-    #   no_proxy:
-    #   - <HOSTNAME_1>
-    #   - <HOSTNAME_2>
-
-    ## @param skip_proxy - boolean - optional - default: false
-    ## If set to `true`, this makes the check bypass any proxy
-    ## settings enabled and attempt to reach services directly.
-    #
-    # skip_proxy: false
-
-    ## @param timeout - number - optional - default: 10
-    ## The timeout for connecting to services.
-    #
-    # timeout: 10
-
-    ## @param service - string - optional
-    ## Attach the tag `service:<SERVICE>` to every metric, event, and service check emitted by this integration.
-    ##
-    ## Additionally, this sets the default `service` for every log source.
-    #
-    # service: <SERVICE>
-
-## Every instance is scheduled independent of the others.
-#
-instances:
-
-    ## @param prometheus_url - string - required
-    ## The URL where your application metrics are exposed by Prometheus.
-    #
-  - prometheus_url: http://127.0.0.1:9876/metrics
-
-    ## @param namespace - string - required
-    ## The namespace to be prepended to all metrics.
-    #
-    namespace: gossamer.staging.polkadot
-
-    ## @param metrics - (list of string or mapping) - required
-    ## List of metrics to be fetched from the prometheus endpoint, if there's a
-    ## value it'll be renamed. This list should contain at least one metric.
-    #
-    metrics:
-      - gossamer_*
-      - go_*
-
-    ## @param prometheus_metrics_prefix - string - optional
-    ## Removes a given <PREFIX> from exposed Prometheus metrics.
-    #
-    # prometheus_metrics_prefix: <PREFIX>_
-
-    ## @param health_service_check - boolean - optional - default: true
-    ## Send a service check reporting about the health of the Prometheus endpoint.
-    ## The service check is named <NAMESPACE>.prometheus.health
-    #
-    # health_service_check: true
-
-    ## @param label_to_hostname - string - optional
-    ## Override the hostname with the value of one label.
-    #
-    # label_to_hostname: <LABEL>
-
-    ## @param label_joins - mapping - optional
-    ## Allows targeting a metric to retrieve its label with a 1:1 mapping.
-    #
-    # label_joins:
-    #   target_metric:
-    #     label_to_match: <MATCHED_LABEL>
-    #     labels_to_get:
-    #     - <EXTRA_LABEL_1>
-    #     - <EXTRA_LABEL_2>
-
-    ## @param labels_mapper - mapping - optional
-    ## The label mapper allows you to rename labels.
-    ## Format is <LABEL_TO_RENAME>: <NEW_LABEL_NAME>
-    #
-    # labels_mapper:
-    #   flavor: origin
-
-    ## @param type_overrides - mapping - optional
-    ## Override a type in the Prometheus payload or type an untyped metric (ignored by default).
-    ## Supported <METRIC_TYPE> are `gauge`, `counter`, `histogram`, and `summary`.
-    ## The "*" wildcard can be used to match multiple metric names.
-    #
-    # type_overrides:
-    #   <METRIC_NAME>: <METRIC_TYPE>
-
-    ## @param send_histograms_buckets - boolean - optional - default: true
-    ## Set send_histograms_buckets to true to send the histograms bucket.
-    #
-    # send_histograms_buckets: true
-
-    ## @param send_distribution_buckets - boolean - optional - default: false
-    ## Set `send_distribution_buckets` to `true` to send histograms as Datadog distribution metrics.
-    ##
-    ## Learn more about distribution metrics: https://docs.datadoghq.com/developers/metrics/distributions/
-    #
-    # send_distribution_buckets: false
-
-    ## @param send_monotonic_counter - boolean - optional - default: true
-    ## Set send_monotonic_counter to true to send counters as monotonic counter.
-    #
-    # send_monotonic_counter: true
-
-    ## @param send_distribution_counts_as_monotonic - boolean - optional - default: false
-    ## If set to true, sends histograms and summary counters as monotonic counters (instead of gauges).
-    #
-    # send_distribution_counts_as_monotonic: false
-
-    ## @param send_distribution_sums_as_monotonic - boolean - optional - default: false
-    ## If set to true, sends histograms and summary sums as monotonic counters (instead of gauges).
-    #
-    # send_distribution_sums_as_monotonic: false
-
-    ## @param exclude_labels - list of strings - optional
-    ## A list of labels to be excluded
-    #
-    # exclude_labels:
-    #   - timestamp
-
-    ## @param bearer_token_auth - boolean - optional - default: false
-    ## If set to true, adds a bearer token authentication header.
-    ## Note: If bearer_token_path is not set, the default path is /var/run/secrets/kubernetes.io/serviceaccount/token.
-    #
-    # bearer_token_auth: false
-
-    ## @param bearer_token_path - string - optional
-    ## The path to a Kubernetes service account bearer token file. Make sure the file exists and is mounted correctly.
-    ## Note: bearer_token_auth should be set to true to enable adding the token to HTTP headers for authentication.
-    #
-    # bearer_token_path: <TOKEN_PATH>
-
-    ## @param ignore_metrics - list of strings - optional
-    ## A list of metrics to ignore, use the "*" wildcard can be used to match multiple metric names.
-    #
-    # ignore_metrics:
-    #   - <IGNORED_METRIC_NAME>
-    #   - <PREFIX_*>
-    #   - <*_SUFFIX>
-    #   - <PREFIX_*_SUFFIX>
-    #   - <*_SUBSTRING_*>
-
-    ## @param ignore_metrics_by_labels - mapping - optional
-    ## A mapping of labels where metrics with matching label key and values are ignored.
-    ## Use the "*" wildcard to match all label values.
-    #
-    # ignore_metrics_by_labels:
-    #   <KEY_1>:
-    #   - <LABEL_1>
-    #   - <LABEL_2>
-    #   <KEY_2>:
-    #   - '*'
-
-    ## @param ignore_tags - list of strings - optional
-    ## A list of regular expressions used to ignore tags added by autodiscovery and entries in the `tags` option.
-    #
-    # ignore_tags:
-    #   - <FULL:TAG>
-    #   - <TAG_PREFIX:.*>
-    #   - <TAG_SUFFIX$>
-
-    ## @param proxy - mapping - optional
-    ## This overrides the `proxy` setting in `init_config`.
-    ##
-    ## Set HTTP or HTTPS proxies for this instance. Use the `no_proxy` list
-    ## to specify hosts that must bypass proxies.
-    ##
-    ## The SOCKS protocol is also supported, for example:
-    ##
-    ##   socks5://user:pass@host:port
-    ##
-    ## Using the scheme `socks5` causes the DNS resolution to happen on the
-    ## client, rather than on the proxy server. This is in line with `curl`,
-    ## which uses the scheme to decide whether to do the DNS resolution on
-    ## the client or proxy. If you want to resolve the domains on the proxy
-    ## server, use `socks5h` as the scheme.
-    #
-    # proxy:
-    #   http: http://<PROXY_SERVER_FOR_HTTP>:<PORT>
-    #   https: https://<PROXY_SERVER_FOR_HTTPS>:<PORT>
-    #   no_proxy:
-    #   - <HOSTNAME_1>
-    #   - <HOSTNAME_2>
-
-    ## @param skip_proxy - boolean - optional - default: false
-    ## This overrides the `skip_proxy` setting in `init_config`.
-    ##
-    ## If set to `true`, this makes the check bypass any proxy
-    ## settings enabled and attempt to reach services directly.
-    #
-    # skip_proxy: false
-
-    ## @param auth_type - string - optional - default: basic
-    ## The type of authentication to use. The available types (and related options) are:
-    ##
-    ##   - basic
-    ##     |__ username
-    ##     |__ password
-    ##     |__ use_legacy_auth_encoding
-    ##   - digest
-    ##     |__ username
-    ##     |__ password
-    ##   - ntlm
-    ##     |__ ntlm_domain
-    ##     |__ password
-    ##   - kerberos
-    ##     |__ kerberos_auth
-    ##     |__ kerberos_cache
-    ##     |__ kerberos_delegate
-    ##     |__ kerberos_force_initiate
-    ##     |__ kerberos_hostname
-    ##     |__ kerberos_keytab
-    ##     |__ kerberos_principal
-    ##   - aws
-    ##     |__ aws_region
-    ##     |__ aws_host
-    ##     |__ aws_service
-    ##
-    ## The `aws` auth type relies on boto3 to automatically gather AWS credentials, for example: from `.aws/credentials`.
-    ## Details: https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html#configuring-credentials
-    #
-    # auth_type: basic
-
-    ## @param use_legacy_auth_encoding - boolean - optional - default: true
-    ## When `auth_type` is set to `basic`, this determines whether to encode as `latin1` rather than `utf-8`.
-    #
-    # use_legacy_auth_encoding: true
-
-    ## @param username - string - optional
-    ## The username to use if services are behind basic or digest auth.
-    #
-    # username: <USERNAME>
-
-    ## @param password - string - optional
-    ## The password to use if services are behind basic or NTLM auth.
-    #
-    # password: <PASSWORD>
-
-    ## @param ntlm_domain - string - optional
-    ## If your services use NTLM authentication, specify
-    ## the domain used in the check. For NTLM Auth, append
-    ## the username to domain, not as the `username` parameter.
-    #
-    # ntlm_domain: <NTLM_DOMAIN>\<USERNAME>
-
-    ## @param kerberos_auth - string - optional - default: disabled
-    ## If your services use Kerberos authentication, you can specify the Kerberos
-    ## strategy to use between:
-    ##
-    ##   - required
-    ##   - optional
-    ##   - disabled
-    ##
-    ## See https://github.com/requests/requests-kerberos#mutual-authentication
-    #
-    # kerberos_auth: disabled
-
-    ## @param kerberos_cache - string - optional
-    ## Sets the KRB5CCNAME environment variable.
-    ## It should point to a credential cache with a valid TGT.
-    #
-    # kerberos_cache: <KERBEROS_CACHE>
-
-    ## @param kerberos_delegate - boolean - optional - default: false
-    ## Set to `true` to enable Kerberos delegation of credentials to a server that requests delegation.
-    ##
-    ## See https://github.com/requests/requests-kerberos#delegation
-    #
-    # kerberos_delegate: false
-
-    ## @param kerberos_force_initiate - boolean - optional - default: false
-    ## Set to `true` to preemptively initiate the Kerberos GSS exchange and
-    ## present a Kerberos ticket on the initial request (and all subsequent).
-    ##
-    ## See https://github.com/requests/requests-kerberos#preemptive-authentication
-    #
-    # kerberos_force_initiate: false
-
-    ## @param kerberos_hostname - string - optional
-    ## Override the hostname used for the Kerberos GSS exchange if its DNS name doesn't
-    ## match its Kerberos hostname, for example: behind a content switch or load balancer.
-    ##
-    ## See https://github.com/requests/requests-kerberos#hostname-override
-    #
-    # kerberos_hostname: <KERBEROS_HOSTNAME>
-
-    ## @param kerberos_principal - string - optional
-    ## Set an explicit principal, to force Kerberos to look for a
-    ## matching credential cache for the named user.
-    ##
-    ## See https://github.com/requests/requests-kerberos#explicit-principal
-    #
-    # kerberos_principal: <KERBEROS_PRINCIPAL>
-
-    ## @param kerberos_keytab - string - optional
-    ## Set the path to your Kerberos key tab file.
-    #
-    # kerberos_keytab: <KEYTAB_FILE_PATH>
-
-    ## @param auth_token - mapping - optional
-    ## This allows for the use of authentication information from dynamic sources.
-    ## Both a reader and writer must be configured.
-    ##
-    ## The available readers are:
-    ##
-    ##   - type: file
-    ##     path (required): The absolute path for the file to read from.
-    ##     pattern: A regular expression pattern with a single capture group used to find the
-    ##              token rather than using the entire file, for example: Your secret is (.+)
-    ##
-    ## The available writers are:
-    ##
-    ##   - type: header
-    ##     name (required): The name of the field, for example: Authorization
-    ##     value: The template value, for example `Bearer <TOKEN>`. The default is: <TOKEN>
-    ##     placeholder: The substring in `value` to replace by the token, defaults to: <TOKEN>
-    #
-    # auth_token:
-    #   reader:
-    #     type: <READER_TYPE>
-    #     <OPTION_1>: <VALUE_1>
-    #     <OPTION_2>: <VALUE_2>
-    #   writer:
-    #     type: <WRITER_TYPE>
-    #     <OPTION_1>: <VALUE_1>
-    #     <OPTION_2>: <VALUE_2>
-
-    ## @param aws_region - string - optional
-    ## If your services require AWS Signature Version 4 signing, set the region.
-    ##
-    ## See https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html
-    #
-    # aws_region: <AWS_REGION>
-
-    ## @param aws_host - string - optional
-    ## If your services require AWS Signature Version 4 signing, set the host.
-    ##
-    ## Note: This setting is not necessary for official integrations.
-    ##
-    ## See https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html
-    #
-    # aws_host: <AWS_HOST>
-
-    ## @param aws_service - string - optional
-    ## If your services require AWS Signature Version 4 signing, set the service code. For a list
-    ## of available service codes, see https://docs.aws.amazon.com/general/latest/gr/rande.html
-    ##
-    ## Note: This setting is not necessary for official integrations.
-    ##
-    ## See https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html
-    #
-    # aws_service: <AWS_SERVICE>
-
-    ## @param tls_verify - boolean - optional - default: true
-    ## Instructs the check to validate the TLS certificate of services.
-    #
-    # tls_verify: true
-
-    ## @param tls_use_host_header - boolean - optional - default: false
-    ## If a `Host` header is set, this enables its use for SNI (matching against the TLS certificate CN or SAN).
-    #
-    # tls_use_host_header: false
-
-    ## @param tls_ignore_warning - boolean - optional - default: false
-    ## If `tls_verify` is disabled, security warnings are logged by the check.
-    ## Disable those by setting `tls_ignore_warning` to true.
-    ##
-    ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration.
-    ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set
-    ## to true.
-    #
-    # tls_ignore_warning: false
-
-    ## @param tls_cert - string - optional
-    ## The path to a single file in PEM format containing a certificate as well as any
-    ## number of CA certificates needed to establish the certificate's authenticity for
-    ## use when connecting to services. It may also contain an unencrypted private key to use.
-    #
-    # tls_cert: <CERT_PATH>
-
-    ## @param tls_private_key - string - optional
-    ## The unencrypted private key to use for `tls_cert` when connecting to services. This is
-    ## required if `tls_cert` is set and it does not already contain a private key.
-    #
-    # tls_private_key: <PRIVATE_KEY_PATH>
-
-    ## @param tls_ca_cert - string - optional
-    ## The path to a file of concatenated CA certificates in PEM format or a directory
-    ## containing several CA certificates in PEM format. If a directory, the directory
-    ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
-    ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
-    #
-    # tls_ca_cert: <CA_CERT_PATH>
-
-    ## @param headers - mapping - optional
-    ## The headers parameter allows you to send specific headers with every request.
-    ## You can use it for explicitly specifying the host header or adding headers for
-    ## authorization purposes.
-    ##
-    ## This overrides any default headers.
-    #
-    # headers:
-    #   Host: <ALTERNATIVE_HOSTNAME>
-    #   X-Auth-Token: <AUTH_TOKEN>
-
-    ## @param extra_headers - mapping - optional
-    ## Additional headers to send with every request.
-    #
-    # extra_headers:
-    #   Host: <ALTERNATIVE_HOSTNAME>
-    #   X-Auth-Token: <AUTH_TOKEN>
-
-    ## @param timeout - number - optional - default: 10
-    ## The timeout for accessing services.
-    ##
-    ## This overrides the `timeout` setting in `init_config`.
-    #
-    # timeout: 10
-
-    ## @param connect_timeout - number - optional
-    ## The connect timeout for accessing services. Defaults to `timeout`.
-    #
-    # connect_timeout: <CONNECT_TIMEOUT>
-
-    ## @param read_timeout - number - optional
-    ## The read timeout for accessing services. Defaults to `timeout`.
-    #
-    # read_timeout: <READ_TIMEOUT>
-
-    ## @param log_requests - boolean - optional - default: false
-    ## Whether or not to debug log the HTTP(S) requests made, including the method and URL.
-    #
-    # log_requests: false
-
-    ## @param persist_connections - boolean - optional - default: false
-    ## Whether or not to persist cookies and use connection pooling for increased performance.
-    #
-    # persist_connections: false
-
-    ## @param tags - list of strings - optional
-    ## A list of tags to attach to every metric and service check emitted by this instance.
-    ##
-    ## Learn more about tagging at https://docs.datadoghq.com/tagging
-    #
-    # tags:
-    #   - <KEY_1>:<VALUE_1>
-    #   - <KEY_2>:<VALUE_2>
-
-    ## @param service - string - optional
-    ## Attach the tag `service:<SERVICE>` to every metric, event, and service check emitted by this integration.
-    ##
-    ## Overrides any `service` defined in the `init_config` section.
-    #
-    # service: <SERVICE>
-
-    ## @param min_collection_interval - number - optional - default: 15
-    ## This changes the collection interval of the check. For more information, see:
-    ## https://docs.datadoghq.com/developers/write_agent_check/#collection-interval
-    #
-    # min_collection_interval: 15
-
-    ## @param empty_default_hostname - boolean - optional - default: false
-    ## This forces the check to send metrics with no hostname.
-    ##
-    ## This is useful for cluster-level checks.
-    #
-    # empty_default_hostname: false
diff --git a/.github/workflows/staging/openmetrics.d/westend-conf.yaml b/.github/workflows/staging/openmetrics.d/westend-conf.yaml
deleted file mode 100644
index cc6543c9f5..0000000000
--- a/.github/workflows/staging/openmetrics.d/westend-conf.yaml
+++ /dev/null
@@ -1,486 +0,0 @@
-## All options defined here are available to all instances.
-#
-init_config:
-
-    ## @param proxy - mapping - optional
-    ## Set HTTP or HTTPS proxies for all instances. Use the `no_proxy` list
-    ## to specify hosts that must bypass proxies.
-    ##
-    ## The SOCKS protocol is also supported like so:
-    ##
-    ##   socks5://user:pass@host:port
-    ##
-    ## Using the scheme `socks5` causes the DNS resolution to happen on the
-    ## client, rather than on the proxy server. This is in line with `curl`,
-    ## which uses the scheme to decide whether to do the DNS resolution on
-    ## the client or proxy. If you want to resolve the domains on the proxy
-    ## server, use `socks5h` as the scheme.
-    #
-    # proxy:
-    #   http: http://<PROXY_SERVER_FOR_HTTP>:<PORT>
-    #   https: https://<PROXY_SERVER_FOR_HTTPS>:<PORT>
-    #   no_proxy:
-    #   - <HOSTNAME_1>
-    #   - <HOSTNAME_2>
-
-    ## @param skip_proxy - boolean - optional - default: false
-    ## If set to `true`, this makes the check bypass any proxy
-    ## settings enabled and attempt to reach services directly.
-    #
-    # skip_proxy: false
-
-    ## @param timeout - number - optional - default: 10
-    ## The timeout for connecting to services.
-    #
-    # timeout: 10
-
-    ## @param service - string - optional
-    ## Attach the tag `service:<SERVICE>` to every metric, event, and service check emitted by this integration.
-    ##
-    ## Additionally, this sets the default `service` for every log source.
-    #
-    # service: <SERVICE>
-
-## Every instance is scheduled independent of the others.
-#
-instances:
-
-    ## @param prometheus_url - string - required
-    ## The URL where your application metrics are exposed by Prometheus.
-    #
-  - prometheus_url: http://127.0.0.1:9876/metrics
-
-    ## @param namespace - string - required
-    ## The namespace to be prepended to all metrics.
-    #
-    namespace: gossamer.staging.westend
-
-    ## @param metrics - (list of string or mapping) - required
-    ## List of metrics to be fetched from the prometheus endpoint, if there's a
-    ## value it'll be renamed. This list should contain at least one metric.
-    #
-    metrics:
-      - gossamer_*
-      - go_*
-
-    ## @param prometheus_metrics_prefix - string - optional
-    ## Removes a given <PREFIX> from exposed Prometheus metrics.
-    #
-    # prometheus_metrics_prefix: <PREFIX>_
-
-    ## @param health_service_check - boolean - optional - default: true
-    ## Send a service check reporting about the health of the Prometheus endpoint.
-    ## The service check is named <NAMESPACE>.prometheus.health
-    #
-    # health_service_check: true
-
-    ## @param label_to_hostname - string - optional
-    ## Override the hostname with the value of one label.
-    #
-    # label_to_hostname: <LABEL>
-
-    ## @param label_joins - mapping - optional
-    ## Allows targeting a metric to retrieve its label with a 1:1 mapping.
-    #
-    # label_joins:
-    #   target_metric:
-    #     label_to_match: <MATCHED_LABEL>
-    #     labels_to_get:
-    #     - <EXTRA_LABEL_1>
-    #     - <EXTRA_LABEL_2>
-
-    ## @param labels_mapper - mapping - optional
-    ## The label mapper allows you to rename labels.
-    ## Format is <LABEL_TO_RENAME>: <NEW_LABEL_NAME>
-    #
-    # labels_mapper:
-    #   flavor: origin
-
-    ## @param type_overrides - mapping - optional
-    ## Override a type in the Prometheus payload or type an untyped metric (ignored by default).
-    ## Supported <METRIC_TYPE> are `gauge`, `counter`, `histogram`, and `summary`.
-    ## The "*" wildcard can be used to match multiple metric names.
-    #
-    # type_overrides:
-    #   <METRIC_NAME>: <METRIC_TYPE>
-
-    ## @param send_histograms_buckets - boolean - optional - default: true
-    ## Set send_histograms_buckets to true to send the histograms bucket.
-    #
-    # send_histograms_buckets: true
-
-    ## @param send_distribution_buckets - boolean - optional - default: false
-    ## Set `send_distribution_buckets` to `true` to send histograms as Datadog distribution metrics.
-    ##
-    ## Learn more about distribution metrics: https://docs.datadoghq.com/developers/metrics/distributions/
-    #
-    # send_distribution_buckets: false
-
-    ## @param send_monotonic_counter - boolean - optional - default: true
-    ## Set send_monotonic_counter to true to send counters as monotonic counter.
-    #
-    # send_monotonic_counter: true
-
-    ## @param send_distribution_counts_as_monotonic - boolean - optional - default: false
-    ## If set to true, sends histograms and summary counters as monotonic counters (instead of gauges).
-    #
-    # send_distribution_counts_as_monotonic: false
-
-    ## @param send_distribution_sums_as_monotonic - boolean - optional - default: false
-    ## If set to true, sends histograms and summary sums as monotonic counters (instead of gauges).
-    #
-    # send_distribution_sums_as_monotonic: false
-
-    ## @param exclude_labels - list of strings - optional
-    ## A list of labels to be excluded
-    #
-    # exclude_labels:
-    #   - timestamp
-
-    ## @param bearer_token_auth - boolean - optional - default: false
-    ## If set to true, adds a bearer token authentication header.
-    ## Note: If bearer_token_path is not set, the default path is /var/run/secrets/kubernetes.io/serviceaccount/token.
-    #
-    # bearer_token_auth: false
-
-    ## @param bearer_token_path - string - optional
-    ## The path to a Kubernetes service account bearer token file. Make sure the file exists and is mounted correctly.
-    ## Note: bearer_token_auth should be set to true to enable adding the token to HTTP headers for authentication.
-    #
-    # bearer_token_path: <TOKEN_PATH>
-
-    ## @param ignore_metrics - list of strings - optional
-    ## A list of metrics to ignore, use the "*" wildcard can be used to match multiple metric names.
-    #
-    # ignore_metrics:
-    #   - <IGNORED_METRIC_NAME>
-    #   - <PREFIX_*>
-    #   - <*_SUFFIX>
-    #   - <PREFIX_*_SUFFIX>
-    #   - <*_SUBSTRING_*>
-
-    ## @param ignore_metrics_by_labels - mapping - optional
-    ## A mapping of labels where metrics with matching label key and values are ignored.
-    ## Use the "*" wildcard to match all label values.
-    #
-    # ignore_metrics_by_labels:
-    #   <KEY_1>:
-    #   - <LABEL_1>
-    #   - <LABEL_2>
-    #   <KEY_2>:
-    #   - '*'
-
-    ## @param ignore_tags - list of strings - optional
-    ## A list of regular expressions used to ignore tags added by autodiscovery and entries in the `tags` option.
-    #
-    # ignore_tags:
-    #   - <FULL:TAG>
-    #   - <TAG_PREFIX:.*>
-    #   - <TAG_SUFFIX$>
-
-    ## @param proxy - mapping - optional
-    ## This overrides the `proxy` setting in `init_config`.
-    ##
-    ## Set HTTP or HTTPS proxies for this instance. Use the `no_proxy` list
-    ## to specify hosts that must bypass proxies.
-    ##
-    ## The SOCKS protocol is also supported, for example:
-    ##
-    ##   socks5://user:pass@host:port
-    ##
-    ## Using the scheme `socks5` causes the DNS resolution to happen on the
-    ## client, rather than on the proxy server. This is in line with `curl`,
-    ## which uses the scheme to decide whether to do the DNS resolution on
-    ## the client or proxy. If you want to resolve the domains on the proxy
-    ## server, use `socks5h` as the scheme.
-    #
-    # proxy:
-    #   http: http://<PROXY_SERVER_FOR_HTTP>:<PORT>
-    #   https: https://<PROXY_SERVER_FOR_HTTPS>:<PORT>
-    #   no_proxy:
-    #   - <HOSTNAME_1>
-    #   - <HOSTNAME_2>
-
-    ## @param skip_proxy - boolean - optional - default: false
-    ## This overrides the `skip_proxy` setting in `init_config`.
-    ##
-    ## If set to `true`, this makes the check bypass any proxy
-    ## settings enabled and attempt to reach services directly.
-    #
-    # skip_proxy: false
-
-    ## @param auth_type - string - optional - default: basic
-    ## The type of authentication to use. The available types (and related options) are:
-    ##
-    ##   - basic
-    ##     |__ username
-    ##     |__ password
-    ##     |__ use_legacy_auth_encoding
-    ##   - digest
-    ##     |__ username
-    ##     |__ password
-    ##   - ntlm
-    ##     |__ ntlm_domain
-    ##     |__ password
-    ##   - kerberos
-    ##     |__ kerberos_auth
-    ##     |__ kerberos_cache
-    ##     |__ kerberos_delegate
-    ##     |__ kerberos_force_initiate
-    ##     |__ kerberos_hostname
-    ##     |__ kerberos_keytab
-    ##     |__ kerberos_principal
-    ##   - aws
-    ##     |__ aws_region
-    ##     |__ aws_host
-    ##     |__ aws_service
-    ##
-    ## The `aws` auth type relies on boto3 to automatically gather AWS credentials, for example: from `.aws/credentials`.
-    ## Details: https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html#configuring-credentials
-    #
-    # auth_type: basic
-
-    ## @param use_legacy_auth_encoding - boolean - optional - default: true
-    ## When `auth_type` is set to `basic`, this determines whether to encode as `latin1` rather than `utf-8`.
-    #
-    # use_legacy_auth_encoding: true
-
-    ## @param username - string - optional
-    ## The username to use if services are behind basic or digest auth.
-    #
-    # username: <USERNAME>
-
-    ## @param password - string - optional
-    ## The password to use if services are behind basic or NTLM auth.
-    #
-    # password: <PASSWORD>
-
-    ## @param ntlm_domain - string - optional
-    ## If your services use NTLM authentication, specify
-    ## the domain used in the check. For NTLM Auth, append
-    ## the username to domain, not as the `username` parameter.
-    #
-    # ntlm_domain: <NTLM_DOMAIN>\<USERNAME>
-
-    ## @param kerberos_auth - string - optional - default: disabled
-    ## If your services use Kerberos authentication, you can specify the Kerberos
-    ## strategy to use between:
-    ##
-    ##   - required
-    ##   - optional
-    ##   - disabled
-    ##
-    ## See https://github.com/requests/requests-kerberos#mutual-authentication
-    #
-    # kerberos_auth: disabled
-
-    ## @param kerberos_cache - string - optional
-    ## Sets the KRB5CCNAME environment variable.
-    ## It should point to a credential cache with a valid TGT.
-    #
-    # kerberos_cache: <KERBEROS_CACHE>
-
-    ## @param kerberos_delegate - boolean - optional - default: false
-    ## Set to `true` to enable Kerberos delegation of credentials to a server that requests delegation.
-    ##
-    ## See https://github.com/requests/requests-kerberos#delegation
-    #
-    # kerberos_delegate: false
-
-    ## @param kerberos_force_initiate - boolean - optional - default: false
-    ## Set to `true` to preemptively initiate the Kerberos GSS exchange and
-    ## present a Kerberos ticket on the initial request (and all subsequent).
-    ##
-    ## See https://github.com/requests/requests-kerberos#preemptive-authentication
-    #
-    # kerberos_force_initiate: false
-
-    ## @param kerberos_hostname - string - optional
-    ## Override the hostname used for the Kerberos GSS exchange if its DNS name doesn't
-    ## match its Kerberos hostname, for example: behind a content switch or load balancer.
-    ##
-    ## See https://github.com/requests/requests-kerberos#hostname-override
-    #
-    # kerberos_hostname: <KERBEROS_HOSTNAME>
-
-    ## @param kerberos_principal - string - optional
-    ## Set an explicit principal, to force Kerberos to look for a
-    ## matching credential cache for the named user.
-    ##
-    ## See https://github.com/requests/requests-kerberos#explicit-principal
-    #
-    # kerberos_principal: <KERBEROS_PRINCIPAL>
-
-    ## @param kerberos_keytab - string - optional
-    ## Set the path to your Kerberos key tab file.
-    #
-    # kerberos_keytab: <KEYTAB_FILE_PATH>
-
-    ## @param auth_token - mapping - optional
-    ## This allows for the use of authentication information from dynamic sources.
-    ## Both a reader and writer must be configured.
-    ##
-    ## The available readers are:
-    ##
-    ##   - type: file
-    ##     path (required): The absolute path for the file to read from.
-    ##     pattern: A regular expression pattern with a single capture group used to find the
-    ##              token rather than using the entire file, for example: Your secret is (.+)
-    ##
-    ## The available writers are:
-    ##
-    ##   - type: header
-    ##     name (required): The name of the field, for example: Authorization
-    ##     value: The template value, for example `Bearer <TOKEN>`. The default is: <TOKEN>
-    ##     placeholder: The substring in `value` to replace by the token, defaults to: <TOKEN>
-    #
-    # auth_token:
-    #   reader:
-    #     type: <READER_TYPE>
-    #     <OPTION_1>: <VALUE_1>
-    #     <OPTION_2>: <VALUE_2>
-    #   writer:
-    #     type: <WRITER_TYPE>
-    #     <OPTION_1>: <VALUE_1>
-    #     <OPTION_2>: <VALUE_2>
-
-    ## @param aws_region - string - optional
-    ## If your services require AWS Signature Version 4 signing, set the region.
-    ##
-    ## See https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html
-    #
-    # aws_region: <AWS_REGION>
-
-    ## @param aws_host - string - optional
-    ## If your services require AWS Signature Version 4 signing, set the host.
-    ##
-    ## Note: This setting is not necessary for official integrations.
-    ##
-    ## See https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html
-    #
-    # aws_host: <AWS_HOST>
-
-    ## @param aws_service - string - optional
-    ## If your services require AWS Signature Version 4 signing, set the service code. For a list
-    ## of available service codes, see https://docs.aws.amazon.com/general/latest/gr/rande.html
-    ##
-    ## Note: This setting is not necessary for official integrations.
-    ##
-    ## See https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html
-    #
-    # aws_service: <AWS_SERVICE>
-
-    ## @param tls_verify - boolean - optional - default: true
-    ## Instructs the check to validate the TLS certificate of services.
-    #
-    # tls_verify: true
-
-    ## @param tls_use_host_header - boolean - optional - default: false
-    ## If a `Host` header is set, this enables its use for SNI (matching against the TLS certificate CN or SAN).
-    #
-    # tls_use_host_header: false
-
-    ## @param tls_ignore_warning - boolean - optional - default: false
-    ## If `tls_verify` is disabled, security warnings are logged by the check.
-    ## Disable those by setting `tls_ignore_warning` to true.
-    ##
-    ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration.
-    ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set
-    ## to true.
-    #
-    # tls_ignore_warning: false
-
-    ## @param tls_cert - string - optional
-    ## The path to a single file in PEM format containing a certificate as well as any
-    ## number of CA certificates needed to establish the certificate's authenticity for
-    ## use when connecting to services. It may also contain an unencrypted private key to use.
-    #
-    # tls_cert: <CERT_PATH>
-
-    ## @param tls_private_key - string - optional
-    ## The unencrypted private key to use for `tls_cert` when connecting to services. This is
-    ## required if `tls_cert` is set and it does not already contain a private key.
-    #
-    # tls_private_key: <PRIVATE_KEY_PATH>
-
-    ## @param tls_ca_cert - string - optional
-    ## The path to a file of concatenated CA certificates in PEM format or a directory
-    ## containing several CA certificates in PEM format. If a directory, the directory
-    ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
-    ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
-    #
-    # tls_ca_cert: <CA_CERT_PATH>
-
-    ## @param headers - mapping - optional
-    ## The headers parameter allows you to send specific headers with every request.
-    ## You can use it for explicitly specifying the host header or adding headers for
-    ## authorization purposes.
-    ##
-    ## This overrides any default headers.
-    #
-    # headers:
-    #   Host: <ALTERNATIVE_HOSTNAME>
-    #   X-Auth-Token: <AUTH_TOKEN>
-
-    ## @param extra_headers - mapping - optional
-    ## Additional headers to send with every request.
-    #
-    # extra_headers:
-    #   Host: <ALTERNATIVE_HOSTNAME>
-    #   X-Auth-Token: <AUTH_TOKEN>
-
-    ## @param timeout - number - optional - default: 10
-    ## The timeout for accessing services.
-    ##
-    ## This overrides the `timeout` setting in `init_config`.
-    #
-    # timeout: 10
-
-    ## @param connect_timeout - number - optional
-    ## The connect timeout for accessing services. Defaults to `timeout`.
-    #
-    # connect_timeout: <CONNECT_TIMEOUT>
-
-    ## @param read_timeout - number - optional
-    ## The read timeout for accessing services. Defaults to `timeout`.
-    #
-    # read_timeout: <READ_TIMEOUT>
-
-    ## @param log_requests - boolean - optional - default: false
-    ## Whether or not to debug log the HTTP(S) requests made, including the method and URL.
-    #
-    # log_requests: false
-
-    ## @param persist_connections - boolean - optional - default: false
-    ## Whether or not to persist cookies and use connection pooling for increased performance.
-    #
-    # persist_connections: false
-
-    ## @param tags - list of strings - optional
-    ## A list of tags to attach to every metric and service check emitted by this instance.
-    ##
-    ## Learn more about tagging at https://docs.datadoghq.com/tagging
-    #
-    # tags:
-    #   - <KEY_1>:<VALUE_1>
-    #   - <KEY_2>:<VALUE_2>
-
-    ## @param service - string - optional
-    ## Attach the tag `service:<SERVICE>` to every metric, event, and service check emitted by this integration.
-    ##
-    ## Overrides any `service` defined in the `init_config` section.
-    #
-    # service: <SERVICE>
-
-    ## @param min_collection_interval - number - optional - default: 15
-    ## This changes the collection interval of the check. For more information, see:
-    ## https://docs.datadoghq.com/developers/write_agent_check/#collection-interval
-    #
-    # min_collection_interval: 15
-
-    ## @param empty_default_hostname - boolean - optional - default: false
-    ## This forces the check to send metrics with no hostname.
-    ##
-    ## This is useful for cluster-level checks.
-    #
-    # empty_default_hostname: false
diff --git a/.github/workflows/staging/polkadot-taskdef.json b/.github/workflows/staging/polkadot-taskdef.json
deleted file mode 100644
index 3aeba03b21..0000000000
--- a/.github/workflows/staging/polkadot-taskdef.json
+++ /dev/null
@@ -1,49 +0,0 @@
-{
-    "containerDefinitions": [
-        {
-            "logConfiguration": {
-                "logDriver": "awslogs",
-                "options": {
-                    "awslogs-group": "gossamer-staging-CWLogsGroup-wPH0S1xHYmq7",
-                    "awslogs-region": "us-east-2",
-                    "awslogs-stream-prefix": "ecs"
-                }
-            },
-            "portMappings": [
-                {
-                    "containerPort": 7001,
-                    "protocol": "tcp"
-                },
-                {
-                    "containerPort": 8546,
-                    "protocol": "tcp"
-                },
-                {
-                    "containerPort": 8540,
-                    "protocol": "tcp"
-                },
-                {
-                    "containerPort": 6060,
-                    "protocol": "tcp"
-                }
-            ],
-            "environment": [],
-            "image": "500822580415.dkr.ecr.us-east-2.amazonaws.com/gossamer-polkadot",
-            "essential": true,
-            "name": "gossamer-polkadot"
-        }
-    ],
-    "placementConstraints": [
-        {
-            "type": "memberOf",
-            "expression": "attribute:ecs.availability-zone==us-east-2a"
-        }
-    ],
-    "memory": "12288",
-    "family": "gossamer-polkadot",
-    "networkMode": "host",
-    "requiresCompatibilities": [
-        "EC2"
-    ],
-    "cpu": "4096"
-}
\ No newline at end of file
diff --git a/.github/workflows/staging/westend-taskdef.json b/.github/workflows/staging/westend-taskdef.json
deleted file mode 100644
index 445227401a..0000000000
--- a/.github/workflows/staging/westend-taskdef.json
+++ /dev/null
@@ -1,53 +0,0 @@
-{
-    "containerDefinitions": [
-        {
-            "logConfiguration": {
-                "logDriver": "awslogs",
-                "options": {
-                    "awslogs-group": "gossamer-staging-CWLogsGroup-wPH0S1xHYmq7",
-                    "awslogs-region": "us-east-2",
-                    "awslogs-stream-prefix": "ecs"
-                }
-            },
-            "portMappings": [
-                {
-                    "containerPort": 7001,
-                    "protocol": "tcp"
-                },
-                {
-                    "containerPort": 8545,
-                    "protocol": "tcp"
-                },
-                {
-                    "containerPort": 8546,
-                    "protocol": "tcp"
-                },
-                {
-                    "containerPort": 8540,
-                    "protocol": "tcp"
-                },
-                {
-                    "containerPort": 6060,
-                    "protocol": "tcp"
-                }
-            ],
-            "environment": [],
-            "image": "500822580415.dkr.ecr.us-east-2.amazonaws.com/gossamer-westend",
-            "essential": true,
-            "name": "gossamer-westend"
-        }
-    ],
-    "placementConstraints": [
-        {
-            "type": "memberOf",
-            "expression": "attribute:ecs.availability-zone==us-east-2a"
-        }
-    ],
-    "memory": "12288",
-    "family": "gossamer-westend",
-    "networkMode": "host",
-    "requiresCompatibilities": [
-        "EC2"
-    ],
-    "cpu": "4096"
-}
\ No newline at end of file
diff --git a/.github/workflows/unit-tests.yml b/.github/workflows/unit-tests.yml
index 5fa2627284..2bf7393f07 100644
--- a/.github/workflows/unit-tests.yml
+++ b/.github/workflows/unit-tests.yml
@@ -89,7 +89,7 @@ jobs:
       - name: Test - Race
         run: make test-using-race-detector
 
-      - uses: codecov/codecov-action@v5.1.1
+      - uses: codecov/codecov-action@v5.1.2
         with:
           if_ci_failed: success
           informational: true
diff --git a/Dockerfile.development b/Dockerfile.development
index 01c8c5cc4f..0bcf8d736a 100644
--- a/Dockerfile.development
+++ b/Dockerfile.development
@@ -2,7 +2,6 @@ FROM golang:1.23
 
 ARG chain="polkadot"
 ARG basepath="~/.local/share/gossamer"
-ARG DD_API_KEY
 
 ENV chain=${chain}
 ENV GSSMRHOME=${basepath}
@@ -11,9 +10,12 @@ WORKDIR /gossamer
 
 COPY . .
 
-RUN go get ./...
-RUN go install -trimpath github.com/ChainSafe/gossamer/cmd/gossamer
+ARG GO_BUILD_FLAGS
+RUN go build \
+    -trimpath \
+    -o /gossamer/bin/gossamer \
+    ${GO_BUILD_FLAGS} \
+    ./cmd/gossamer
 
-RUN ["sh", "-c", "gossamer init --chain=${chain} --base-path=${basepath}/${chain}"]
-ENTRYPOINT ["sh", "-c", "gossamer --chain=${chain} --base-path=${basepath}/${chain} --rpc-external=true --unsafe-rpc=true --prometheus-external --prometheus-port=9876 --pprof.enabled --pprof.listening-address=\":6060\""]
 EXPOSE 7001 8545 8546 8540 9876 6060
+ENTRYPOINT [ "/gossamer/bin/gossamer" ]
diff --git a/Dockerfile.staging b/Dockerfile.staging
deleted file mode 100644
index eacc5e6a8c..0000000000
--- a/Dockerfile.staging
+++ /dev/null
@@ -1,24 +0,0 @@
-FROM golang:1.23
-
-ARG chain="polkadot"
-ARG basepath="~/.local/share/gossamer"
-ARG DD_API_KEY
-
-ENV chain=${chain}
-ENV GSSMRHOME=${basepath}
-ENV DD_API_KEY=${DD_API_KEY}
-ENV DD_HOSTNAME=${chain}-host
-
-RUN ["sh", "-c", "DD_AGENT_MAJOR_VERSION=7 DD_INSTALL_ONLY=true DD_API_KEY=${DD_API_KEY} DD_SITE=\"datadoghq.com\" bash -c \"$(curl -L https://s3.amazonaws.com/dd-agent/scripts/install_script.sh)\""]
-
-WORKDIR /gossamer
-
-COPY . .
-RUN ["sh", "-c", "mv .github/workflows/staging/openmetrics.d/${chain}-conf.yaml /etc/datadog-agent/conf.d/openmetrics.d/conf.yaml"]
-
-RUN go get ./...
-RUN go install -trimpath github.com/ChainSafe/gossamer/cmd/gossamer
-
-RUN ["sh", "-c", "gossamer init --chain=${chain} --base-path=${basepath}/${chain}"]
-ENTRYPOINT ["sh", "-c", "service datadog-agent start && gossamer --chain=${chain} --base-path=${basepath}/${chain} --rpc-external=true --unsafe-rpc=true --prometheus-external --prometheus-port=9876 --pprof.enabled --pprof.listening-address=\":6060\""]
-EXPOSE 7001 8545 8546 8540 9876 6060
diff --git a/Makefile b/Makefile
index 46a10a96e4..160fc26e64 100644
--- a/Makefile
+++ b/Makefile
@@ -21,7 +21,7 @@ help: Makefile
 .PHONY: lint
 lint:
 	go install github.com/golangci/golangci-lint/cmd/golangci-lint@v1.62
-	golangci-lint run
+	golangci-lint run --timeout 3m
 
 clean:
 	rm -fr ./bin
diff --git a/.github/CONTRIBUTING.md b/docs/CONTRIBUTING.md
similarity index 52%
rename from .github/CONTRIBUTING.md
rename to docs/CONTRIBUTING.md
index d30c905520..f1bd02b0aa 100644
--- a/.github/CONTRIBUTING.md
+++ b/docs/CONTRIBUTING.md
@@ -2,7 +2,7 @@
 
 Thank you for your interest in our implementation of the Polkadot Runtime Environment Implementation! We're excited to get to know you and work with you on gossamer. We've put together these guidelines to help you figure out how you can help us.
 
-At any point in this process feel free to reach out on [Discord](https://discord.gg/Xdc5xjE) with any questions or to say Hello :)
+At any point in this process feel free to reach out on [Discord](https://discord.gg/M5XgXGRv) with any questions or to say Hello :)
 
 ## Getting Started
 
@@ -12,87 +12,45 @@ The Web3 Foundation has a [Polkadot Wiki](https://wiki.polkadot.network/docs/get
 
 The [Polkadot Runtime Specification](https://research.web3.foundation/en/latest/_static/pdfview/viewer.html?file=../pdf/polkadot_re_spec.pdf) serves as our primary specification, however it is currently in its draft status so things may be subject to change.
 
-One important distinction is that we are building the Polkadot Runtime Environment, not Polkadot itself. Given that, although a deep understanding of Polkadot is helpful, it's not critical to contribute to gossamer. To help understand how the Runtime Environment relates to Polkadot, check out this [talk that one of our team members gave at DotCon](https://www.youtube.com/watch?v=nYkbYhM5Yfk).
+To understand more about Parachain Protocol please refer to [The Polkadot Parachain Host Implementers Guide](https://paritytech.github.io/polkadot-sdk/book/index.html).
+Additionally information about design that is done by our team for some modules refer to our [design docs](https://github.com/ChainSafe/gossamer/tree/development/docs/docs/design)
+or [Gossamer blogposts](https://blog.chainsafe.io/gossamer/).
+
+And there are many more articles and videos that we are willing to share if you are interested. So please come by to our [Discord](https://discord.gg/M5XgXGRv) channel to ask for help or simply say hi.
 
 For coding style, you may refer to the [code style](CODE_STYLE.md) document which we keep up to date with coding style conventions we have for this repository.
 
 ## Contribution Steps
-
-1. **Fork the gossamer repo.**
-2. **Create a local clone of gossamer.**
-
-    ```sh
-    go get -u github.com/ChainSafe/gossamer
-    cd $GOPATH/src/github.com/ChainSafe/gossamer
-    git init
-    ```
-
-    You may encounter a `package github.com/ChainSafe/gossamer: no Go files in ...` message when doing `go get`. This is not an error, since there are no go files in the project root.
-
-3. **Link your local clone to the fork on your Github repo.**
-
-    ```sh
-    git remote add your-gossamer-repo https://github.com/<your_github_user_name>/gossamer.git
-    ```
-
-4. **Link your local clone to the ChainSafe Systems repo so that you can easily fetch future changes to the ChainSafe Systems repo.**
-
-    ```sh
-    git remote add gossamer https://github.com/ChainSafe/gossamer.git
-    git remote -v (you should see myrepo and gossamer in the list of remotes)
-    ```
-
-5. You can optionally setup Git hooks defined in this repository with `make githooks`.
-6. **Find something to work on.**
-
-    To start, check out our open issues. We recommend starting with an [issue labeled `Good First Issue`](https://github.com/ChainSafe/gossamer/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+First+Issue%22). Leave a comment to let us know that you would like to work on it.
-
-    Another option is to improve gossamer where you see fit based on your evaluation of our code. In order to best facilitate collaboration, please create an issue before you start working on it.
-
-7. **Make improvements to the code.**
-
-    Each time you work on the code be sure that you are working on the branch that you have created as opposed to your local copy of the gossamer repo. Keeping your changes segregated in this branch will make it easier to merge your changes into the repo later.
-
-    ```sh
-    git checkout -b feature-in-progress-branch
-    ```
-
-8. **Test your changes.**
-
-    Changes that only affect a single file can be tested with
+1. Make sure you're familiar with our contribution guidelines (this document)!
+2. Find an issue you want to work on. We have a ["good first issue" label on github](https://github.com/ChainSafe/gossamer/issues?q=is%3Aissue%20state%3Aopen%20label%3A"good%20first%20issue). To avoid duplicate efforts or working on outdated tasks, please clarify your intentions in the issue comments before starting. This step ensures there are no parallel executions of the same issue and confirms its validity for implementation.
+3. Create your own fork of this repository.
+4. Make your changes in your local fork.
+5. If you've made a code change, make sure to lint and test your changes.
+   Changes that only affect a single file can be tested with
 
     ```sh
     go test <file_you_are_working_on>
     ```
 
-    Sometimes you may need to create mocks for interfaces, in that case, add a go generate comment. For example, for interface `Client` in the `dot/telemetry` package, the comment would be:
+   Sometimes you may need to create mocks for interfaces, in that case, add a go generate comment. For example, for interface `Client` in the `dot/telemetry` package, the comment would be:
 
     ```go
     //go:generate mockgen -destination=mock_myinterface_test.go -package $GOPACKAGE github.com/ChainSafe/gossamer/dot/telemetry Client
     ```
 
-    This will generate a Go file `mock_myinterface_test.go` with the `Client` mock. Note this is only accessible
-    in your current package since it's written to a `_test.go` file. We prefer to generate mocks locally where they are needed instead of sharing them to reduce package dependency and the Go API 'noise'.
+   This will generate a Go file `mock_myinterface_test.go` with the `Client` mock. Note this is only accessible
+   in your current package since it's written to a `_test.go` file. We prefer to generate mocks locally where they are needed instead of sharing them to reduce package dependency and the Go API 'noise'.
 
-    Generate the mock code with `go generate -run "mockgen" ./...` from your working directory. This will also update existing mocks. You can update all mocks by running `go generate -run "mockgen" ./...` from the repository root. Note this does not log anything out.
-
-    > To execute `//go:generate` commands that are placed at files with `//go:build integration` remember to add `-tags integration` in the `go generate` command eg. `go generate -tags integration ...`
-
-9. **Lint your changes.**
-
-    Before opening a pull request be sure to run the linter
+   Before opening a pull request be sure to run the linter
 
     ```sh
     make lint
     ```
-
-10. **Add licenses to new Go and Proto files**
-
+6. **Add licenses to new Go and Proto files**
     If you added any new file, run `make license` to setup all licenses on relevant files.
     If you do not have `make` available, you can copy paste the command from the Makefile's `license:` block and run that instead.
-11. **Create a pull request.**
-
-    Navigate your browser to [https://github.com/ChainSafe/gossamer](https://github.com/ChainSafe/gossamer) and click on the new pull request button. In the “base” box on the left, change the branch to “**base development**”, the branch that you want your changes to be applied to. In the “compare” box on the right, select feature-in-progress-branch, the branch containing the changes you want to apply. You will then be asked to answer a few questions about your pull request. After you complete the questionnaire, the pull request will appear in the list of pull requests at [https://github.com/ChainSafe/gossamer/pulls](https://github.com/ChainSafe/gossamer/pulls).
+7. Make an open pull request when you're ready for it to be reviewed. We review PRs on a regular basis. See Pull request etiquette for more information.
+8. You may be asked to sign a Contributor License Agreement (CLA). We make it relatively painless with CLA-bot.
 
 ## Note on memory intensive tests
 
@@ -175,7 +133,7 @@ If a change does not alter any logic (e.g. comments, dependencies, docs), then i
 ###  Labels
 
 The set of labels and their description can be found [labels.yml](/.github/labels.yml).
-To change update this file and CI will automatically add/remove changed labels. 
+To change update this file and CI will automatically add/remove changed labels.
 
 ### Process
 
@@ -204,21 +162,14 @@ Anyone can become a part-time contributor and help out on gossamer. Contribution
 - Engaging in Discord conversations, asking questions on how to contribute to the project
 - Opening up Github issues to contribute ideas on how the code can be improved
 - Opening up PRs referencing any open issue in the repo. PRs should include:
-  - Detailed context of what would be required for merge
-  - Tests that are consistent with how other tests are written in our implementation
+    - Detailed context of what would be required for merge
+    - Tests that are consistent with how other tests are written in our implementation
 - Proper labels, milestones, and projects (see other closed PRs for reference)
 - Follow up on open PRs
-  - Have an estimated timeframe to completion and let the core contributors know if a PR will take longer than expected
-
-We do not expect all part-time contributors to be experts on all the latest Polkadot documentation, but all contributors should at least be familiarized with the fundamentals of the [Polkadot Runtime Specification](https://research.web3.foundation/en/latest/polkadot/specifications/runtime.html).
+    - Have an estimated timeframe to completion and let the core contributors know if a PR will take longer than expected
 
 ### Core Contributors
+Core contributors are currently comprised of members of the ChainSafe Systems team.
 
-Core contributors are currently comprised of members of the ChainSafe Systems team. Core devs have all of the responsibilities of part-time contributors plus the majority of the following:
-
-- Participate in our software development process (standups, sprint planning, retrospectives, etc)
-- Stay up to date on the latest Polkadot research and updates
-- Commit high quality code on core functionality
-- Monitor github issues and PR’s to make sure owner, labels, descriptions are correct
-- Formulate independent ideas, suggest new work to do, point out improvements to existing approaches
-- Participate in code review, ensure code quality is excellent and test coverage is high
+### Join Core team
+If you have an intention of joining the core team, please 
\ No newline at end of file
diff --git a/docs/docs/assets/img/sd_img1.jpeg b/docs/docs/assets/img/sd_img1.jpeg
new file mode 100644
index 0000000000..b759509564
Binary files /dev/null and b/docs/docs/assets/img/sd_img1.jpeg differ
diff --git a/docs/docs/contributing.md b/docs/docs/contributing.md
deleted file mode 100644
index e4e6f229ed..0000000000
--- a/docs/docs/contributing.md
+++ /dev/null
@@ -1,132 +0,0 @@
-# Contribution Guidelines
-
-Thank you for your interest in our implementation of the Polkadot Runtime Environment Implementation! We're excited to get to know you and work with you on gossamer. We've put together these guidelines to help you figure out how you can help us.
-
-At any point in this process feel free to reach out on [Discord](https://discord.gg/Xdc5xjE) with any questions or to say Hello :)
-
-# Getting Started
-
-Generally, it is important to have a basic understanding of Polkadot and the Polkadot Runtime Environment. Having a stronger  understanding will allow you to make more significant contributions. We've put together a list of resources that can help you develop this fundamental knowledge.  
-
-The Web3 Foundation has a [Polkadot Wiki](https://wiki.polkadot.network/docs/en/learn-introduction) that would help both part-time and core contributors to the project in order to get up to speed. Our [wiki](https://github.com/ChainSafe/gossamer/wiki) also has some helpful resources. 
-
-The [Polkadot Runtime Specification](https://research.web3.foundation/en/latest/_static/pdfview/viewer.html?file=../pdf/polkadot_re_spec.pdf) serves as our primary specification, however it is currently in its draft status so things may be subject to change.
-
-One important thing distinction is that we are building the Polkadot Runtime Environment, not Polkadot itself. Given that, although a deep understanding of Polkadot is helpful, it's not critical to contribute to gossamer. To help understand how the Runtime Environment relates to Polkadot, check out this [talk that one of our team members gave at DotCon.](https://www.youtube.com/watch?v=nYkbYhM5Yfk)
-
-## Contribution Steps
-
-**1. Fork the gossamer repo.**
-
-**2. Create a local clone of gossamer.**
-
-```
-go get -u github.com/ChainSafe/gossamer
-cd $GOPATH/src/github.com/ChainSafe/gossamer
-git init
-```
-You may encounter a `package github.com/ChainSafe/gossamer: no Go files in ...` message when doing `go get`. This is not an error, since there are no go files in the project root.
-
-**3. Link your local clone to the fork on your Github repo.**
-
-```
-$ git remote add your-gossamer-repo https://github.com/<your_github_user_name>/gossamer.git
-```
-
-**4. Link your local clone to the ChainSafe Systems repo so that you can easily fetch future changes to the ChainSafe Systems repo.**
-     
-```
-$ git remote add gossamer https://github.com/ChainSafe/gossamer.git
-$ git remote -v (you should see myrepo and gossamer in the list of remotes)
-```
-
-**5. Find something to work on.**
-
-To start, check out our open issues. We recommend starting with an [issue labeled `Good First Issue`](https://github.com/ChainSafe/gossamer/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+First+Issue%22). Leave a comment to let us know that you would like to work on it. 
-
-Another option is to improve gossamer where you see fit based on your evaluation of our code. In order to best facilitate collaboration, please create an issue before you start working on it.
-
-**6. Make improvements to the code.**
-
-Each time you work on the code be sure that you are working on the branch that you have created as opposed to your local copy of the gossamer repo. Keeping your changes segregated in this branch will make it easier to merge your changes into the repo later.
-
-```
-$ git checkout feature-in-progress-branch
-```
-
-**7. Test your changes.**
-
-Changes that only affect a single file can be tested with
-
-```
-$ go test <file_you_are_working_on>
-```
-
-**8. Lint your changes.**
-
-Before opening a pull request be sure to run the linter
-
-```
-$ make lint
-```
-
-**9. Create a pull request.**
-
-Navigate your browser to [https://github.com/ChainSafe/gossamer](https://github.com/ChainSafe/gossamer) and click on the new pull request button. In the “base” box on the left, change the branch to “**base development**”, the branch that you want your changes to be applied to. In the “compare” box on the right, select feature-in-progress-branch, the branch containing the changes you want to apply. You will then be asked to answer a few questions about your pull request. After you complete the questionnaire, the pull request will appear in the list of pull requests at [https://github.com/ChainSafe/gossamer/pulls](https://github.com/ChainSafe/gossamer/pulls).
-
-## Note on memory intensive tests
-Unfortunately, the free tier for CI's have a memory cap and some tests will cause the CI to experience an out of memory error.
-In order to mitigate this we have introduced the concept of **short tests**. If your PR causes an out of memory error please separate the tests into two groups
-like below and make sure to label it `large`:
-
-```
-var stringTest = []string {
-    "This causes no leaks"
-}
-
-var largeStringTest = []string {
-    "Whoa this test is so big it causes an out of memory issue"
-}
-
-func TestStringTest(t *testing.T) {
-    ...
-}
-
-func TestLargeStringTest(t *testing.T) {
-   	if testing.Short() {
-  		t.Skip("\033[33mSkipping memory intensive test for <TEST NAME> in short mode\033[0m")
-    } else {
-        ...
-    }
-}
-```
-
-## Contributor Responsibilities
-
-We consider two types of contributions to our repo and categorize them as follows:
-
-### Part-Time Contributors
-
-Anyone can become a part-time contributor and help out on gossamer. Contributions can be made in the following ways:
-
--   Engaging in Discord conversations, asking questions on how to contribute to the project
--   Opening up Github issues to contribute ideas on how the code can be improved
--   Opening up PRs referencing any open issue in the repo. PRs should include:
-    -   Detailed context of what would be required for merge
-    -   Tests that are consistent with how other tests are written in our implementation
--   Proper labels, milestones, and projects (see other closed PRs for reference)
--   Follow up on open PRs
-    -   Have an estimated timeframe to completion and let the core contributors know if a PR will take longer than expected
-
-We do not expect all part-time contributors to be experts on all the latest Polkadot documentation, but all contributors should at least be familiarized with the fundamentals of The <a href="https://spec.polkadot.network/id-polkadot-protocol" target="_blank">Polkadot Runtime Specification.</a>
-
-### Core Contributors
-
-Core contributors are currently comprised of members of the ChainSafe Systems team. Core devs have all of the responsibilities of part-time contributors plus the majority of the following:
-
--   Participate in our software development process (standups, sprint planning, retrospectives, etc)
--   Stay up to date on the latest Polkadot research and updates
-- 	Commit high quality code on core functionality
--   Monitor github issues and PR’s to make sure owner, labels, descriptions are correct
--   Formulate independent ideas, suggest new work to do, point out improvements to existing approaches
--   Participate in code review, ensure code quality is excellent, and ensure high code coverage
diff --git a/docs/docs/design/statement-distribution.md b/docs/docs/design/statement-distribution.md
new file mode 100644
index 0000000000..658bf586b7
--- /dev/null
+++ b/docs/docs/design/statement-distribution.md
@@ -0,0 +1,146 @@
+# Statement Distribution
+
+This subsystem is responsible for distributing signed statements that we have generated and forwarding statements generated by our peers.
+
+## Subsystem Structure
+
+The subsystem needs to handle multiple channels, beyond the overseer channel we also need to manage request and responses channels that are generated by spawned goroutines. These goroutines are called "responders" and in the parity implementation there exists 2 "responders", *larger_statement_responder* (legacy) and *candidate_responder* (v2).
+
+The responsibility of these "responders" is to listen for incoming requests and forward them to inside the statement distribution (as they are spawned goroutines), which will reach the target function that will respond to the request properly. The "responders" also act as a limiter on the amount of requests we are capable of handling.
+ 
+For V2:
+- Incoming request type [AttestedCandidateRequest](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/protocol/src/request_response/v2.rs#L32)
+- Response type [AttestedCandidateResponse](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/protocol/src/request_response/v2.rs#L47)
+- The handler [answer_request](https://github.com/paritytech/polkadot-sdk/blob/c0921339f9d486981b3681760ee83ba9237f2eaa/polkadot/node/network/statement-distribution/src/v2/mod.rs#L3245)
+
+For V1 (No need for handling such requests or implementing the handlers, will be removed soon see https://github.com/paritytech/polkadot-sdk/issues/4447):
+- Incoming request type [StatementFetchingRequest](https://github.com/paritytech/polkadot-sdk/blob/c0921339f9d486981b3681760ee83ba9237f2eaa/polkadot/node/network/protocol/src/request_response/v1.rs#L196)
+- The handler [handle_responder_message](https://github.com/paritytech/polkadot-sdk/blob/c0921339f9d486981b3681760ee83ba9237f2eaa/polkadot/node/network/statement-distribution/src/legacy_v1/mod.rs#L1896)
+
+The V2 brings a new advantage, the validators don't send each other heavy `CommitedCandidateReceipt`, but instead request them lazily through request/response protocols.
+
+The messages that validators can exchange are: 
+- `Statement`: contains only a signed compact statement;
+- `BackedCandidateManifest`: advertise a description of a backed candidate and stored statements;
+- `BackedCandidateAcknowledgement`: acknowledges that a backed candidate is fully known.
+
+### Messages Received
+
+The subsystem must be registered with the overseer and handle subsystem-specific messages from it:
+
+1. [StatementDistributionMessage::Share](https://github.com/paritytech/polkadot-sdk/blob/c0921339f9d486981b3681760ee83ba9237f2eaa/polkadot/node/subsystem-types/src/messages.rs#L829)
+
+- We have originated a signed statement in the context of given relay-parent hash and it should be distributed to other validators
+
+2. [StatementDistributionMessage::Backed](https://github.com/paritytech/polkadot-sdk/blob/c0921339f9d486981b3681760ee83ba9237f2eaa/polkadot/node/subsystem-types/src/messages.rs#L836)
+
+- The candidate received enough validity votes from the backing group. If the candidate is backed as a result of a local statement, this message MUST be preceded by a `Share` message for that statement. This ensures that Statement Distribution is always aware of full candidates prior to receiving the `Backed` notification, even when the group size is 1 and the candidate is seconded locally
+
+3. [StatementDistributionMessage::NetworkBridgeUpdate](https://github.com/paritytech/polkadot-sdk/blob/c0921339f9d486981b3681760ee83ba9237f2eaa/polkadot/node/subsystem-types/src/messages.rs#L839)
+
+- Event from the network bridge.
+
+4. [OverseerSignal::ActiveLeaves](https://github.com/paritytech/polkadot-sdk/blob/c0921339f9d486981b3681760ee83ba9237f2eaa/polkadot/node/subsystem-types/src/lib.rs#L114)
+
+### Messages Sent
+
+1. [NetworkBridgeTxMessage::SendValidationMessages](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/subsystem-types/src/messages.rs#L424)
+
+- Send a batch of validation messages and they will be send in order
+
+2. [NetworkBridgeTxMessage::SendValidationMessage](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/subsystem-types/src/messages.rs#L416C2-L416C23)
+
+- Send a message to one or more peers on the validation peer-set.
+
+3. [NetworkBridgeTxMessage::ReportPeer](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/subsystem-types/src/messages.rs#L410)
+
+4. [CandidateBackingMessage::Statement](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/subsystem-types/src/messages.rs#L112)
+
+- Note a validator's statement about a particular candidate in the context of the given relay-parent. Disagreements about validity must be escalated to a broader check by the Disputes Subsystem, though that escalation is deferred until the approval voting stage to guarantee availability. Agreements are simply tallied until a quorum is reached.
+
+5. [ProspectiveParachainsMessage::GetHypotheticalMembership](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/subsystem-types/src/messages.rs#L1411)
+
+- Get the hypothetical or actual membership of candidates with the given properties under the specified active leaf associated fragment chain. For each candidate, we return a vector of leaves where the candidate is present or could be added. "Could be added" either means that the candidate can be added to the chain right now or could be added in the future (we may not have its ancestors yet). Note that even if we think it could be added in the future, we may find out that it was invalid, as time passes. If an active leaf is not in the vector, it means that there's no chance this candidate will become valid under that leaf in the future. If `fragment_chain_relay_parent` in the request is `Some()`, the return vector can only contain this relay parent (or none).
+
+6. [NetworkBridgeTxMessage::SendRequests](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/subsystem-types/src/messages.rs#L433)
+
+- Sends request via normal network layer
+
+## Subsystem State
+
+The Statement Distribution subsystem currently has 2 states to manage under the current implementation but here we should focus on `v2::State` given that `v1::State` is legacy code and will be removed soon see https://github.com/paritytech/polkadot-sdk/issues/4447.
+
+The state holds
+- the implicit view
+- candidates (a tracker for all known candidates in the view)
+- per-relay-parent state
+- per-session state
+- unused topologies (topologies might be received before the first leaf update, so we should cache it)
+- peers view and state
+- keystore
+- authorities (a map from authority id to peer id)
+- request and response manager
+
+## Message Handling Logic
+
+1. [handle_subsystem_message](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/lib.rs#L308): This handler deals with multiple kinds of messages from the overseer (also other subsystems):
+
+- **OverseerSignal::ActiveLeaves**: we should implement the [`v2::handle_active_leaves_update`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L578) and also [v2::handle_deactivate_leaves](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L798)
+
+- **StatementDistributionMessage::Share**: this message is handled by [`v2::share_local_statement`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L1181), where a local originated statement is imported and need to be distributed to peers, calls [`v2::circulate_statement`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L1343-L1344)
+
+- **StatementDistributionMessage::NetworkBridgeUpdate**: messages coming from network bridge might be labeled with its version. We should focus only on messages labeled `Version::V2` and `Version::V3`. Messages targeting the current protocol they are handled by [`v2::handle_network_update`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L428). The message from the network bridge can unwrap in one of the following messages:
+- `NetworkBridgeEvent::PeerConnected`: update the current subsystem state peer view
+- `NetworkBridgeEvent::PeerDisconnected`: update the current subsystem state peer view
+- `NetworkBridgeEvent::NewGossipTopology`: given the incoming topology checks if we already have such session index to supply the topology, otherwise keep it in the `unused_topology`
+- `NetworkBridgeEvent::PeerViewChange`: handled by [`handle_peer_view_update`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L838-L839)
+- `NetworkBridgeEvent::OurViewChange`: do nothing
+- `NetworkBridgeEvent::UpdatedAuthorityIds`: we could find the PeerIDs of current session authorities, update them in the subsystem state.
+- `NetworkBridgeEvent::PeerMessage`:
+    - `StatementDistributionMessage::V1(_)`: ignore the message
+    - `StatementDistributionMessage::V2(protocol_v2::StatementDistributionMessage::V1Compatibility)`: ignore the message
+    - `StatementDistributionMessage::V3(protocol_v3::StatementDistributionMessage::V1Compatibility)`: ignore the message
+    - `StatementDistributionMessage::V2(protocol_v2::StatementDistributionMessage::Statement)`: handled by [`handle_incoming_statement`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L1549-L1550)
+    - `StatementDistributionMessage::V3(protocol_v3::StatementDistributionMessage::Statement)`: handled by [`handle_incoming_statement`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L1549-L1550)
+    - `StatementDistributionMessage::V2(protocol_v2::StatementDistributionMessage::BackedCandidateManifest)`: handled by [`handle_incoming_manifest`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L2339-L2340)
+    - `StatementDistributionMessage::V3(protocol_v3::StatementDistributionMessage::BackedCandidateManifest)`: handled by [`handle_incoming_manifest`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L2339-L2340)
+    - `StatementDistributionMessage::V2(protocol_v2::StatementDistributionMessage::BackedCandidateKnown)`: handled by [`handle_incoming_acknowledgement`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L2726-L2727)
+    - `StatementDistributionMessage::V3(protocol_v3::StatementDistributionMessage::BackedCandidateKnown)`: handled by [`handle_incoming_acknowledgement`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L2726-L2727)
+
+- **StatementDistributionMessage::Backed**: handles the notification of a candidate being backed. The candidate should be known before to be handled correctly if the candidate is not known the message is dropped. This calls [`provide_candidate_to_grid`](https://github.com/paritytech/polkadot-sdk/blob/76a292b23bf6f35156fd3dd832e9c4ec31b24b2c/polkadot/node/network/statement-distribution/src/v2/mod.rs#L1983C10-L1983C35) which provides the a backable candidate to the grid and dispatchs backable candidates announcements and acknowledgments via grid topology, if the session topology is not yet available then it will be a noop. Next method used is [`prospective_backed_notification_fragment_chain_updates`](https://github.com/paritytech/polkadot-sdk/blob/76a292b23bf6f35156fd3dd832e9c4ec31b24b2c/polkadot/node/network/statement-distribution/src/v2/mod.rs#L2309) which retrieve hypothetical membership from Prospective-Parachains and send them to Candidate-Backing subsystem as fresh statements through the function [`send_backing_fresh_statements`](https://github.com/paritytech/polkadot-sdk/blob/41a5d8ec5f3d3d0ff82899be66113b223395ade5/polkadot/node/network/statement-distribution/src/v2/mod.rs#L1929).
+
+2. [handle_response](https://github.com/paritytech/polkadot-sdk/blob/b8da8faa0a675afbed1c9ed5d524a674e93910b9/polkadot/node/network/statement-distribution/src/lib.rs#L287) 
+
+- After `ResponseManager` receives a message from the peer we're requesting some data this handler is triggered to handle the incoming response. 
+
+3. [answer_request](https://github.com/paritytech/polkadot-sdk/blob/41a5d8ec5f3d3d0ff82899be66113b223395ade5/polkadot/node/network/statement-distribution/src/v2/mod.rs#L3245-L3246)
+
+- Given a [`AttestedCandidateRequest`](https://github.com/paritytech/polkadot-sdk/blob/82117ad53fc68e8097183e759926b62265ffff0a/polkadot/node/network/protocol/src/request_response/v2.rs#L32) request we should respond the request for the asked candidate hash.
+
+4. [dispatch_requests](https://github.com/paritytech/polkadot-sdk/blob/b8da8faa0a675afbed1c9ed5d524a674e93910b9/polkadot/node/network/statement-distribution/src/lib.rs#L303C8-L303C25)
+
+- This method is called in 2 situations: right after one of the above handles finishes execution, that is why while handling a message we might have produced a request to dispatch for example: we received a `Manifest` message and now we need to request the candidate so we build the candidate request and place them in the `RequestManager` queue and after handling the message we call `dispatch_requests`. The second situation is when we receive a `RetryRequest` message coming from `RequestManager`, meaning that we have failed requests in the queue to dispatch. 
+
+## Grid Mode
+
+Here is a brief explanation of the function [`build_session_topology`](https://github.com/paritytech/polkadot-sdk/blob/41a5d8ec5f3d3d0ff82899be66113b223395ade5/polkadot/node/network/statement-distribution/src/v2/grid.rs#L118-L119) that is an important part to define our sender/receivers in the grid mode topology
+
+The method [`build_session_topology`](https://github.com/paritytech/polkadot-sdk/blob/41a5d8ec5f3d3d0ff82899be66113b223395ade5/polkadot/node/network/statement-distribution/src/v2/grid.rs#L118-L119) builds a view of the topology for the session. The network bridge gives us the entire grid topology for a certain session. In it, we know our neighbors in the X axis and Y axis (based on our validator index). So together with the [`Groups`](https://github.com/paritytech/polkadot-sdk/blob/5ca726750da563c46449f9aa915296e6c6967e61/polkadot/node/network/statement-distribution/src/v2/groups.rs#L28), which is the validator group within the session, we can define the peers we expect to receive messages and the peers we should send messages to.
+
+1. We should not send `Manifests` or `Acknowledgements` to validators in the same group as ours. They are already present in the Cluster topology. We should send those messages to peers in the same "row" and "column" as ours if they are not part of our group.
+
+2. if the validator is not in the same group, we should check if we share the same "row" or "column". If we share the same **ROW** then I expect to receive messages from him, and I will propagate his messages with my **COLUMN** neighbors that are not part of the sender's group. It's the same logic the other way around. If we share the same **COLUMN** then I expect to receive messages from him, and I will propagate his messages with my **ROW** neighbors that are not part of the sender's group.
+
+Take the example:
+
+![Grid Topology Example](../assets/img/sd_img1.jpeg)
+
+1) Considering that **J** is our validator index, we share X axis with **[I, K, J]** and Y axis with **[B, F, N]**, lets say that a message coming from `B` arrives, we can only propagate the message to validator `I`, as `K` and `L` are from the same group as `B`.
+
+2) Considering that we, `J`, want to share a `Manifest` with our grid neighbors, we can send the message to **[I, K, J]** and **[B, F, N]** as they are not part of the group I belong to.
+
+## Request and Response Managers
+
+Whenever we're [`handling an incoming statement`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L1549-L1550) or [`handling an incoming manifest`](https://github.com/paritytech/polkadot-sdk/blob/3d8da815ecd12b8f04daf87d6ffba5ec4a181806/polkadot/node/network/statement-distribution/src/v2/mod.rs#L2339-L2340) we do check if we have the related candidate, if we don't know it we should request if from the peer and that is made through [`RequestManager`](https://github.com/paritytech/polkadot-sdk/blob/f4a196ab1473856c9c5992239fcc2f14c2c42914/polkadot/node/network/statement-distribution/src/v2/requests.rs#L162) and [`ResponseManager`](https://github.com/paritytech/polkadot-sdk/blob/f4a196ab1473856c9c5992239fcc2f14c2c42914/polkadot/node/network/statement-distribution/src/v2/requests.rs#L429).
+
+The outgoing requests are managed by the request manager, and it is responsible also for holding requests that failed and marking them to retry later. After the Statement Distribution finishes to handling some message it calls [`v2::dispatch_requests`](https://github.com/paritytech/polkadot-sdk/blob/f4a196ab1473856c9c5992239fcc2f14c2c42914/polkadot/node/network/statement-distribution/src/lib.rs#L303) which will drain the requests in the [`RequestManager`](https://github.com/paritytech/polkadot-sdk/blob/f4a196ab1473856c9c5992239fcc2f14c2c42914/polkadot/node/network/statement-distribution/src/v2/requests.rs#L162) manager queue and will now track the in-flight requests in the [`ResponseManager`](https://github.com/paritytech/polkadot-sdk/blob/f4a196ab1473856c9c5992239fcc2f14c2c42914/polkadot/node/network/statement-distribution/src/v2/requests.rs#L429), that is made through a communication channel, the request will be sent to `NetworkBridgeSubsystem` and the `ResponseManager` will wait until any info comes through communication channel pipe ([`receive_response`](https://github.com/paritytech/polkadot-sdk/blob/f4a196ab1473856c9c5992239fcc2f14c2c42914/polkadot/node/network/statement-distribution/src/v2/mod.rs#L3067)), when that happens the message will be handled by Statement Distribution Subsystem under [`handle_response`](https://github.com/paritytech/polkadot-sdk/blob/f4a196ab1473856c9c5992239fcc2f14c2c42914/polkadot/node/network/statement-distribution/src/v2/mod.rs#L3088).
diff --git a/go.mod b/go.mod
index d79aa39dc8..976adb84d3 100644
--- a/go.mod
+++ b/go.mod
@@ -7,10 +7,10 @@ require (
 	github.com/btcsuite/btcd/btcutil v1.1.6
 	github.com/btcsuite/btcutil v1.0.3-0.20201208143702-a53e38424cce
 	github.com/centrifuge/go-substrate-rpc-client/v4 v4.1.0
-	github.com/cockroachdb/pebble v1.1.2
+	github.com/cockroachdb/pebble v1.1.3
 	github.com/cosmos/go-bip39 v1.0.0
 	github.com/dgraph-io/badger/v4 v4.5.0
-	github.com/dgraph-io/ristretto/v2 v2.0.1
+	github.com/dgraph-io/ristretto/v2 v2.1.0
 	github.com/disiqueira/gotree v1.0.0
 	github.com/ethereum/go-ethereum v1.14.12
 	github.com/fatih/color v1.18.0
@@ -42,10 +42,10 @@ require (
 	github.com/tidwall/btree v1.7.0
 	github.com/tyler-smith/go-bip39 v1.1.0
 	go.uber.org/mock v0.5.0
-	golang.org/x/crypto v0.31.0
+	golang.org/x/crypto v0.32.0
 	golang.org/x/exp v0.0.0-20240719175910-8a7402abbf56
-	golang.org/x/term v0.27.0
-	google.golang.org/protobuf v1.35.2
+	golang.org/x/term v0.28.0
+	google.golang.org/protobuf v1.36.1
 	gopkg.in/yaml.v3 v3.0.1
 )
 
@@ -207,7 +207,7 @@ require (
 	golang.org/x/mod v0.19.0 // indirect
 	golang.org/x/net v0.31.0 // indirect
 	golang.org/x/sync v0.10.0 // indirect
-	golang.org/x/sys v0.28.0 // indirect
+	golang.org/x/sys v0.29.0 // indirect
 	golang.org/x/text v0.21.0 // indirect
 	golang.org/x/tools v0.23.0 // indirect
 	gonum.org/v1/gonum v0.15.0 // indirect
diff --git a/go.sum b/go.sum
index 2dc9b0b45e..8d7819f203 100644
--- a/go.sum
+++ b/go.sum
@@ -74,8 +74,8 @@ github.com/cockroachdb/fifo v0.0.0-20240606204812-0bbfbd93a7ce h1:giXvy4KSc/6g/e
 github.com/cockroachdb/fifo v0.0.0-20240606204812-0bbfbd93a7ce/go.mod h1:9/y3cnZ5GKakj/H4y9r9GTjCvAFta7KLgSHPJJYc52M=
 github.com/cockroachdb/logtags v0.0.0-20230118201751-21c54148d20b h1:r6VH0faHjZeQy818SGhaone5OnYfxFR/+AzdY3sf5aE=
 github.com/cockroachdb/logtags v0.0.0-20230118201751-21c54148d20b/go.mod h1:Vz9DsVWQQhf3vs21MhPMZpMGSht7O/2vFW2xusFUVOs=
-github.com/cockroachdb/pebble v1.1.2 h1:CUh2IPtR4swHlEj48Rhfzw6l/d0qA31fItcIszQVIsA=
-github.com/cockroachdb/pebble v1.1.2/go.mod h1:4exszw1r40423ZsmkG/09AFEG83I0uDgfujJdbL6kYU=
+github.com/cockroachdb/pebble v1.1.3 h1:GM5YY3Yb09KCGUQoyWdi3vsLErXHsmc3qRRWsX+tBqw=
+github.com/cockroachdb/pebble v1.1.3/go.mod h1:4exszw1r40423ZsmkG/09AFEG83I0uDgfujJdbL6kYU=
 github.com/cockroachdb/redact v1.1.5 h1:u1PMllDkdFfPWaNGMyLD1+so+aq3uUItthCFqzwPJ30=
 github.com/cockroachdb/redact v1.1.5/go.mod h1:BVNblN9mBWFyMyqK1k3AAiSxhvhfK2oOZZ2lK+dpvRg=
 github.com/cockroachdb/tokenbucket v0.0.0-20230807174530-cc333fc44b06 h1:zuQyyAKVxetITBuuhv3BI9cMrmStnpT18zmgmTxunpo=
@@ -115,8 +115,8 @@ github.com/decred/dcrd/dcrec/secp256k1/v4 v4.3.0/go.mod h1:v57UDF4pDQJcEfFUCRop3
 github.com/decred/dcrd/lru v1.0.0/go.mod h1:mxKOwFd7lFjN2GZYsiz/ecgqR6kkYAl+0pz0tEMk218=
 github.com/dgraph-io/badger/v4 v4.5.0 h1:TeJE3I1pIWLBjYhIYCA1+uxrjWEoJXImFBMEBVSm16g=
 github.com/dgraph-io/badger/v4 v4.5.0/go.mod h1:ysgYmIeG8dS/E8kwxT7xHyc7MkmwNYLRoYnFbr7387A=
-github.com/dgraph-io/ristretto/v2 v2.0.1 h1:7W0LfEP+USCmtrUjJsk+Jv2jbhJmb72N4yRI7GrLdMI=
-github.com/dgraph-io/ristretto/v2 v2.0.1/go.mod h1:K7caLeufSdxm+ITp1n/73U+VbFVAHrexfLbz4n14hpo=
+github.com/dgraph-io/ristretto/v2 v2.1.0 h1:59LjpOJLNDULHh8MC4UaegN52lC4JnO2dITsie/Pa8I=
+github.com/dgraph-io/ristretto/v2 v2.1.0/go.mod h1:uejeqfYXpUomfse0+lO+13ATz4TypQYLJZzBSAemuB4=
 github.com/dgryski/go-farm v0.0.0-20200201041132-a6ae2369ad13 h1:fAjc9m62+UWV/WAFKLNi6ZS0675eEUC9y3AlwSbQu1Y=
 github.com/dgryski/go-farm v0.0.0-20200201041132-a6ae2369ad13/go.mod h1:SqUrOPUnsFjfmXRMNPybcSiG0BgUW2AuFH8PAnS2iTw=
 github.com/disiqueira/gotree v1.0.0 h1:en5wk87n7/Jyk6gVME3cx3xN9KmUCstJ1IjHr4Se4To=
@@ -698,8 +698,8 @@ golang.org/x/crypto v0.0.0-20210921155107-089bfa567519/go.mod h1:GvvjBRRGRdwPK5y
 golang.org/x/crypto v0.8.0/go.mod h1:mRqEX+O9/h5TFCrQhkgjo2yKi0yYA+9ecGkdQoHrywE=
 golang.org/x/crypto v0.12.0/go.mod h1:NF0Gs7EO5K4qLn+Ylc+fih8BSTeIjAP05siRnAh98yw=
 golang.org/x/crypto v0.18.0/go.mod h1:R0j02AL6hcrfOiy9T4ZYp/rcWeMxM3L6QYxlOuEG1mg=
-golang.org/x/crypto v0.31.0 h1:ihbySMvVjLAeSH1IbfcRTkD/iNscyz8rGzjF/E5hV6U=
-golang.org/x/crypto v0.31.0/go.mod h1:kDsLvtWBEx7MV9tJOj9bnXsPbxwJQ6csT/x4KIN4Ssk=
+golang.org/x/crypto v0.32.0 h1:euUpcYgM8WcP71gNpTqQCn6rC2t6ULUPiOzfWaXVVfc=
+golang.org/x/crypto v0.32.0/go.mod h1:ZnnJkOaASj8g0AjIduWNlq2NRxL0PlBrbKVyZ6V/Ugc=
 golang.org/x/exp v0.0.0-20190121172915-509febef88a4/go.mod h1:CJ0aWSM057203Lf6IL+f9T1iT9GByDxfZKAQTCR3kQA=
 golang.org/x/exp v0.0.0-20240719175910-8a7402abbf56 h1:2dVuKD2vS7b0QIHQbpyTISPd0LeHDbnYEryqj5Q1ug8=
 golang.org/x/exp v0.0.0-20240719175910-8a7402abbf56/go.mod h1:M4RDyNAINzryxdtnbRXRL/OHtkFuWGRjvuhBJpk2IlY=
@@ -801,8 +801,8 @@ golang.org/x/sys v0.8.0/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
 golang.org/x/sys v0.9.0/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
 golang.org/x/sys v0.11.0/go.mod h1:oPkhp1MJrh7nUepCBck5+mAzfO9JrbApNNgaTdGDITg=
 golang.org/x/sys v0.16.0/go.mod h1:/VUhepiaJMQUp4+oa/7Zr1D23ma6VTLIYjOOTFZPUcA=
-golang.org/x/sys v0.28.0 h1:Fksou7UEQUWlKvIdsqzJmUmCX3cZuD2+P3XyyzwMhlA=
-golang.org/x/sys v0.28.0/go.mod h1:/VUhepiaJMQUp4+oa/7Zr1D23ma6VTLIYjOOTFZPUcA=
+golang.org/x/sys v0.29.0 h1:TPYlXGxvx1MGTn2GiZDhnjPA9wZzZeGKHHmKhHYvgaU=
+golang.org/x/sys v0.29.0/go.mod h1:/VUhepiaJMQUp4+oa/7Zr1D23ma6VTLIYjOOTFZPUcA=
 golang.org/x/term v0.0.0-20201126162022-7de9c90e9dd1/go.mod h1:bj7SfCRtBDWHUb9snDiAeCFNEtKQo2Wmx5Cou7ajbmo=
 golang.org/x/term v0.0.0-20210927222741-03fcf44c2211/go.mod h1:jbD1KX2456YbFQfuXm/mYQcufACuNUgVhRMnK/tPxf8=
 golang.org/x/term v0.5.0/go.mod h1:jMB1sMXY+tzblOD4FWmEbocvup2/aLOaQEp7JmGp78k=
@@ -810,8 +810,8 @@ golang.org/x/term v0.7.0/go.mod h1:P32HKFT3hSsZrRxla30E9HqToFYAQPCMs/zFMBUFqPY=
 golang.org/x/term v0.8.0/go.mod h1:xPskH00ivmX89bAKVGSKKtLOWNx2+17Eiy94tnKShWo=
 golang.org/x/term v0.11.0/go.mod h1:zC9APTIj3jG3FdV/Ons+XE1riIZXG4aZ4GTHiPZJPIU=
 golang.org/x/term v0.16.0/go.mod h1:yn7UURbUtPyrVJPGPq404EukNFxcm/foM+bV/bfcDsY=
-golang.org/x/term v0.27.0 h1:WP60Sv1nlK1T6SupCHbXzSaN0b9wUmsPoRS9b61A23Q=
-golang.org/x/term v0.27.0/go.mod h1:iMsnZpn0cago0GOrHO2+Y7u7JPn5AylBrcoWkElMTSM=
+golang.org/x/term v0.28.0 h1:/Ts8HFuMR2E6IP/jlo7QVLZHggjKQbhu/7H0LJFr3Gg=
+golang.org/x/term v0.28.0/go.mod h1:Sw/lC2IAUZ92udQNf3WodGtn4k/XoLyZoh8v/8uiwek=
 golang.org/x/text v0.3.0/go.mod h1:NqM8EUOU14njkJ3fqMW+pc6Ldnwhi/IjpwHt7yyuwOQ=
 golang.org/x/text v0.3.1-0.20180807135948-17ff2d5776d2/go.mod h1:NqM8EUOU14njkJ3fqMW+pc6Ldnwhi/IjpwHt7yyuwOQ=
 golang.org/x/text v0.3.2/go.mod h1:bEr9sfX3Q8Zfm5fL9x+3itogRgK3+ptLWKqgva+5dAk=
@@ -886,8 +886,8 @@ google.golang.org/protobuf v1.22.0/go.mod h1:EGpADcykh3NcUnDUJcl1+ZksZNG86OlYog2
 google.golang.org/protobuf v1.23.0/go.mod h1:EGpADcykh3NcUnDUJcl1+ZksZNG86OlYog2l/sGQquU=
 google.golang.org/protobuf v1.23.1-0.20200526195155-81db48ad09cc/go.mod h1:EGpADcykh3NcUnDUJcl1+ZksZNG86OlYog2l/sGQquU=
 google.golang.org/protobuf v1.25.0/go.mod h1:9JNX74DMeImyA3h4bdi1ymwjUzf21/xIlbajtzgsN7c=
-google.golang.org/protobuf v1.35.2 h1:8Ar7bF+apOIoThw1EdZl0p1oWvMqTHmpA2fRTyZO8io=
-google.golang.org/protobuf v1.35.2/go.mod h1:9fA7Ob0pmnwhb644+1+CVWFRbNajQ6iRojtC/QF5bRE=
+google.golang.org/protobuf v1.36.1 h1:yBPeRvTftaleIgM3PZ/WBIZ7XM/eEYAaEyCwvyjq/gk=
+google.golang.org/protobuf v1.36.1/go.mod h1:9fA7Ob0pmnwhb644+1+CVWFRbNajQ6iRojtC/QF5bRE=
 gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
 gopkg.in/check.v1 v1.0.0-20180628173108-788fd7840127/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
 gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=