You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Amilcar Giménez (Jira)" <ji...@apache.org> on 2025/08/09 19:01:00 UTC

[jira] [Created] (NIFI-14838) Add Ethereum Beacon Chain Event Processor and Controller Service

Amilcar Giménez created NIFI-14838:
--------------------------------------

             Summary: Add Ethereum Beacon Chain Event Processor and Controller Service
                 Key: NIFI-14838
                 URL: https://issues.apache.org/jira/browse/NIFI-14838
             Project: Apache NiFi
          Issue Type: New Feature
          Components: Extensions
    Affects Versions: 2.6.0
            Reporter: Amilcar Giménez
            Assignee: Amilcar Giménez


I want to provide an integration with the Ethereum Beacon Chain so NiFi users can consume consensus-layer events (SSE) from {{/eth/v1/events}} and build dataflows for monitoring, analytics, alerting, and archival. The Beacon Node API is standardized and widely implemented by clients such as Lighthouse, Teku, Nimbus, Prysm, and Lodestar.

Proposed Components

*Controller Service:* {{BeaconChainClientService}}
 * Purpose: Manage connection/config to a Beacon node and expose an event subscription client.

 

*Processor:* {{ConsumeBeaconChainEvents}}
 * Purpose: Open an SSE stream to {{/eth/v1/events}} (topics: {{{}head{}}}, {{{}block{}}}, {{{}attestation{}}}, {{{}finalized_checkpoint{}}}, {{{}chain_reorg{}}}, {{{}contribution_and_proof{}}}, etc.), convert each event to a FlowFile (JSON) with useful attributes, and route to {{{}success{}}}/{{{}failure{}}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)