Skip to main content

Data Markets

Snapshotters generate snapshots, both base and higher order, as per the data sources defined by the data markets they participate in. Each data market maintains its specific protocol state concerning the submission, calculation, and finalization of such snapshots.

The data sources defined by a market can be static or dynamic, depending on the use case at hand.

Static Data Sources

Our implementation of a data market serves datasets to render live Uniswap V2, Uniswap V3, and Aave V3 dashboards. Further details about the data source configurations and snapshot schemas can be found in the following sections of our documentation:

Continuing with the Uniswap V2 example, you can explore the data sources list defined as part of the Uniswap v2 specific configuration in the snapshotter-configs repository.


The projects field in the above configuration snippet represents the Uniswap v2 pair contract addresses that are tracked, and snapshots are generated for these contracts. To further understand how snapshots on these contracts are tracked, refer to the section on Project Types and IDs.

Dynamic Data Sources

In situations where data sources are constantly changing or numerous, making it impractical to maintain an extensive list, the data sources need not be explicitly defined in the configuration.

Instead, the snapshotter implementation operates in 'bulk mode'. The data source configuration specifies computation modules that utilize general-purpose preloaded datasets to filter transactions, event logs, etc., on contract addresses of interest. This is where the signaling of data sources comes into play.


Data Source Signaling

Data sources can be dynamically added to the contract based on the role of certain peers in the ecosystem known as 'signalers.' This is a pivotal aspect of the Powerloom Protocol ecosystem, separate from snapshotting, and is on track to be decentralized. The decentralization will take into account on-chain activity, market forces, and accommodate a demand-driven, dynamic data ecosystem.

In the current implementation of a use case that tracks wallet activity for Quests on Polygon zkEVM, such wallets are added from a data feed supplied by Merkle. The feed consists of wallets that sign up on their platform. Only these wallet addresses are of interest to the Quest platform on Merkle for tracking activities across DEXs and asset bridges.

Read more about it in the snapshotter specs of the bulk node.

Merkle Data Source Signaling

Project Types and IDs

All data sources are tracked with a project ID on the protocol. Think of it as a stream of datasets, finalized by consensus against each epoch released on the protocol.

Find more details in the specifications of snapshot generation.