[BIP Draft] Segregated Data: a prunable, script-isolated block region for data carriage

The email raises concerns regarding the implementation of SegData as an alternative to witness stuffing, highlighting that although both processes incur similar costs, SegData offers reduced data availability. This poses a significant question about its attractiveness to users who are interested in embedding data within blockchain technology. The skepticism is further reinforced by the observation that there is generally a lack of interest in enhancing support for data embedding, which could diminish the perceived value of pursuing such a change through a softfork.

The sender questions the rationale behind opting for SegData when it does not present clear advantages for its intended users. This critique is rooted in the practical implications of adopting new technologies or methodologies in blockchain operations, especially when such changes do not evidently align with user demands or enhance functionality. The essence of the inquiry is to challenge the justification of investing in and advocating for technological shifts like SegData, particularly under circumstances where potential benefits are overshadowed by drawbacks such as reduced availability of data.