[Bug] No verifiable method for operators to confirm active participation and reward eligibility

[maslitti]

Summary

EigenLayer operators currently have no clear or verifiable method to confirm whether their operator is actively participating in the protocol and eligible for rewards.

While an operator may appear registered and running, there is no observable proof that it is being recognized as active by the system.

---

Expected behavior

Operators should be able to verify that:

• their operator is actively participating
• uptime or activity is being tracked
• the operator is eligible for rewards

This should be observable through on-chain state, metrics, or publicly documented verification methods.

---

Actual behavior

In the current design:

• operators can be registered and delegated to
• services may be running normally
• no explicit errors are reported

However:

• there is no clear indicator of active participation
• no uptime or heartbeat visibility
• no confirmation of reward eligibility
• no public dashboard or API confirming operator activity

As a result, an operator can appear correctly configured while not being verifiably counted as active.

---

Impact

Without a verifiable participation signal:

• operators cannot confirm whether they are contributing to network security
• reward eligibility cannot be independently validated
• inactive or misconfigured operators may go unnoticed
• incentive transparency is reduced

This creates uncertainty for operators and complicates trust in the incentive mechanism.

---

Steps to reproduce

1. Register an EigenLayer operator following official documentation.
2. Complete delegation and configuration steps.
3. Observe that the operator appears registered and running.
4. Attempt to verify whether the operator is actively participating or eligible for rewards.
5. Note that no clear or verifiable confirmation mechanism exists.

---

Suggested solution

Provide a verifiable method for operators to confirm active participation, such as:

• explicit on-chain activity or heartbeat indicators
• publicly accessible participation or uptime metrics
• documented APIs or dashboards confirming reward eligibility