From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id BAB98C0011 for ; Thu, 24 Feb 2022 21:02:09 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id A8B7183DF5 for ; Thu, 24 Feb 2022 21:02:09 +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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp1.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=rodarmor.com Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9JVXwaFL3uu5 for ; Thu, 24 Feb 2022 21:02:08 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) by smtp1.osuosl.org (Postfix) with ESMTPS id 4B8D083DF3 for ; Thu, 24 Feb 2022 21:02:08 +0000 (UTC) Received: by mail-ed1-x531.google.com with SMTP id bq11so4659819edb.2 for ; Thu, 24 Feb 2022 13:02:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rodarmor.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=EMxe8nBn9MKKUSmC6UbSqTJC+Qku7MZZCchAAJks7fk=; b=Eo+pERz+Wg/y+ztmcxenN75hFA4HZoW8OoAkkrrOdUElY8NLTz6fPNf1ogja+yUua9 4g/34vjSjgAl+sNrGxYAPudDK2SwSicSDIDMCzSMkY4Ruh9eu0vWqyXWE8uygi8Cu6FJ ibWAKqDGER+qr2WJ+JpXp1Fwp+wbf5phOw81iZDFpWnTb4wNpHXu9CmfKzCnc6id8ST2 mJuaa0t9p8cd+YMzb4EHyVr1JhRD7kyucEltvGOdGXmB2lZ6ulGk8ST+61cLHP1M80hB BWw2P9HD+zPfg0cgWmhF3XGYUyajHiDVfLl4xipUuIEOeAj8OLyL1UrCzaXqpPBxL4za 6D5g== 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:cc; bh=EMxe8nBn9MKKUSmC6UbSqTJC+Qku7MZZCchAAJks7fk=; b=CTx7v+fPEiOj0WuwxacKBfPs7ykTX1Q36kcIbJFh2pY5pqQv8Xyckr054SdQB1Xp9K TOq5CLTb7R+fyN3ZfaAAAoRLN8HK8yaeA0jDc41dxeUVd0AXb/qGjLaGuknqTtRWhcgK 3ub6PhpdKVZg3hGv2OiarmEXoU8LS8ZgPkvEQBGgLrQYfp14nGw79xCzwW8/hIu42+ih 8plYUnAhr2is8wpXZBJibgxMvu/rcpPbrdCwaGAnFbrlZzlfC5dQUwnBrKSuBQusKUwk PLADtXc6g56mpHfyPRccDl9lK/+UUNK3etukBLCkHdcQzqSKFBq2JBcAc1iACG75ncst xf1g== X-Gm-Message-State: AOAM532QHE59BSR87G/g9VtFxhek40l4gDJTg5FfuG+Uuya6dRCguuEe q1F/imbxGNMGm0xVon8aq4WSF/yh3ku474dyj89AyA== X-Google-Smtp-Source: ABdhPJyoOkV5esOgHIsiYyjvvNXf6gSPXYuwSs3ZoxvApl1M0qUQCvuOoTdq5m+0qGl2UZiDghzqy0xLgUQ70rJ5dq4= X-Received: by 2002:a05:6402:3553:b0:412:d0aa:e7b0 with SMTP id f19-20020a056402355300b00412d0aae7b0mr4096082edd.309.1645736526399; Thu, 24 Feb 2022 13:02:06 -0800 (PST) Received: from 649336022844 named unknown by gmailapi.google.com with HTTPREST; Thu, 24 Feb 2022 13:02:05 -0800 Mime-Version: 1.0 X-Superhuman-ID: l01h0lp2.17d1cc05-651a-4a1e-8bf2-ca255b568695 X-Superhuman-Draft-ID: draft00fec4a85b5d7f11 X-Mailer: Superhuman Web (2022-02-23T23:06:01Z) In-Reply-To: <157676573-26d876ec3baac7f177731a4fa956fb25@pmq3v.m5r2.onet> References: <157676573-26d876ec3baac7f177731a4fa956fb25@pmq3v.m5r2.onet> From: Casey Rodarmor Date: Thu, 24 Feb 2022 13:02:05 -0800 Message-ID: To: vjudeu@gazeta.pl, Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="0000000000000d040405d8c9e5d6" X-Mailman-Approved-At: Thu, 24 Feb 2022 21:11:40 +0000 Cc: Billy Tetrud Subject: Re: [bitcoin-dev] Draft-BIP: Ordinal Numbers 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: Thu, 24 Feb 2022 21:02:09 -0000 --0000000000000d040405d8c9e5d6 Content-Type: text/plain; charset="UTF-8" > When we talk about future improvements, there could be even bigger problem with ordinal numbers: what if/when we introduce some Monero-like system and hide coin amounts? (for example by using zero satoshi, because we have to use something that will be backward-compatible). Zero is quite interesting amount, because it means "skip amount checking for old clients". That can be used in many ways to introduce many protocols (and also to add fractional satoshis on-chain, because 0.4 satoshis could be represented as zero), so if that amounts will be simply ignored, then I wonder how it would be possible to connect some future protocol based on that with ordinal numbers. Ordinal numbers are inherently public, so it seems reasonable that they don't work with transactions that are private or have obfuscated values. --0000000000000d040405d8c9e5d6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> When we talk about future impr= ovements, there could be even bigger problem with ordinal numbers: what if/= when we introduce some Monero-like system and hide coin amounts? (for examp= le by using zero satoshi, because we have to use something that will be bac= kward-compatible). Zero is quite interesting amount, because it means "= ;skip amount checking for old clients". That can be used in many ways = to introduce many protocols (and also to add fractional satoshis on-chain, = because 0.4 satoshis could be represented as zero), so if that amounts will= be simply ignored, then I wonder how it would be possible to connect some = future protocol based on that with ordinal numbers.

Ordinal numbers are inherently public, so it seems reasonable that th= ey don't work with transactions that are private or have obfuscated val= ues.
--0000000000000d040405d8c9e5d6--