jimbocoin on Nostr: Such a scheme could be developed. It would require publishers to somehow hash their ...
Such a scheme could be developed. It would require publishers to somehow hash their posts into the timechain (like with opentimestamps). Then clients (and optionally relays) would check for these hashes and assert that they preceded the pre-specified height.
Not impossible, but it would take some backend work to implement, and front end work to design a UX for both publishers and readers.
Published at
2024-07-02 17:38:28Event JSON
{
"id": "8c9ff228a50e25d1a58a2b303bd46cb27fb2be38524e4dc3a878bc08a5900e56",
"pubkey": "6140478c9ae12f1d0b540e7c57806649327a91b040b07f7ba3dedc357cab0da5",
"created_at": 1719941908,
"kind": 1,
"tags": [
[
"e",
"0132e2c2540aa354d3ba975ae8bbe10f8c9505e5ee86881f59498e1f94e0150f",
"",
"root"
],
[
"p",
"34134b9e1cbb322582bca4020a39cc1256036d1f5e98effcc838b421fc209d48"
]
],
"content": "Such a scheme could be developed. It would require publishers to somehow hash their posts into the timechain (like with opentimestamps). Then clients (and optionally relays) would check for these hashes and assert that they preceded the pre-specified height.\n\nNot impossible, but it would take some backend work to implement, and front end work to design a UX for both publishers and readers.",
"sig": "a60e6c3687208a9acf0ae550fbf6156105cc0134f7b022572876e2ccf655bbb4af1b73a68d5fad8be57a2b9d37d4d17d4a388ee3771bee1d54b57da082ac7098"
}
