Ryan on Nostr: It would be great for this to be implemented. Just like how you can create a new ...
It would be great for this to be implemented. Just like how you can create a new Bitcoin address for every transfer, you could create a new key for every Nostr login, while keeping your actual nsec private and secure. As it works currently every login with your nsec is like typing in your 24 word backup into Internet connected software. There is a lot of trust involved there. If you could create keys with the possibility of invalidating them if a client app goes rogue it would get rid of that trust issue.
Published at
2025-02-23 13:59:24Event JSON
{
"id": "4feb162b6af31881239ff94314b1f596ba9fd74355018fffc9948b52ae9ac716",
"pubkey": "deab79dafa1c2be4b4a6d3aca1357b6caa0b744bf46ad529a5ae464288579e68",
"created_at": 1740319164,
"kind": 1,
"tags": [
[
"e",
"29413c90fa8454491c5256edfa63136224d906e6a6f3bf82e81f06d4cff9401c",
"",
"root"
],
[
"p",
"26e9ab7f2c8d2ac37903af90be2a1aef6f2acbd699f4f259caac7ad33d2000c1"
]
],
"content": "It would be great for this to be implemented. Just like how you can create a new Bitcoin address for every transfer, you could create a new key for every Nostr login, while keeping your actual nsec private and secure. As it works currently every login with your nsec is like typing in your 24 word backup into Internet connected software. There is a lot of trust involved there. If you could create keys with the possibility of invalidating them if a client app goes rogue it would get rid of that trust issue.",
"sig": "3148c2d4af07296ef744f2c0e4285da0ed5bc0e0893d7de1d98121f5a2c4e7ca08c882274255412e05e71feeb4d32665b8031dc5c53ae8a982c0854a9a6a627b"
}
