Skip to content

Latest commit

 

History

History
44 lines (28 loc) · 1.21 KB

ingestion.md

File metadata and controls

44 lines (28 loc) · 1.21 KB
Raw
description
How EaaS ingests data from the blockchain

Ingestion

The CosmosSDK does have event streaming for results of transaction processing, but they lose the correlation between event and transaction. Currently there is only one way to ingest all points of data from the blockchain without losing those correlating data points that make the data useful.

The SDK supports the use of Google Protobuf for managing transactions, queries, and the objects used for both. Protobuf message objects have the ability to define whats called gRPC - an API layer that allows for seamless integration with any client.

EaaS leverages the given gRPC APIs to quickly query the blockchain for any piece of data it might need.

How it starts

As everything on a blockchain begins with a block, so must the ingestion process.

Block

Proposer

Validator Set

Missed Blocks

Transactions

  • Transaction
  • Gas fees
  • Messages, message types
  • Addresses
  • Markers/Denoms
  • NFTs
  • Governance
  • IBC
  • Smart Contracts
  • Transaction signatures

Update assets/denoms

Update validator records

Update cached tx counts

Update block latency