Experimental
The type of database context. Usually DbContext, if used with standard @tezos-dappetizer/database.
The type of your custom data that flows in indexingContext
through all indexers for a block.
See createContextData for more details.
The type of your custom data associated with the smart rollup that flows in indexingContext
through this indexer.
See shouldIndex for more details.
Optional
Readonly
nameThe explicit name used to easily identify the indexer, for example in error messages.
Optional
indexIndexes a SmartRollupAddMessagesOperation related to ANY smart rollup as far as the operation does not contain the rollup address. You need to filter out messages unrelated to the selected (see shouldIndex) smart rollup yourself based on decoded message. Also, this can be called before shouldIndex method.
Optional
indexIndexes a SmartRollupCementOperation related to the selected (see shouldIndex) smart rollup.
Optional
indexIndexes a SmartRollupExecuteOutboxMessageOperation related to the selected (see shouldIndex) smart rollup.
Optional
indexIndexes a SmartRollupOriginateOperation related to the selected (see shouldIndex) smart rollup.
Optional
indexIndexes a SmartRollupPublishOperation related to the selected (see shouldIndex) smart rollup.
Optional
indexIndexes a SmartRollupRecoverBondOperation related to the selected (see shouldIndex) smart rollup.
Optional
indexIndexes a SmartRollupRefuteOperation related to the selected (see shouldIndex) smart rollup.
Optional
indexIndexes a SmartRollupTimeoutOperation related to the selected (see shouldIndex) smart rollup.
Optional
shouldDynamically selects a smart rollup for indexing (remaining index*()
methods) by this indexer.
Firstly, the selective indexing is evaluated based on Dappetizer config file.
If this method is not implemented, then all smart rollups are selected.
Also, it associates returned value as your custom data with the smart rollup.
Then the data flows in indexingContext
through this indexer for all blocks being indexed.
If false
, then the smart rollup will not be indexed.
Otherwise, your custom data to be associated with the smart rollup if it should be indexed.
If you do not care about the data, then just return true
.
The method can be async, so the returned value can be a Promise
.
The smart rollup to be evaluated whether it should be indexed.
The database context but it must execute only readonly queries so that it does not interfere with block indexing.
Generated using TypeDoc
Provides extension points for block parts related to a smart rollup. At least one of methods must be implemented.