substreams.yaml, defines the modules composing the Substreams. The manifest is used, among other things, to define the dependencies between your module's inputs and outputs.
v0.1.0- no questions asked.
substreams pack substreams.yamlyour package.
namemust match this regular expression:
A-Zand can contain numbers thereafter
importssection imports modules with their WASM code, all of their (compiled) protobuf definitions and modules definition. The imported modules can be referred to by the key later in the
.yamlfile), or remote path as long as it starts with
Protobufsection points to the protobuf definitions used by these modules.
importPaths. Note that the
importssection will also affect which
.protofiles end up in your package.
substreams pack, as well as any
[a-zA-Z0-9_]. These are the same rules as for
initialBlockfield can be elided and its value will be inferred by its dependent
inputs, as long as all the inputs have the same
initialBlock. If some inputs have different
initialBlock, then it becomes mandatory.
module. There are two types of modules:
set(last key wins merge strategy)
set_if_not_exists(first key wins merge strategy)
append(concatenates two keys' values)
add(sum the two keys' values)
min(min between two keys' values)
max(max between two keys' values)
inputsis a list of input structures. For each object, one of three keys is required:
store(can also define a