📅 Original date posted:2018-01-30
📝 Original message:On Mon, Jan 29, 2018 at 09:54:23PM +0000, Gregory Maxwell via bitcoin-dev wrote:
> If times need to be accurate Bitcoin would need to use a rather
> different design (e.g. each block would commit to the observation time
> of the prior N blocks, and an iterative algorithm would solve for each
> blocks time and each miners local offset).
>
> IIRC open-timestamp calendar servers provide more precise
> time-stamping under the assumption that the calendar server is
> behaving correctly.
That is incorrect. The OpenTimestamps servers are specifically designed not to
be trusted, and thus do not make any cryptographically verifiable attestations
as to when timestamps were created.
In the future I expect to add a trusted timestamping scheme via disposable keys
to the OpenTimestamps protocol, but that work isn't yet complete:
https://lists.opentimestamps.org/pipermail/ots-dev/2017-May/000001.html
--
https://petertodd.org 'peter'[:-1]@petertodd.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180130/ebd74375/attachment.sig>;
Peter Todd [ARCHIVE] /
npub1m2…a2np2
2023-06-07 18:10:24
in reply to nevent1q…hslw
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Published at
2023-06-07 18:10:24Event JSON
{
"id": "7ca7afe102b4e163e81deeae003bc80d3e9c8c875b6871870a8a5df514c368e0",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686161424,
"kind": 1,
"tags": [
[
"e",
"88c58d5589d7722de84cdc11e2eba2693b3168f189e3827879c0e97e565301e9",
"",
"root"
],
[
"e",
"5b1f6fc9b98d3e511336ffcfd62e3bdb63aa9e355fab87960f780350f1255283",
"",
"reply"
],
[
"p",
"4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73"
]
],
"content": "📅 Original date posted:2018-01-30\n📝 Original message:On Mon, Jan 29, 2018 at 09:54:23PM +0000, Gregory Maxwell via bitcoin-dev wrote:\n\u003e If times need to be accurate Bitcoin would need to use a rather\n\u003e different design (e.g. each block would commit to the observation time\n\u003e of the prior N blocks, and an iterative algorithm would solve for each\n\u003e blocks time and each miners local offset).\n\u003e \n\u003e IIRC open-timestamp calendar servers provide more precise\n\u003e time-stamping under the assumption that the calendar server is\n\u003e behaving correctly.\n\nThat is incorrect. The OpenTimestamps servers are specifically designed not to\nbe trusted, and thus do not make any cryptographically verifiable attestations\nas to when timestamps were created.\n\nIn the future I expect to add a trusted timestamping scheme via disposable keys\nto the OpenTimestamps protocol, but that work isn't yet complete:\n\nhttps://lists.opentimestamps.org/pipermail/ots-dev/2017-May/000001.html\n\n-- \nhttps://petertodd.org 'peter'[:-1]@petertodd.org\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 488 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180130/ebd74375/attachment.sig\u003e",
"sig": "68d0e8de5d947206d52afd29ed5bfede635e626448c9695fc86c2c3a13c97a746762c02c7bd1ca534ca6149eb6ad2ba95e9df6b1419f9ba26ab0afefe1500cf5"
}