Tim Beiko pointed out that EOF Option A had unexpectedly severe negative consequences on developer experience
Claim
Quotes that support claims
Shortly before ACDE#210, some core developers realized that their preferred EOF Option (Option A) had unexpectedly significant negative developer experience consequences. While these had been flagged before, their magnitude hadn’t been fully appreciated. Client teams agreed to urgently review these implications and resolve them by the next Testing/Interop #34 call.
Referenced by
Challenges revealed by the EOF and Fusaka situation
Crypto news
Data block