?ed=2048 | outdated
?ed=2560 | 0-RTT - http3+tls1.3 - web3 connectivity support - .crypto top domain resolve for unstoppable domains - faster api connectivity + better handling for closing unsecure tcp connections while upgrading from 80 to encrypted 443 (Upgrade-Insecure-Requests). old 2048 had issue with closing video stream connections but this one is legit for user actions in streams.
I recommend you remove early data on your vless config path, its trash, disadvantages are a lot but the only advantage -100ms for responsing, not worthy at all. limits most of DoH-DNS to resolve themselves, the goal of setting early data is for reduce latency ONLY on first tcp connection, which can reduce ping like 100-200ms when opening an app or a site w/api support, but adds tons of errors and limitations... it also affects download speed when you downloading with an advance downloader like IDM which can split the file to 32 parts for parallel downloads, with early data it can't even handle 8 connections properly, hangs like crazy, dl rate & ping leaps a lot and jitter jitter jitter... this error also happens when you have a lot of open connections or multiple open tabs/apps.
just use standard / for path and thank me later when you understand how early data works )