[BIP Proposal] Limit ScriptPubkey Size >= 520 Bytes Consensus.

ScriptPubKeys, a component of Bitcoin's scripting system, are not being utilized for data storage beyond 520 bytes. This observation suggests a shift in the practices within the Bitcoin community, where innovative methods for encoding data into transactions have emerged. A notable example of such innovation is the inclusion of a Merkle path in the taproot control block. This development implies that traditional uses of scriptPubKeys for data storage might be becoming obsolete, as users explore new ways to leverage Bitcoin's transaction capabilities.

Furthermore, the broader implications of this trend could potentially impact users who still prefer or intend to use scriptPubKeys for data storage purposes. The decrease in its use for large data storage signals a change in user preferences and technological adaptations within the Bitcoin network. Additionally, the reference to a transaction on mempool.space illustrates a practical example of how data storage practices are evolving in real-world applications. This shift highlights the dynamic nature of Bitcoin's technological infrastructure and the continuous search for more efficient and effective methods of utilizing its features.