cc nostr:npub1acr7ycax3t7ne8xzt0kfhh33cfd5z4h8z3ntk00erpd7zx...

ChipTuner

npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7

hex

eb1cf79265cdaf41d7629532b975d5f2df48aae9c6fd23abb0c7b4a6965f6733

nevent

nevent1qqswk88hjfjumt6p6a3f2v4ewh2l9h6g4t5udlfr4wcv0d9xje0kwvcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsqxefne258ydmfgm2wfl02fsdqgs0d5wx29kweg9amxcqxew4t7kqj8qarh

Kind-1 (TextNote)

2026-04-30T18:34:53Z

↳ Reply to ChipTuner (npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7)

Noscrypt has some changes staged for library updates, these changes remove all of the unused source code of the vendored copy of libsecp256k1, most wa...

cc nostr:npub1acr7ycax3t7ne8xzt0kfhh33cfd5z4h8z3ntk00erpd7zxlqzy3qrn2tqw

I think you should be fine, as it looks like you're building outside of your cmakelists. If you are, and you rely on libsecp256k1, you can either link noscrypt dynamically to it (instead of building static) or you can possibly, if you statically link noscrypt to libsecp256k1, you can just link against noscrypt and save yourself some space. Not sure how you want to play it.

I like to see how libnostr-c has matured lately btw!

Raw JSON

{
  "kind": 1,
  "id": "eb1cf79265cdaf41d7629532b975d5f2df48aae9c6fd23abb0c7b4a6965f6733",
  "pubkey": "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
  "created_at": 1777574093,
  "tags": [
    [
      "e",
      "2419e4f134badb4decc94cda2a941efec4f3239ead48aa1e6b373beccf862bef",
      "wss://relay.primal.net/",
      "root",
      "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58"
    ],
    [
      "e",
      "2419e4f134badb4decc94cda2a941efec4f3239ead48aa1e6b373beccf862bef",
      "wss://relay.primal.net/",
      "reply",
      "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58"
    ],
    [
      "p",
      "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
      "wss://relay.primal.net/"
    ],
    [
      "p",
      "ee07e263a68afd3c9cc25bec9bde31c25b4156e71466bb3df9185be11be01122"
    ]
  ],
  "content": "cc nostr:npub1acr7ycax3t7ne8xzt0kfhh33cfd5z4h8z3ntk00erpd7zxlqzy3qrn2tqw \n\nI think you should be fine, as it looks like you're building outside of your cmakelists. If you are, and you rely on libsecp256k1, you can either link noscrypt dynamically to it (instead of building static) or you can possibly, if you statically link noscrypt to libsecp256k1, you can just link against noscrypt and save yourself some space. Not sure how you want to play it. \n\nI like to see how libnostr-c has matured lately btw! ",
  "sig": "def75b91257abde6918d99363f07799b0db4e9c4ad4bfe4f91cd86580c849f4d31f608bff03a625942ca972504e41280217623b1263e6a0174ab41885a9355b4"
}