[
https://issues.apache.org/jira/browse/NIFI-14838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amilcar Giménez updated NIFI-14838:
-----------------------------------
Description:
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: Connect to the controller service and specific events, convert each
event to a FlowFile (JSON) with useful attributes, and route to
{{{}success{}}}/{{{}failure.{}}}
I created a public library under the MIT licence in order to connect to a node
through the Beacon Chain API, and I use it for this processor:
[Am-ilcar/eth-events-listener|https://github.com/Am-ilcar/eth-events-listener]
This can be useful for other developers too.
About the ETH Beacon Chain API: [https://ethereum.github.io/beacon-APIs/#/]
was:
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: Connect to the controller service and specific events, convert each
event to a FlowFile (JSON) with useful attributes, and route to
{{{}success{}}}/{{{}failure.{}}}
I made a public library to connect to ETH Events Service
About the ETH Beacon Chain API: [https://ethereum.github.io/beacon-APIs/#/]
> 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
> Priority: Major
>
> 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: Connect to the controller service and specific events, convert
> each event to a FlowFile (JSON) with useful attributes, and route to
> {{{}success{}}}/{{{}failure.{}}}
>
> I created a public library under the MIT licence in order to connect to a
> node through the Beacon Chain API, and I use it for this processor:
> [Am-ilcar/eth-events-listener|https://github.com/Am-ilcar/eth-events-listener]
> This can be useful for other developers too.
> About the ETH Beacon Chain API: [https://ethereum.github.io/beacon-APIs/#/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
