A contract listener configures FireFly to stream events from the blockchain,
from a specific location on the blockchain, according to a given definition
of the interface for that event.
Check out the Custom Contracts Tutorial for
a walk-through of how to set up listeners for the events from your smart contracts.
The stringified signature of the event, as computed by the blockchain plugin
string
topic
A topic to set on the FireFly event that is emitted each time a blockchain event is detected from the blockchain. Setting this topic on a number of listeners allows applications to easily subscribe to all events they need
string
options
Options that control how the listener subscribes to events from the underlying blockchain
Additional blockchain specific fields about this event from the original smart contract. Used by the blockchain plugin and for documentation generation.
The name of the parameter. Note that parameters must be ordered correctly on the FFI, according to the order in the blockchain smart contract
string
schema
FireFly uses an extended subset of JSON Schema to describe parameters, similar to OpenAPI/Swagger. Converters are available for native blockchain interface definitions / type systems - such as an Ethereum ABI. See the documentation for more detail
A blockchain specific string, such as a block number, to start listening from. The special strings ‘oldest’ and ‘newest’ are supported by all blockchain connectors. Default is ‘newest’