The Plight of Secure Elements

npub1lnms53w04qt742qnhxag5d6awy7nz6055flnmjkr6jg39hm86dlq7arrnt
hex
fcdf161fb70d33fb55b553e0d8716bdccdf829b945c5c48402a5365516e4ac96nevent
nevent1qqs0ehckr7ms6vlm2k648cxcw94aen0c9xu5t3wyssp22dj4zmj2e9sprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs0eac2gh86s9l24qfmnw52xawhz0f3d862yleaetpafygjmanaxls8hhaa2Kind-1 (TextNote)
The Plight of Secure Elements
Most wallets that use secure elements have had to switch to version 2 of their hardware due to defects in the secure elements themselves.
In other words, if a vulnerability is found in the secure element, your HWW cannot be updated.
This doesn’t happen with the Jade architecture, because everything is software—if a bug appears, it gets patched.
All HWW manufacturers should stop using those crappy secure elements and adopt the Jade model—a 2-of-2 multisig to encrypt the seed (PIN-blind Oracle).
Even in models where the seed can be extracted, such as the Trezor 1 and Trezor T, the PIN-blind Oracle could be implemented, making them fully up-to-date devices.
But no one cares about that—it’s all about planned obsolescence.
原始 JSON
{
"kind": 1,
"id": "fcdf161fb70d33fb55b553e0d8716bdccdf829b945c5c48402a5365516e4ac96",
"pubkey": "fcf70a45cfa817eaa813b9ba8a375d713d3169f4a27f3dcac3d49112df67d37e",
"created_at": 1787207401,
"tags": [
[
"r",
"wss://nostr-pub.wellorder.net/"
],
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://premium.primal.net/"
],
[
"r",
"wss://relay.momostr.pink/"
],
[
"r",
"wss://relay.primal.net/"
],
[
"r",
"wss://relay.nostr.net/"
],
[
"r",
"wss://bcast.girino.org/"
],
[
"r",
"wss://nostr.mom/"
],
[
"r",
"wss://relay.coinos.io/"
],
[
"r",
"wss://relay.ditto.pub/"
],
[
"r",
"wss://relay.nos.social/"
],
[
"r",
"wss://relay.mostr.pub/"
],
[
"r",
"wss://offchain.pub/"
],
[
"r",
"wss://nostr.bitcoiner.social/"
],
[
"client",
"Primal Web"
]
],
"content": "The Plight of Secure Elements\n\nMost wallets that use secure elements have had to switch to version 2 of their hardware due to defects in the secure elements themselves.\n\nIn other words, if a vulnerability is found in the secure element, your HWW cannot be updated.\n\nThis doesn’t happen with the Jade architecture, because everything is software—if a bug appears, it gets patched.\n\nAll HWW manufacturers should stop using those crappy secure elements and adopt the Jade model—a 2-of-2 multisig to encrypt the seed (PIN-blind Oracle).\n\nEven in models where the seed can be extracted, such as the Trezor 1 and Trezor T, the PIN-blind Oracle could be implemented, making them fully up-to-date devices.\n\nBut no one cares about that—it’s all about planned obsolescence.\n\n",
"sig": "e721c2ce5ffa9c190c7c922b4346f23590fc0a596511927d3ff04e3852ab0405a235c6dec7f41463024f7856b69388370179ae1f08959f5d8580366de96fc0db"
}