From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 3413BC000B for ; Sun, 6 Feb 2022 17:56:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 1CDE5813EA for ; Sun, 6 Feb 2022 17:56:26 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -0.077 X-Spam-Level: X-Spam-Status: No, score=-0.077 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, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: smtp1.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 TGk0YzcTRF59 for ; Sun, 6 Feb 2022 17:56:25 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) by smtp1.osuosl.org (Postfix) with ESMTPS id 6748A8137F for ; Sun, 6 Feb 2022 17:56:25 +0000 (UTC) Received: by mail-lj1-x231.google.com with SMTP id t14so16525309ljh.8 for ; Sun, 06 Feb 2022 09:56:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:cc; bh=YgJul6DS5/hoDP8Qk9WJvUr2aedF83cau4AwKEBYylI=; b=fRDeUUxujfk7UVTiDecfN/NMAAgwHUr3VlfrCsCsDJrSc0bPgD8Pm89TEUNC/LH6Wa j8utxSjZi+cN0xkUvZO0xGphkBB0DnhurOTbKyTG6+QxqZTRKSPLkzWUSngvZz+bOb+f SjoyS2c9AWav508VihNXa9W9cRX8OuihS7chEGJk5B3dg0xoqsaD1PgWdl0DH5n3sfXP 8CR6NVffUTronZnN450TNnFp4rfOa4U+s2h2BqbnaoEYe8SO0kqK+ZMQM5XTL3CuVgMJ YNSCVHqWsTi1onwPH5aRhjcVVKQDWRi9EKPJGCTTiZH9sb4aTQ3mld3OaGiSiNpMoYly 1MuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:cc; bh=YgJul6DS5/hoDP8Qk9WJvUr2aedF83cau4AwKEBYylI=; b=1ijU2lEpQ7aj/32Mb9zPynXCciPKpCl1LRRRhy1uZZaRL3P4dnzQC67FRHLoSREItG gysjIw/dcw/1OS4AhNwyvN5C5v93YvMBtz2frQEbcKBqImroSo+sRNJbq4hPwE1dRqWs /5CfFGXuFp4B9HxePmGgNNRO25l81Rmxmews1rZl6R4aPX20KVt4buM0M0DD3PQJoI0z sN3I6MDkUEppcGYG4uB/ScPBqPrdGRmxZgWtU6UM1+haJm5M4USHBMNYO29kO2mPqZLl FOlE+8BkcmwOk0faTn4RB106NfJEif0MwmHMbgSdgzGe7p1qCQjwb+otItfPEJQU8J5o gZ9g== X-Gm-Message-State: AOAM531mWKKGzu+rplFSeK2YIpjiyI3DBlrvdxGeLAQnzB8zklxODJmM 8FMqm1QB1N8DpQD4CSPfCkE8DdRCY3Qdfxi2wnb6f9yNEmw= X-Received: by 2002:a2e:9e82:: with SMTP id f2mt1855957ljk.57.1644170182885; Sun, 06 Feb 2022 09:56:22 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jeremy Rubin Date: Sun, 6 Feb 2022 09:56:12 -0800 Message-ID: Content-Type: multipart/alternative; boundary="000000000000b4f78d05d75d3321" Cc: Bitcoin Protocol Discussion , dlc-dev@mailmanlists.org Subject: Re: [bitcoin-dev] CTV dramatically improves DLCs 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: Sun, 06 Feb 2022 17:56:26 -0000 --000000000000b4f78d05d75d3321 Content-Type: text/plain; charset="UTF-8" I'm not sure what is meant concretely by (5) but I think overall performance is ok here. You will always have 10mins or so to confirm the DLC so you can't be too fussy about performance! I mean that if you think of the CIT points as being the X axis (or independent axes if multivariate) of a contract, the Y axis is the dependent variable represented by the CTV hashes. For a DLC living inside a lightning channel, which might be updated between parties e.g. every second, this means you only have to recompute the cheaper part of the DLC only if you update the payoff curves (y axis) only, and you only have to update the points whose y value changes. For on chain DLCs this point is less relevant since the latency of block space is larger. --000000000000b4f78d05d75d3321 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=
I'm not sure what is m= eant concretely by (5) but I think overall performance is ok here. You will= always have 10mins or so to confirm the DLC so you can't be too fussy = about performance!

I mean that = if you think of the CIT points as being the X axis (or independent axes if = multivariate) of a contract, the Y axis is the dependent variable represent= ed by the CTV hashes.=C2=A0


For a DLC living inside a lightning c= hannel, which might be updated between parties e.g. every second, this mean= s you only have to recompute the cheaper part of the DLC only if you update= the payoff curves (y axis) only, and you only have to update the points wh= ose y value changes.

=
For on chain DLCs this p= oint is less relevant since the latency of block space is larger.=C2=A0
--000000000000b4f78d05d75d3321--