---
# System prepended metadata

title: EigenDA - Clarifying Questions

---

# EigenDA - Clarifying Questions


### Q: How does EigenDA earn revenue at the moment? Are the L2s which committed to use it, actually paying for service? If so, are these onchain operations that you can point us to fee handler contract or explain how that process works?

### A:


### Q: Is there some data or resource that shows the tx costs using EigenDA vs batching direct to ethereum? What is the main kpi? Should it be tx fees on the L2?

### A:


### Q: Apart from points program native to EigenLayer, is there any plan for a native token, points program or another incentivization mechanism for EigenDA specifically that can be shared publicly?

### A:


### Q: Question about the disperser- this appears to be a centralized service operated by EigenLabs but in a blog post it references this component being something client rollups can operate themselves or setup optimistically to fallback to their own disperser. Is this something open source now that clients can run themselves and is there any integration right now we can point to where this is the case? Or so far rollups are relying on EigenLabs to operate this service with maybe plans to operate their own in the future?

### A:


### Q: According to the SLA NOs can be ejected for poor performance. How is that ejection process managed? Is it programmatic or based on internal monitoring and handled by EigenDA team or some privileged committee/address?

### A:


### Q: Can you elaborate on the EIGEN delegation logic? Is it an established rule that EIGEN should be automatically delegated to the same operator to whom the primary ETH delegation was made?

### A:


### Q: Does slashing veto committee have an authority over EIGEN slashing conditions or EIGEN stakes cannot be slashed at all?

### A:

### Q: Who concludes that a node operator's input is invalid? it seems that this is done by the Disperser? and is done off-chain, before calling the `EigenDAServiceManager.confirmBatch()` function? --> if so, if the NOs input is found to be invalid by the off-chain service, how does it trigger penalties?


