Event Listener

Origin Event Listener

The Origin Event Listener follows the blockchain, looking for Origin events and passing those events on to whatever systems need that data. These events are annotated with full information about the Origin resources (listings/offers/) that fired off these events.

The data from the listener can be used to build and keep up-to-date an offline index of all Origin Protocol data on the chain.

The listener will let you know one or more times about an event. Make sure your webhook endpoint is idempotent, and can handle receiving the same data multiple times!

To allow the listener to be compatible with infura.io, the listener does not use subscriptions, only API queries.

Running Localy

Start the event-listener container.

docker-compose up event-listener

You should see messages in the console indicating events are being indexed.

Command line options


--verbose Optional. Output json for all event information to stdout.

--webhook=yoururl Optional. Post json for each event to the URL.

--discord-webhook=discordurl Optional. Post a short Discord notification for each marketplace event.

--elasticsearch Optional. Record data into Elasticsearch.

--db Optional. Record data into Postgres.

Config: --blockEpoch=blockNumber Optional. Block number corresponding to Origin’s plaform launch date.

--defaultContinueBlock=blockNumber Optional. Block number value to use if there is no continue data (ex. when listener is started for the first time).

--continue-file=path Optional. Will start following events at the block number defined in the file, and will keep this file updated as it listens to events. The continue file is JSON, in the format {"lastLogBlock":222, "version":1}. If no continue file is specified, the event listener stores the continue data in the Postgres DB.

--trailBlocks=numBlocks Optional. Number of confirmation blocks before data is indexed

--web3Url=URL Optional. Web3 provider. For example https://mainnet.infura.io/v2/

--ipfsUrl=URL Optional. IPFS cluster to use for fetching the off-chain data.

--arbitratorAccount=ethereumAddress Optional. Address of the Origin arbitrator account.

--affiliateAccount=ethereumAddress Optional. Address of the Origin affiliate account.

--attestationAccount=ethereumAddress Optional. Address of the Origin attestation account.

Env variables

The listener calls out origin.js to load and validate data from the blockchain. In order to properly configure an origin.js object, the listener uses the following environment variables:

Those values can be found via the DApp info page:

How the listener works

The listener checks every few seconds for a new block number. If it sees one, it requests all Origin related events from the last block it saw an event on, to the new block.

For each of those events, the listener decodes them, annotates them with some useful fields, then runs a rule based on the event/contract to load additional information about the event through origin.js. For example, a ListingCreated event on a marketplace contract will have the results of origin.marketplace.get added to it. The code that uses the event listener output doesn’t need to talk to the blockchain or IPFS at all.

After being annotated with more information, the event is then output to the places set by the command line options.

Error handling