It's mostly about speed for us. Timestamping on BTC takes significantly longer due to longer block times. Of course you could make the argument that one has to wait for more blocks on ETH to get the same kind of security but I think we can agree that this rarely makes a difference in practice and even so it would still be considerably faster.
. . . . . . . . . . . . . . . . . . . . . . . . . . Ing. Patrick Szabo Developer LexisNexis Verlag ARD Orac GmbH & Co KG A-1030 Wien, Marxergasse 25 mailto:patrick.sz...@lexisnexis.at Tel.: +43 1 53452 1514 Fax.: +43 1 534 52 146 . . . . . . . . . . . . . . . . . . . . . . . . . . -----Ursprüngliche Nachricht----- Von: Peter Todd [mailto:p...@petertodd.org] Gesendet: Freitag, 13. Juli 2018 00:55 An: Szabo, Patrick (LNG-VIE) Cc: ots-dev@lists.opentimestamps.org Betreff: Re: [ots-dev] production ready eth server ? On Thu, Jul 12, 2018 at 07:15:55AM +0000, Szabo, Patrick (LNG-VIE) via ots-dev wrote: > Hi, > > I was wondering if there was any way to use ethereum in a production > environment together with ots. > There seems to be an experimental server without much documentation and of > course there are services using the ots protocol, providing an API but I was > wondering if there was any way to run this ourselves, without having to rely > on a third party. I think the question to ask here is why do you need a ETH timestamp? In practice we've found the ETH timestamping infrastructure to be significantly less reliable than BTC. Equally, if you really want a ETH timestamp, why not timestamp the BTC chain with ETH? -- https://petertodd.org 'peter'[:-1]@petertodd.org
