Noscrypt has some changes staged for library updates, these changes remove all of the unused source code of the vendored copy of libsecp256k1, most was already removed, but trimmed further. I also removed headers of unused modules.
Noscrypt symbols are unchanged, and the only symbol change to the libsecp256k1 ABI would be disabling the musig module. If, for whatever reason, you depended on noscrypt for those libsecp256k1 symbols, they will be gone in v0.1.14.
Same goes if you relied on those headers for whatever reason (the modules were never enabled, so linking would have failed anyway).
https://github.com/VnUgE/noscrypt/compare/develop...feature/no-ref/update-libsecp
ChipTuner
npub1qd…3fqm7
2026-04-30 18:30:44 UTC
Author Public Key
npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7Published at
2026-04-30 18:30:44 UTCEvent JSON
{
"id": "2419e4f134badb4decc94cda2a941efec4f3239ead48aa1e6b373beccf862bef",
"pubkey": "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
"created_at": 1777573844,
"kind": 1,
"tags": [],
"content": "Noscrypt has some changes staged for library updates, these changes remove all of the unused source code of the vendored copy of libsecp256k1, most was already removed, but trimmed further. I also removed headers of unused modules. \n\nNoscrypt symbols are unchanged, and the only symbol change to the libsecp256k1 ABI would be disabling the musig module. If, for whatever reason, you depended on noscrypt for those libsecp256k1 symbols, they will be gone in v0.1.14. \n\nSame goes if you relied on those headers for whatever reason (the modules were never enabled, so linking would have failed anyway). \n\nhttps://github.com/VnUgE/noscrypt/compare/develop...feature/no-ref/update-libsecp",
"sig": "3bd48ee1d76ef15117f76c5f1108f0eaa2e8e17e7b7415e3e1931c38d8fca4ff40d850139b951104d60d5d8ff1452334524bed18424d5293b26b35b25ab330b8"
}