Version 1.8.7 and earlier contained a memory corruption bug in the realtime package used for traffic shaping. Under specific conditions, a malformed input could lead to a panic (DoS) or potentially memory corruption. Xray 1.8.8 backported a hardened bounds checker, eliminating that vector.

If you could provide more context or clarify what "prepare a piece" entails in your scenario, I could offer more targeted advice.

By late 2023, Xray had already cemented its position as the de facto choice for circumvention and private network routing. Version 1.8.x represented the "mature" branch, prioritizing reliability over experimental features. Xray 1.8.8 arrived as a direct response to two pressing needs: