2dust/v2rayN

Choose this fork only if you need the Hiddify-specific Windows workflow and can accept substantial lag behind upstream. If you want current protocol support, active maintenance, or cross-platform parity, upstream v2rayN is the safer choice.

Prefer upstream unless you need this fork's exact legacy/custom routing and configuration behavior. This fork looks useful for niche, path-dependent deployments, but its age and divergence make it a poor default choice for new installs.

Choose this fork only if Trojan support on this older codebase is the main requirement. For most users, upstream v2rayN is the better default because this fork is stale and materially behind on newer features and fixes.

Choose this fork if you want an upstream-current v2rayN with promotions and automatic updates stripped out; skip it if you rely on built-in update convenience or want the broader upstream ecosystem.

Choose this fork only if you specifically want a Windows-only, heavily customized variant and can accept major upstream lag. For most adopters, upstream v2rayN is the safer choice because it is active, broader in platform support, and much more current.