For Blockchain Events

For every event we track, we need the proper configuration format. This allows for flexible and precise point allocation based on blockchain interactions.

Points are issued retroactively. If new conditions are added, users will be rewarded retroactively according to the specified block ranges or timestamps.

How It Works

The system scans blockchain logs for events matching the specified criteria (contract address, chain ID, method, etc.).
When a matching event is found, it extracts the relevant data using the configured fields.
Points are calculated based on either the fixed points value or the math_expr formula.
The calculated points are attributed to the address specified by beneficiary_field.
Additional filters (equivalence_filters) can be applied to match specific event parameters.
Time ranges can be set using block numbers or timestamps for precise control over event tracking periods.

FAQ

The math_expr field takes in a mathematical expression where x inside the expression denotes the value of the decoded_log_field.

Usage Tips

Use start_block_number and end_block_number or start_timestamp and end_timestamp to define specific periods for event tracking.
The math_expr field allows for dynamic point calculation based on event data. Use decoded_log_field to specify which event field to use in the calculation.
For fixed point rewards, simply use the points field instead of math_expr.
The equivalence_filters can be used to create more specific conditions for point allocation within a single event type.
Ensure the event_string matches exactly with the smart contract’s event definition to guarantee correct event parsing.

Configuration Fields

event_name

string

required

A descriptive name for the event being tracked. Example: "Uniswap V3 Swap"

event_description

string

A brief description of the event for clarity.

beneficiary_field

string

required

Specifies which field contains the address to receive points. Options:

"transaction.from": Uses the transaction sender’s address
Any field name from the event log Example: "sender"

method

string

required

The method signature or name associated with the event. Example: "Swap"

contract_address

string

required

The address of the smart contract that emits the event. Example: "0xCBCdF9626bC03E24f779434178A73a0B4bad62eD"

chain_id

integer

required

The ID of the blockchain network. Example: 1 (for Ethereum mainnet)

event_string

string

required

The full event signature. Example: "event Swap(address sender indexed, uint256 amount0In, uint256 amount1In, uint256 amount0Out, uint256 amount1Out, address to indexed)"

points

numeric

Fixed number of points to award for this event. Use this or math_expr for point calculation.

math_expr

string

Mathematical expression to calculate points dynamically. Use this or points for point calculation. Example: "x * 0.1"

start_block_number

integer

The starting block number to begin tracking events (inclusive).

end_block_number

integer

The ending block number to stop tracking events (inclusive).

start_timestamp

timestamp

The starting timestamp to begin tracking events. Format: "YYYY-MM-DDTHH:MM:SS.sssZ"

end_timestamp

timestamp

The ending timestamp to stop tracking events. Format: "YYYY-MM-DDTHH:MM:SS.sssZ"

decoded_log_field

string

The specific field in the decoded log to use for point calculation when using math_expr.

equivalence_filters

array

An array of JSON objects representing filters to match specific event parameters. Each object in the array is treated as an OR condition, while the key-value pairs within each object are treated as AND conditions.

Format: [{"key1": "value1"}, {"key2": "value2", "key3": "value3"}]

Explanation:

The equivalence_filters field expects an array of JSON objects.
Each object in the array represents a set of conditions that can match an event.
Multiple objects in the array are treated as OR conditions. If any object’s conditions are fully met, the filter matches.
Within each object, multiple key-value pairs are treated as AND conditions. All conditions within an object must be met for that object to match.

Example:

[
  {"_to": "0x788D1B1D001926A735540a685004AF96FFa6b6BE"},
  {"_from": "0x1234567890123456789012345678901234567890", "_value": "1000000000000000000"}
]

Get Started

User Connections

Points Sources

Reward Distribution

Guides

How It Works

FAQ

Usage Tips

Configuration Fields

Get Started

User Connections

Points Sources

Reward Distribution

Guides

​How It Works

​FAQ

​Usage Tips

​Configuration Fields

How It Works

FAQ

Usage Tips

Configuration Fields