FAQ

A Predicate Operator runs a client responsible for two key tasks: attestation and indexing. The attestation service verifies that transactions meet their destination protocols policy, while the indexer builds dynamic social graphs by indexing Ethereum transactions.

These policies are stored on Ethereum and define specific predicate functions that must be satisfied. Predicate functions can express a wide range of logic, but they all return a boolean value. One common example is the membership function, which checks if an address is part of a dynamic list of accounts.

Correctness, latency, and availability are the three key performance metrics for Operators. These metrics are tracked and influence the opportunity for Operators to claim future network emissions.

We have a testnet and mainnet dashboard you can reference to check your performance metrics. (Availability and Correctness will be made public starting Q1 2025)

If you’d like to create your own dashboard or simply query your operator metrics you can hit the following endpoint: http://your-operator-url:9090/metrics

The complexity of the policy and its underlying rules (see Introduction) will determine the network emissions that are generated on a per-transaction basis. These emissions will be deposited into the Predicate Treasury and can be claimed by Operators (Q2 2025)

Slashing has not been implemented yet. Clear guidelines will be provided to the community before it is activated.

All Operator activity will be made publicly available; latency, response rates, results, stake etc. However, the sole slashing condition for Operators will be instances of false negatives for objective policies. Specifically, an Operator will be slashed if it incorrectly signs a transaction, approving a transaction which does not satisfy the conditions in the destination protocol’s policy.