chadlupkes on Nostr: Hashed content cannot be altered after the fact. So I think it's an important option ...
Hashed content cannot be altered after the fact. So I think it's an important option that we would want to explore. A good example of a protective hashed system is IPFS, which saves content hashes for any size file. I've been wondering if something like that could be used on Nostr or integrated with Nostr at some point.
Published at
2024-11-01 00:04:27Event JSON
{
"id": "43d6276ca97615f21411cf250ab7d9abf97e5d1c56d7364e991d3107516a58a7",
"pubkey": "df06d21eca7c19c89d054964b2d9e305a425ebde34403cb0e7966a872b23058f",
"created_at": 1730419467,
"kind": 1,
"tags": [
[
"e",
"0000f796edd1b69b337cd5dccdd9818afe86007baa686f03331ca464e407b753",
"",
"root"
],
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49"
]
],
"content": "Hashed content cannot be altered after the fact. So I think it's an important option that we would want to explore. A good example of a protective hashed system is IPFS, which saves content hashes for any size file. I've been wondering if something like that could be used on Nostr or integrated with Nostr at some point.",
"sig": "fb1fa7ad728cb75efad605efb69017747f3de7d1c73dd1c48b0042713e5ca1bf40d90fc440bbfe56d78dc00c50748fdcbfaa2621de83e1c489bd772b3ccf5dde"
}
