Skip to main content

Frequently Asked Questions

TODO: Complete FAQ​

Common questions and quick answers.

General Questions​

Q: What is EigenWatch? A: EigenWatch is a risk telemetry system for EigenLayer restaking. It monitors operators and provides real-time risk scores, slashing alerts, and reputation data.

Q: Is EigenWatch open-source? A: Yes, the code is available on GitHub. [Link to be added]

Q: Who built EigenWatch? A: [Team information to be added]

Risk Scoring​

Q: What does a risk score of 42 mean? A: It means the operator is in the medium-risk category (21-50). See Risk Scoring for details.

Q: Can a low-risk operator still get slashed? A: Yes. Risk scores reflect historical patterns and current state, but cannot predict all future events. See Data Limitations.

Q: How often do risk scores update? A: Risk scores update in real-time when relevant on-chain events occur. See Risk Scoring for details.

Q: Can I use EigenWatch risk scores to make trading decisions? A: Yes, many users do. But you should also do independent research and not rely solely on EigenWatch.

Slashing​

Q: What is slashing? A: Slashing is when an operator's stake is forfeited due to malicious or faulty behavior. See Restaking Risks.

Q: If my operator gets slashed, does EigenWatch refund me? A: No, EigenWatch is a data provider, not insurance. For insurance products, see Insurance Integration.

Q: How does EigenWatch detect slashing? A: EigenWatch monitors on-chain events. Slashing is detected when the event is recorded on-chain.

Using EigenWatch​

Q: How do I query operator risk scores? A: Use the REST API or WebSocket. See Risk Scoring API for details.

Q: Do I need an API key? A: Yes, API keys are required for all queries. See API Overview.

Q: What's the rate limit? A: Rate limits depend on your tier. See API Overview for details.

Q: Can I download all the data? A: Bulk data exports are available for paid tiers. Contact support for details.

Integration​

Q: How do I integrate EigenWatch into my protocol? A: See the integration guide for your use case:

Q: Can I use on-chain oracle data? A: Yes, see Oracle Feeds.

Q: What's your SLA for API uptime? A: See SLA.

Data & Privacy​

Q: Is EigenWatch data real-time? A: Mostly. There is some latency from on-chain event to API/oracle publication. See Data Latency.

Q: How long do you keep historical data? A: See Historical Data.

Q: Can you deanonymize operators? A: Operator addresses are publicly on-chain. EigenWatch does not perform additional deanonymization.

Q: What data does EigenWatch collect about me? A: Only API usage data (queries, rate limiting). See Privacy Policy (link to be added).

Troubleshooting​

Q: I'm getting 429 (rate limited). What do I do? A: You've exceeded your rate limit. Upgrade your tier or wait for the limit to reset. See API Overview.

Q: The API is returning 404 for an operator. Why? A: The operator address may be incorrect, or the operator may not yet be indexed. Check the address format.

Q: My alert didn't fire. Why? A: Check your subscription configuration. See Alerts API.

Q: I see different risk scores in different systems. Why? A: Different systems may use different methodologies. Confirm you're comparing data from the same time.

More Questions?​

Check out:

Status: NOT STARTED — Requires UX research & product expertise