jb55 on Nostr: i don’t think high throughput and efficient processing of private nostr data is ...
i don’t think high throughput and efficient processing of private nostr data is compatible with the async signer model.
in nostrdb we have ndb_add_key which pushes private keys to the ingester threads so that they can efficiently unwrap giftwraps with optimal performance.
I can’t imagine how this would work with a remote signer doing decryption.
Published at
2025-11-28 05:08:30 UTCEvent JSON
{
"id": "7c8c6c1110c5faa6c827d40a0d620dc95ee8bbbd7026b38dcc907a89b7799fe1",
"pubkey": "32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
"created_at": 1764306510,
"kind": 1,
"tags": [],
"content": "i don’t think high throughput and efficient processing of private nostr data is compatible with the async signer model.\n\nin nostrdb we have ndb_add_key which pushes private keys to the ingester threads so that they can efficiently unwrap giftwraps with optimal performance.\n\nI can’t imagine how this would work with a remote signer doing decryption.",
"sig": "2f8f81f8451d59403445778e6a062a4cf7a1b76d10c533054713c9ccc7250209cc5eec4544773aafdf2e5961885847a744d1b89e9df7d4ecde5eb44bb8a12e01"
}
