Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 45FB9C002D for ; Tue, 14 Jun 2022 11:53:32 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 2654D408F3 for ; Tue, 14 Jun 2022 11:53:32 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 546O9iDbrD9F for ; Tue, 14 Jun 2022 11:53:31 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) by smtp2.osuosl.org (Postfix) with ESMTPS id 8314D405B3 for ; Tue, 14 Jun 2022 11:53:31 +0000 (UTC) Received: by mail-yb1-xb2c.google.com with SMTP id p13so14760623ybm.1 for ; Tue, 14 Jun 2022 04:53:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=DjWch8zLLqcfGqKkYuScNF0tx4HIhAsxPHZOk0fpQpI=; b=RugsyZRZ9pMYJPKNlS8VN9JZWEV8RruQxd+2ed5ZIaMMa1DKuRdbERFPWEhUreYg1m yt9XzcZXkNnm/XAi9ZlQkng5bcW+5OVjjlzRnzsUVK/eua+tRoPEXIvoV8BNkANQ9W3f EwhD7ST2ldWG3PFdgAl2GKN0LjrW44Uw0amV84pc4g/1oEp3AmHAbLeiM5rQVeQbDfbH G8U3gZbrTBBZuxGkiSfcJbPt0Mo/NAo4Gvd5/VtRF6qD+b2ZAVXwXdABfDqg8Tww6ZrU QXxp3sMG/9Kfcmj5lVIdX95I0KDaZExdMUqwNrVf7EXCqa0n9BjyqS4wOKpZE8TVIbeT re/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=DjWch8zLLqcfGqKkYuScNF0tx4HIhAsxPHZOk0fpQpI=; b=tTbFKqe4beHeVlX92xDDohTk23Fp0BElAYxzXLnoQAghfrkvFJbHuqTp1cvhwMNSh6 rDp/bfPr6m0bS6mA0j8FpKFPX6Anrsv9f1pNzDWB3EEJDd1M5GmxiRtkgSmtpo/lTOoF CXrehrWDp2HQkqDumVn6Tm3BhnttG+TUwJnz6sM9jOIWkFBPLDJnXYOS9Mh52X7Sc2dP WL/39aIyROQGAd6/6lxRT2mNS5ylm1+TX1XH3A0RV2IGqKZzUkHzhHy9zcABrfOQxhXq T9JFYyGpBzDiMwPR3q0JaAaQfIO8A+cQat88AwIcYel31FMFzC8IupwWgWWbxIvEgiNw KnLg== X-Gm-Message-State: AJIora95aPrl43z73yzwlJ7Kh1BmsSFS2Op+mXMr9GJL5Bzg7KGTuig0 m/CvXFRGiX4oKCbGHta/zEs/DLFMoyGsaTfDOAsbTBFa45s= X-Google-Smtp-Source: AGRyM1sm33xzawEtk97IukPZ5MgV/OCvnh1fxxxRXqifDu/oCHPcfGAHhk6er737l5Td6HdeyN0RLDTKOfXyULY53Kw= X-Received: by 2002:a25:90a:0:b0:664:3dd3:63de with SMTP id 10-20020a25090a000000b006643dd363demr4485579ybj.506.1655207610038; Tue, 14 Jun 2022 04:53:30 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:7000:dd05:0:0:0:0 with HTTP; Tue, 14 Jun 2022 04:53:29 -0700 (PDT) In-Reply-To: References: From: "Undiscussed Horrific Abuse, One Victim of Many" Date: Tue, 14 Jun 2022 07:53:29 -0400 Message-ID: To: Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Tue, 14 Jun 2022 12:10:31 +0000 Subject: Re: [bitcoin-dev] Why OpenTimestamps does not "linearize" its transactions X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2022 11:53:32 -0000 I was privately asked for more opinions. I am sharing them publicly below: It's always been clear that OTS proves longness of duration but not shortness. It doesn't demonstrate that an earlier work was not published, because it hashes each document hash with private material the author must separately publicize. Any unpublished private material could be an earlier equivalent to a public proof. the reason i call this 'designed to be broken' is that it lets people rewrite history to their stories by republishing other people's documents under different contexts. I would not be surprised if OTS also fails to add tx history containing its hashes to associated wallets, letting them be lost in chain forks.