Some meaningful changes in the PeerDAS design have been discussed, and agreed upon, at the interop:
Do not use the tight fork-choice in the first iteration of PeerDAS
Increase custody requirement and subnet count
Introduce validator custody
Take peer sampling completely out of the critical path of consensus
In my opinion, they represent both a huge simplification and an increase in robustness of the design. Let's break down what these points mean and why that is the case.
Trailing fork-choice instead of tight fork-choice