{"type":"rich","version":"1.0","title":"pistachio3 wrote","author_name":"pistachio3 (npub1e9…5khp0)","author_url":"https://nostr.now/npub1e9lvdx8ypf2hn0gmvd9lz5vdkexg40m5jcxnek5mk36e7cj75hjqm5khp0","provider_name":"njump","provider_url":"https://nostr.now","html":"#asknostr does anyone know if the nostr:nprofile1qqs09jtvjlmyrxjn37zv70a89csegcz7rpyqjmnw29cveedhv7vagqqpzfmhxue69uhk7enxvd5xz6tw9ec82cspr3mhxue69uhkummnw3ez6un9d3shjtnhd3m8xtnnwpskxegdzx7vp generates a sufficiently random nonce K during signing transactions? I understand that a private key can be derived from a reused nonce k or weak nonce k. Does sparrow mitigate this issue? Looking to understand a little more about the security of a seedsigner multisig set up. Thanks!"}