2026-09-12T18:53:30Z https://njump.cloud.vinney.xyz ghost43 https://njump.cloud.vinney.xyz/npub1d4fhy4egr6yxqg3useqsa6tzwaq4v53sn0e30c3lglhv3475qapsrnlal7 https://avatars.githubusercontent.com/u/29142493 https://avatars.githubusercontent.com/u/29142493 https://njump.cloud.vinney.xyz/nevent1qqstz4hawyptsmmycs9y69xgf7xat0t4x0uau8nvt2e4620mkck87gczypk4xujh9q0gscpz8jryzrhfvfm5z4jjxzdlx9lz8ar7ajxh6sr5xzel9xs In reply to <a href='/nevent1qqsv66ys07qzks6z5shwpkxkh7yw2kxwqxv5u4etnxpxmlv0mjxpppcppemhxue69uhkummn9ekx7mp0plmjfx'>nevent1q…mjfx</a><br/>_________________________<br/><br/>Release notes are committed into the git repo, in the RELEASE-NOTES file, and distributed as part of the release tarballs.<br/><br/>We don&#39;t consider the &#34;github releases&#34; feature to be safe enough. Anyone with write permissions on the git repo can edit existing &#34;releases&#34; or create new ones, so compromising a single account or blackmailing a single person would be sufficient to put malicious binaries there. In contrast, the electrum(.)org website is set up to be safe from single-account compromise.<br/>(see &#34;Website and release security&#34; at <a href="https://electrum.org/#about">https://electrum.org/#about</a> ) 2026-09-12T18:27:55Z