Output
sf.substreams.cosmos.v1.EventList
Inputs
Package ref
my-injective-events@v0.1.0Run package
CLI
Run map_event_groups from the command line.
substreams run my-injective-events@v0.1.0 map_event_groups -e injective-mainnet --start-block -1substreams auth or directly on thegraph.market (see docs).README
This package was initialized via substreams init, using the injective-events template.
substreams build
substreams auth
substreams gui # Get streaming!
substreams registry login # Login to substreams.dev
substreams registry publish # Publish your Substreams to substreams.dev
map_event_groupsThis module uses the Injective Foundational Modules and applies filters on the chosen events and attributes.
Modules
Output
sf.substreams.cosmos.v1.EventList
Inputs
Output
sf.substreams.cosmos.v1.EventList
Inputs
Output
sf.substreams.cosmos.v1.TransactionList
Inputs
`filtered_event_groups` reads from `all_events` and applies a filter on the event types and attribute keys, outputing all the events from transactions that have at least one event matching the filter. Example usage: `type:injective.peggy.v1.EventDepositClaim || (type:wasm && attr:_contract_address)`
Output
sf.substreams.cosmos.v1.EventList
Inputs
`filtered_events_groups_by_attribute_value` reads from `all_events` and applies a filter on the event types, attribute keys and values, outputing all the events from transactions that have at least one event matching the filter. Example usage: "type:wasm && attr:_contract_address:inj1v77y5ttah96dc9qkcpc88ad7rce8n88e99t3m5" To use this module with an index, import it and override it with the `use:` parameter, setting blockFilter.Query.String to a query that matches the event type and attribute keys only (ex: `type:wasm && attr:_contract_address`)
Output
sf.substreams.cosmos.v1.EventList
Inputs
Output
sf.substreams.cosmos.v1.EventList
Inputs
`filtered_events_by_attribute_value` reads from `all_events` and applies a filter on the event types, attribute keys and values, only outputing the events that match the filter. Example usage: "type:wasm && attr:_contract_address:inj1v77y5ttah96dc9qkcpc88ad7rce8n88e99t3m5" To use this module with an index, import it and override it with the `use:` parameter, setting blockFilter.Query.String to a query that matches the event type and attribute keys only (ex: `type:wasm && attr:_contract_address`)
Output
sf.substreams.cosmos.v1.EventList
Inputs
`filtered_trx_by_events` reads from `all_transactions` and applies a filter on the event types and attribute keys, outputing the complete transactions that have at least one event matching the filter. Example usage: `type:injective.peggy.v1.EventDepositClaim || (type:wasm && attr:_contract_address)`
Output
sf.substreams.cosmos.v1.TransactionList
Inputs
`filtered_trx_by_events_attribute_value` reads from `all_events` and applies a filter on the event types, attribute keys and values, outputing the complete transactions that have at least one event matching the filter. Example usage: "type:wasm && attr:_contract_address:inj1v77y5ttah96dc9qkcpc88ad7rce8n88e99t3m5" To use this module with an index, import it and override it with the `use:` parameter, setting blockFilter.Query.String to a query that matches the event type and attribute keys only (ex: `type:wasm && attr:_contract_address`)
Output
sf.substreams.cosmos.v1.TransactionList
Inputs
`index_events` sets the keys corresponding to all event 'types' and 'attribute keys' in the block ex: `type:coin_received`, `type:injective.peggy.v1.EventDepositClaim`, `attr:action`, `attr:sender` ... The attribute values are never indexed because they have a high cardinality and would be too expensive to index.
Output
sf.substreams.index.v1.Keys
Inputs