From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id DD451C002D for ; Tue, 26 Jul 2022 16:02:18 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id AFAE74231D for ; Tue, 26 Jul 2022 16:02:18 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org AFAE74231D Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key) header.d=chia.net header.i=@chia.net header.a=rsa-sha256 header.s=google header.b=r7tumz6T 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 Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33ATWN7T_Me1 for ; Tue, 26 Jul 2022 16:02:15 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 56A9E409FF Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by smtp4.osuosl.org (Postfix) with ESMTPS id 56A9E409FF for ; Tue, 26 Jul 2022 16:02:15 +0000 (UTC) Received: by mail-yb1-xb2a.google.com with SMTP id f73so26036267yba.10 for ; Tue, 26 Jul 2022 09:02:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chia.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ug2aTruo2w9oXjtY9E+duWMLVY1oRzukSSb7rrxrqg4=; b=r7tumz6ToJnXsRTGQWT0xqoLAw8/X0kNeSIbHxwSHSUURmBvnoZUBBde5JZCoAdjz3 9yWk+gyM+ELyk4IOcAqGhy2Aab9YfRMI1C5B+3MSgLbO2LXfIxBsXUIfi9nFzvcOLt9j 6mq0SMWInT4P0VzMFCD155ofnTuh9Ew7wXeAbIJMel6ZQ6NnP57dz0qscdW/xrMg6oNg Kh6xsEzuGykjS6oZEHsyWcJ2vOO50u4hKLRztPS5g/CaGDI2ttZyjUFkpqP6OKo9sGpQ 7YcssoNboJ/TjVRhVeAY6WJcwEQ4yFBwzQAwCf12MYpEEPfupG2MlpIsejSEcTPSFyvU 4aDg== 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:to:cc; bh=ug2aTruo2w9oXjtY9E+duWMLVY1oRzukSSb7rrxrqg4=; b=lBYMDDXgBhxdsm66IC5NnAuBFVzxRlFCchS78bBKsww4L6VY1Y6B9deI07Kpr3qE3s /n+HxTEvkQPXLnmecUGd4yWhnLEz7jwIbEpJB9ZtbeNKs0bewhxCfSXDKE5+T1m3qoDw 9Pm6RXm/oDoxS3MAI5rqm7z934Gf9iouhwRBoxdUlL5A7zM92Fkk76gOi6KPmJzRRQAx 6e30NPilLDZ7isv12QqbrSq+5VuMoG1sWgQk8/1a4TGxx0wR32KW9PTayHXNJBC8gD/U 7JQcN6M+pKe1fu18Uv7soj+wx8WaepFgmULlY6AQfJE053/ASBHPgxXlnaj/+DnR//MM UJUQ== X-Gm-Message-State: AJIora8pNFofLGDAPfe/SwpDcnj88GcIxrz75yU78GG3qi+j0Oae3Fby ZWs7zqMRARSuAg3uBLp4JWg6QbgJWMMri+K9j0jIufYThAn36Q== X-Google-Smtp-Source: AGRyM1tvH3DVf8ZGLvTo+pVUnUCWyZw4okYnQXKKEh0j9WcwOW2nZ4ueBUgnmvanDOX+NIZQ97vlRZw+pG/0/cimTF4= X-Received: by 2002:a25:e0d1:0:b0:670:ee96:21b3 with SMTP id x200-20020a25e0d1000000b00670ee9621b3mr13918415ybg.463.1658851334067; Tue, 26 Jul 2022 09:02:14 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Bram Cohen Date: Tue, 26 Jul 2022 09:02:03 -0700 Message-ID: To: Antoine Riard Content-Type: multipart/alternative; boundary="00000000000080a9b505e4b76c70" X-Mailman-Approved-At: Tue, 26 Jul 2022 16:47:17 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] On a new community process to specify covenants 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, 26 Jul 2022 16:02:19 -0000 --00000000000080a9b505e4b76c70 Content-Type: text/plain; charset="UTF-8" On Mon, Jul 25, 2022 at 8:21 PM Antoine Riard wrote: > What would be the canonical definition and examples of capabilities in the > Bitcoin context ? > Payments into vaults which can only be accepted by that vault and are guaranteed to be subject to the vault's restrictions (the vault has a capability) Oracles whose validity can be verified on chain (so transactions can depend on what they say. The oracle has a capability) Colored coins whose validity can be verified on chain (the colored coins have a capability) --00000000000080a9b505e4b76c70 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Jul 25, 2022 at 8:21 PM Antoine R= iard <antoine.riard@gmail.com= > wrote:
What would be the canonical def= inition and examples of capabilities in the Bitcoin context ?

Payments into vaults which can only be accepte= d by that vault and are guaranteed to be subject to the vault's restric= tions (the vault has a capability)

Oracles whose validity can be verified on chain (so tr= ansactions can depend on what they say. The oracle has a capability)
<= div>
Colored coins whose validity can be verified on ch= ain (the colored coins have a capability)

--00000000000080a9b505e4b76c70--