Event JSON
{
"id": "7952177c99bb61db22b439b787e3a1e3bd30a5f73a88cad6a5421a89b5666d0d",
"pubkey": "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d",
"created_at": 1729030528,
"kind": 1,
"tags": [
[
"e",
"e05887c3d1b4a9e89fc30822205292da8a980d2789d930c3c5b4442b4481efdb",
"",
"root"
],
[
"e",
"dade9577dcb4371f4158cc48da1484092105a237bc77dae98953254cd69567b4",
"",
"reply"
],
[
"p",
"52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd",
"",
"mention"
],
[
"p",
"916cb5ff07d3b51cef7f6b6b7f5479b1001b401c0e82558ee1a22504c7d507c9",
"",
"mention"
],
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "My take - the take I had adopted for nostr:npub1j9kttlc86w63emmldd4h74rekyqpksqup6p9trhp5gjsf374qlyszvuswx - is that a \"secure element\" does not get in the way of verifiability iff it does never handle the private key material. It may contribute \"true randomness\" and it can be used for a key encryption key but the parts that actually touch the keys must be public source and binaries reproducible and the device itself has to show the actual hash of the binary you are trying to install prior to installation.",
"sig": "dd8ff03a8590f4545eb12c57f8314cd1f8d1a7f23739125f08a17d27266eb76561c10f611734fc619e774b94a4d0aa7b64ae09a05fabf4adf48af0bf774bc14b"
}