Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 80BE71AB8 for ; Sat, 6 Jul 2019 10:12:50 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wr1-f66.google.com (mail-wr1-f66.google.com [209.85.221.66]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0C027881 for ; Sat, 6 Jul 2019 10:12:48 +0000 (UTC) Received: by mail-wr1-f66.google.com with SMTP id r1so5847644wrl.7 for ; Sat, 06 Jul 2019 03:12:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=QK53uLF2EGexkHeAWZj7c4td/dWbHqKafDFBggChwfw=; b=M9HfbKJRMU87Nvr6WOMqIu0kdsiDwIFH4q2FPmAH4C2KGYZ6wsw42tdBYTut6MgdrF sd7WDM4ZJeUv5/sh+qhU5AxzI/6KuShDT5w31H7i4lvQYCRXWgy5nPgWAKT1xk59/TmY 8aItiRN7fg7vHHSfu8/hiB3poQkSN7KwxBtEQOwzyhXbtjAjbCuuNlt28q2I7U4CJXaV c7Z8jfdYjMLDBpUJbEaBbqVvJyD3odIqAn2r7AmnW9zdwOnHLcy5x27A8J3lLRaWnAoc TOV8YVfuyD/GRgvK4vRkdFrvhx77Ueo3r0XaK9Cf93o0a0vqINgKN6zD31Uo0VXckKtm toyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=QK53uLF2EGexkHeAWZj7c4td/dWbHqKafDFBggChwfw=; b=FZHl00aK8Ygar9ngH7uR0NoAmSRH2O2hjB1/CFaxvTLLRvE5ViGhVJ9RbU/csHi6C0 FqiR8ysUFtr6m0gcwBw7eL46f5fzqU8XXbWY7Nk6eRb0u3p6YnqZAMFMfnUR5CauFJJV 6Gu32frKXQk3hYAz1+gGxa24wXIJ3VyPj7J4dyxictBzH/V6MK/nyLfsSDuZoJnMAQ69 uJyBhtdCubC6eqAgRGWPj17I0y66xl/cS59ZTeZUSG91B46DsJM4lvaONfLDnobXmc4t N9ZsUQfk3XlHlgV/t0b2zkGk6VtnXebIq9+8H3Zf5MMYiuk8Uu0/feo60hU12FkwddAC 2yiQ== X-Gm-Message-State: APjAAAXWpOdi6S3ra0MOlm6dg4hs1HIXG8jnf6L6/fSTjhQVgrqrXrme Vkvo5mJft44Gu6jXOXIPNbI= X-Google-Smtp-Source: APXvYqxTC4E7Qp549/lTtkOyf3Vj00NYMpQ93RXbEWIH1BvKxmuP5LByE5TwONj2n0tJ5c8gg5r/fw== X-Received: by 2002:a5d:620d:: with SMTP id y13mr8906443wru.243.1562407967646; Sat, 06 Jul 2019 03:12:47 -0700 (PDT) Received: from p200300dd671264266ded46351ea408b2.dip0.t-ipconnect.de (p200300DD671264266DED46351EA408B2.dip0.t-ipconnect.de. [2003:dd:6712:6426:6ded:4635:1ea4:8b2]) by smtp.gmail.com with ESMTPSA id t1sm13743481wra.74.2019.07.06.03.12.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Jul 2019 03:12:46 -0700 (PDT) From: Tamas Blummer Message-Id: <16B09501-7AE3-4F8E-A1A4-3E5F6B12D127@gmail.com> Content-Type: multipart/signed; boundary="Apple-Mail=_EE2376EF-56C9-4E83-BE03-D9ABF91EE74D"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Date: Sat, 6 Jul 2019 12:12:44 +0200 In-Reply-To: <4mT6iC4Va7Afg15a5NLbddAnF2a_vAcQSXYr_jg_5IyEK2ezblJff7EJZakoqvp4BJlLitt9Zlq1_l5JadR0nVss7VDPW-pv8jXGh7lkFC4=@protonmail.com> To: ZmnSCPxj References: <0DBC0DEA-C999-4AEE-B2E1-D5337ECD9405@gmail.com> <0AA10217-E1CC-46D1-9B43-038CEEF942CD@gmail.com> <6B9A04E2-8EEE-40A0-8B39-64AA0F478CAB@voskuil.org> <4mT6iC4Va7Afg15a5NLbddAnF2a_vAcQSXYr_jg_5IyEK2ezblJff7EJZakoqvp4BJlLitt9Zlq1_l5JadR0nVss7VDPW-pv8jXGh7lkFC4=@protonmail.com> X-Mailer: Apple Mail (2.3273) X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Sat, 06 Jul 2019 12:48:29 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Generalized covenants with taproot enable riskless or risky lending, prevent credit inflation through fractional reserve X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jul 2019 10:12:50 -0000 --Apple-Mail=_EE2376EF-56C9-4E83-BE03-D9ABF91EE74D Content-Type: multipart/alternative; boundary="Apple-Mail=_CEF1A73F-8208-4C70-8393-3190AA52BDF7" --Apple-Mail=_CEF1A73F-8208-4C70-8393-3190AA52BDF7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jul 6, 2019, at 01:16, ZmnSCPxj wrote: >=20 > Good morning Eric, >=20 >=20 > Sent with ProtonMail Secure Email. >=20 > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 = Original Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2= =80=90 > On Saturday, July 6, 2019 3:27 AM, Eric Voskuil > wrote: >=20 >>> On Jul 4, 2019, at 21:05, ZmnSCPxj ZmnSCPxj@protonmail.com wrote: >>> Good morning Eric, >>>=20 >>>> As with Bitcoin mining, it is the consumed cost that matters in = this scenario, (i.e., not the hash rate, or in this case the encumbered = coin face value). Why would the advertiser not simply be required to = burn .1 coin for the same privilege, just as miners burn energy? Why = would it not make more sense to spend that coin in support of the = secondary network (e.g. paying for confirmation security), just as with = the burning of energy in Bitcoin mining? >>=20 >> Good morning ZmnSCPxj, >>=20 >>> Using the unspentness-time of a UTXO allows for someone advertising = a service or producer to "close up shop" by simply spending the = advertising UTXO. >>> For instance, if the advertisement is for sale of a limited stock of = goods, once the stock has been sold, the merchant (assuming the merchant = used own funds) can simply recover the locked funds, with the potential = to reinvest them elsewhere. >>> This allows some time-based hedging for the merchant (they may be = willing to wait indefinitely for the stock to be sold, but once the = stock is sold, they can immediately reap the rewards of not having their = funds locked anymore). >>=20 >> This is a materially different concept than proposed by Tamas. >>=20 >> =E2=80=9C...he gives up his control of the coins until maturity, he = can not use them elsewhere until then.=E2=80=9D >=20 > Possibly. > In a way, this is giving up control of the coin, until he no longer = needs the advertisement, i.e. dynamically select the maturity age = needed. >=20 My proposal would separate the owner of the funds from the one using the = advertizement service. Yes, the owner lock up until maturity. But those = using the UTXO for the advertizement service could transfer (sell) the = UTXO to someone else as soon as they do not need it, so it is dynamic = maturity for them The new owner could use them for an other = advertizement or for an entirely different purpose. Regarding burning: I think burning is unsustainable as usage of services = is unlimited while coin suply is limited. >>=20 >> And as I have shown above, nor can a =E2=80=9Clocked-up=E2=80=9D coin = be unlocked to do the same. >=20 > You have shown no such thing, merely shown that you have not = understood the proposal. >=20 > Regards, > ZmnSCPxj I also struggle to communicate to Eric and likely many other reader the = generic utility of temporary control of an UTXO. Let me try again: Bitcoin offers a memory with remarkable properties: - it can be read by anyone anywhere - anyone anywhere who knows a key controlling an UTXO, and only them, = can initiate an update to the memory - global replicas guaranteed to apply updates of the memory within a = short time period. This is a utility that is sufficient to implement money. Such a reliable shared memory could have however more uses than tracking = money, It could keep track of, and thereby make scarce, arbitary other = things. We can unlock these uses by separating the money use of memory from = other uses. The covenant achives this separation temporarily. A UTXO with a covenant = that guarantees that current owner re-gains control at a later time = means, that the current owner temporarily forgoes the UTXOs use as money and = thereby allows its temporary use to keep track of something else. UTXOs with different covenants or without covenant are not fungible. Why use UTXOs of significant value to track something that is not money? = Because the reason the registry is used is to create scarcity and = scarcity can be tailored to more or less severe by requiring more or less satoshis to track something. The current owner of a regular UTXO will want to be paid for temporarily = giving up control, and that payment represents interest. Riskless, since = it is certain to re-gain control. Regards, Tamas Blummer --Apple-Mail=_CEF1A73F-8208-4C70-8393-3190AA52BDF7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On Jul 6, 2019, at 01:16, ZmnSCPxj <ZmnSCPxj@protonmail.com> wrote:

Good morning Eric,
Sent with ProtonMail Secure Email.
=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80= =90=E2=80=90 Original Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90= =E2=80=90=E2=80=90
On Saturday, July 6, 2019 3:27 AM, Eric = Voskuil <eric@voskuil.org> wrote:

On Jul 4, 2019, at 21:05, ZmnSCPxj ZmnSCPxj@protonmail.com wrote:
Good morning = Eric,

As= with Bitcoin mining, it is the consumed cost that matters in this = scenario, (i.e., not the hash rate, or in this case the encumbered coin = face value). Why would the advertiser not simply be required to burn .1 = coin for the same privilege, just as miners burn energy? Why would it = not make more sense to spend that coin in support of the secondary = network (e.g. paying for confirmation security), just as with the = burning of energy in Bitcoin mining?

Good morning = ZmnSCPxj,

Using the unspentness-time of a UTXO allows for someone = advertising a service or producer to "close up shop" by simply spending = the advertising UTXO.
For instance, if the advertisement = is for sale of a limited stock of goods, once the stock has been sold, = the merchant (assuming the merchant used own funds) can simply recover = the locked funds, with the potential to reinvest them elsewhere.
This allows some time-based hedging for the merchant (they = may be willing to wait indefinitely for the stock to be sold, but once = the stock is sold, they can immediately reap the rewards of not having = their funds locked anymore).

This is a materially different concept than proposed by = Tamas.

=E2=80=9C...he gives up his control = of the coins until maturity, he can not use them elsewhere until = then.=E2=80=9D

Possibly.
In a way, this is giving up control of the coin, = until he no longer needs the advertisement, i.e. dynamically select the = maturity age needed.


My proposal = would separate the owner of the funds from the one using the = advertizement service. Yes, the owner lock up until maturity. But those = using the UTXO for the advertizement service could transfer (sell) the = UTXO to someone else as soon as they do not need it, so it is dynamic = maturity for them The new owner could use them for an other = advertizement or for an entirely different purpose.

Regarding burning: I think burning is = unsustainable as usage of services is unlimited while coin suply is = limited. 


And as I have = shown above, nor can a =E2=80=9Clocked-up=E2=80=9D coin be unlocked to = do the same.

You have shown no such thing, = merely shown that you have not understood the proposal.
Regards,
ZmnSCPxj

I also struggle to communicate to Eric and likely many other = reader the generic utility of temporary control of an UTXO. Let me try = again:

Bitcoin = offers a memory with remarkable properties:
- it = can be read by anyone anywhere
- anyone anywhere = who knows a key controlling an UTXO, and only them, can initiate an = update to the memory 
- global replicas = guaranteed to apply updates of the memory within a short time = period.

This = is a utility that is sufficient to implement money. 

Such a reliable shared = memory could have however more uses than tracking money, It could keep = track of, and thereby make scarce, arbitary other things.

We can unlock these uses = by separating the money use of memory from other uses. 

The covenant achives = this separation temporarily. A UTXO with a covenant that guarantees that = current owner re-gains control at a later time means, 
that the current owner temporarily forgoes the UTXOs use as = money and thereby allows its temporary use to keep track of something = else. 
UTXOs with different covenants or = without covenant are not fungible.

Why use UTXOs of significant value to = track something that is not money? Because the reason the registry is = used is to create scarcity and scarcity can be tailored to more = or
less severe by requiring more or less satoshis = to track something.

The current owner of a regular UTXO will want to be paid for = temporarily giving up control, and that payment represents interest. = Riskless, since it is certain to re-gain control.
Regards,

Tamas Blummer





= --Apple-Mail=_CEF1A73F-8208-4C70-8393-3190AA52BDF7-- --Apple-Mail=_EE2376EF-56C9-4E83-BE03-D9ABF91EE74D Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE6YNJViYMM6Iv5f9e9nKRxRdxORwFAl0gdBwACgkQ9nKRxRdx ORwbggf7BatA+K9tCji9bPUe8x/3mbz8ny0r/qR5y5OlMh+OcLcuF01dOnMKyLw6 yjbvIm650TxLxRSQYlvr2JD9L13khLnM6EH4upKaitck8b7cZJItcVIBKUWi89+j 43p6013/0cX/Eq89EaKFZg8nSJ7AHK+QQJvmHj1019DKuIVY74G9RzEiDC85Ms+O C/IzELc91wfFqko54ITozZAPkjfr6NK//F7XozyzYoWyOxTs/EFri6wngCdXUZTo JWG+HlSjX3ZOZcTp/s9KoFff7T8doNFUjKBmbd2r1Xt7JfefnYn2jsf4ARbEY4xq 1TLi9wu/9BVequejp2dDdfSqZvPToQ== =vArM -----END PGP SIGNATURE----- --Apple-Mail=_EE2376EF-56C9-4E83-BE03-D9ABF91EE74D--