Avail Intern

great points ser, but i think it is a nice wordplay. ———————- You took out all the limitations/disadvantages of eigenDA and pinned it all on the architecture design. It may very well be one great design and possibly fits the Eigen ecosystem, but what about multiple tradeoffs and issues that are faced at the same time? ———————- 1. the obvious centralization risk: There is no decentralization, which means single point of failure. Unless the design has some kind of mechanism to avoid that. in EigenDA's DAC design, the operators form a trusted committee that make data available, but end users or apps cannot verify independently. Another issue from your own docs is the disperser itself. This is responsible for encoding blobs, right? However it is centralized and pose a threat to system liveness. there is also no information about the 200+ operators decentralized network where data is being stored (saw a comment down below) 2. You said that there is no censorship choke point, I might be wrong but dont you think this design gives it more chances for censorship? As you scale, a group of nodes could collude to suppress/manipulate the data without immediate detection. This becomes a bigger issue since, as mentioned above, end users/apps cant verify the data. On penalties and forking, check 3rd point plz. "Add on self-verifiability: anyone can sample chunks from the network to check for verifiability. Light nodes can be implemented on top of this." -- I see this, but how does it really work out because without widespread availability of data, LCs may struggle to obtain sufficient samples to verify data integrity confidently. 3. "EIGEN forking: if data is not available by majority collusion, the EIGEN token can fork to impose cryptoeconomic penalties." -- I like this. Currently only thing that is guaranteed is economic guarantees not the data, but sadly it may not matter much if malicious actors can profit more in the short term. please correct me if im wrong here. 4. Having no leader as compared to traditional DAs may cause issues and delays due to coordination and data retrieval as network scales at an exponential rate. How is that handled? 5. There is still no DAS which makes it harder for user verification compared to what you said earlier. Maybe there was an acknowledgement of not having it, but this doesn't make Eigen better than other DA solutions. All in all, i think EigenDA, which is NOT a chain btw (need to clarify because people on CT confuse and are swayed because of marketing) has features that may fit the eigen ecosystem, but doesn't solve most of the issues. A lot of people on CT has a wrong view on why to choose X over Y, and I hope they read all the tradeoffs from you and other folks and choose what fits their needs best.