# Restaking Analytics

There's no standard way to track and report how well validators are performing their duties. By creating and encouraging the use of a common method to measure and share this performance data, we can help services that rely on validators work more effectively and reliably.

**Partners** 

<div align="left"><figure><img src="/files/JlmA4EBPZdEvW4JJiqHZ" alt=""><figcaption></figcaption></figure></div>

* **Space & Time**: We can leverage Space and Time’s proof of SQL to store the rule sets governing rewards and penalties (for example: all transactions need to be processed in under X seconds).&#x20;
* **Lava**: We can use Lava Network to connect to blockchains in order to pull down the data we need about Operator actions.&#x20;
* **Cube3**: We can use Cube3 to get data about Operators in order to ensure interactions with whitelisted/blacklisted entities are occurring properly.

**Example Use Case**\
\
An Operator Set triggers a slashing event for an underperforming operator who failed to process transactions within the required time window. The system automatically aggregates the rule violations, pulls relevant blockchain data, checks the operator's reputation, and provides a comprehensive analytics package to a security provider like EigenLayer for transparent decision-making.

**Benefits**<br>

* Transparent rule enforcement through verified SQL-based governance
* Real-time monitoring of operator actions and performance metrics
* Automated compliance checking through reputation tracking
* Immutable on-chain record of all operator evaluations

**Sequence For Slashing Notification**

Trigger: An Operator Set triggers the slashing of an Operator.

{% stepper %}
{% step %}
Space and Time (SxT) aggregates the appropriate rules governing that event.

{% endstep %}

{% step %}
Lava Network pulls the appropriate on-chain information about the event and shares it with SxT.&#x20;
{% endstep %}

{% step %}
Cube3's vets Operator reputations - flagged if bad actor or on whitelist/blacklist.

{% endstep %}

{% step %}
W3.io aggregates the partner data into a normalized analytics package.&#x20;

{% endstep %}

{% step %}
Space and Time provided analytics package and updates Operator information.&#x20;

{% endstep %}

{% step %}
W3.io batches the analytics package along with the validated series of transactions and puts it on-chain.&#x20;

{% endstep %}

{% step %}
EigenLayer can pull all of the information from on-chain whenever needed.&#x20;

{% endstep %}
{% endstepper %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.w3.io/cookbook/restaking/restaking-analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.