Helius expands pre-confirmation permissions; earlier signals require clearer state boundaries. Low-latency tools can improve responsiveness, but the product must know when to consider an action complete. ① On October 17 (Beijing Time), Helius announced that its pre-confirmation feature is now available to all paid plans, adding four new filtering capabilities: source, signer, signatures, and instructions. This week’s update expands both availability and filtering functionality. ② For applications that need to track specific signers or instructions, filtering reduces irrelevant messages, enabling programs to receive relevant signals earlier. However, this feature is not universally available on free plans, nor is it new this week. ③ Documentation distinguishes between stages of different signal sources: notifications after local execution differ in contained state information from those received before execution. Developers cannot ignore the specific meaning of signals merely because they arrive earlier. ④ Pre-confirmation does not equal final settlement. Application design must account for scope coverage, potential duplicate notifications, connection recovery, and the eventual final state—especially when displaying balances or delivering assets. My own assessment: The value of such features depends on whether the business can correctly leverage the early notice. I’d prefer to see clear “pending confirmation” indicators and robust error recovery, avoiding user confusion caused by interfaces that appear too fast and imply irreversibility. @Solana_zh @solana @Helius