
SV2 Apps add Bitcoin Core v32 support and block submission over IPC, and continue addressing @ProjectLoupe findings across Pool, JDS, JDC and Translator Proxy. Protocol library highlights include hardening of buffer_sv2, codec_sv2 and framing_sv2, message field renames to match the spec, and support for application-supplied jobs in channels_sv2. All changed published crates introduce breaking changes except noise_sv2, so downstream consumers should review the release notes when upgrading. SV2 UI adds experimental Telegram notifications, multiple custom pools, clearer fallback pool status, and improvements to onboarding, logs and recovery. Setup now supports Bitcoin Core v32. Findings from @ProjectLoupe continue to guide security improvements across the stack. Thank you to the Loupe team and everyone helping turn those findings into fixes! This milestone introduces our SV2 interoperability project, a new effort to test protocol compatibility across different SV2 implementations. The goal is to catch interoperability issues early, make it easier for implementers to validate their software against the spec, and help ensure different SV2 implementations work reliably together. Contributions and feedback are welcome!












