pkt on Nostr: Nah, that was a useful fight. Especially the email I linked to above. In a different ...
Nah, that was a useful fight. Especially the email I linked to above. In a different timeline Chainpoint might have gotten W3C standardization, screwing over OpenTimestamps adoption. By arguing publicly I was able to make clear to everyone that Chainpoint just wasn't a good protocol, and OTS was.
Re: the binary format, it is documented. Read the protocol spec, the python-opentimestamps library. Though there's little reason to unless you're writing your own OpenTimestamps library; if you aren't, just use an existing library.
Published at
2024-12-24 10:22:57Event JSON
{
"id": "d9152700e3223323e7adf66cbb89673a6d537b636305b3ba6fe58b17c45b289b",
"pubkey": "ccaa58e37c99c85bc5e754028a718bd46485e5d3cb3345691ecab83c755d48cc",
"created_at": 1735035777,
"kind": 1,
"tags": [
[
"e",
"20c8ad3862beb3cb16344cd83b97629fc6edc5b99ae56a7e3608d5317ff0176b",
"",
"root"
],
[
"e",
"fb0654a428d1c06e14468980cd1359703247ea80f4b0c62985f3f30594747bd6",
"",
"reply"
],
[
"p",
"ccaa58e37c99c85bc5e754028a718bd46485e5d3cb3345691ecab83c755d48cc"
],
[
"p",
"c654525862af6bfee2ebd951a568e16f3be534a7d9aad352c0227a24d90ac91a"
]
],
"content": "Nah, that was a useful fight. Especially the email I linked to above. In a different timeline Chainpoint might have gotten W3C standardization, screwing over OpenTimestamps adoption. By arguing publicly I was able to make clear to everyone that Chainpoint just wasn't a good protocol, and OTS was.\n\nRe: the binary format, it is documented. Read the protocol spec, the python-opentimestamps library. Though there's little reason to unless you're writing your own OpenTimestamps library; if you aren't, just use an existing library.",
"sig": "283f1ceac7ad8dabfd465c5d9d1a890854edc96e11b94e69ae953ab6150fa2854ed33847fefa99a494d02f11efae05d89b4381ae5e6fa8d99c4fb5b0461a6fc7"
}
