Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id BA33DC0012 for ; Thu, 23 Dec 2021 18:11:01 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 9AC9381842 for ; Thu, 23 Dec 2021 18:11:01 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.848 X-Spam-Level: X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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=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 fJfl1zGer3BE for ; Thu, 23 Dec 2021 18:11:00 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-ua1-x930.google.com (mail-ua1-x930.google.com [IPv6:2607:f8b0:4864:20::930]) by smtp1.osuosl.org (Postfix) with ESMTPS id 5170D81831 for ; Thu, 23 Dec 2021 18:11:00 +0000 (UTC) Received: by mail-ua1-x930.google.com with SMTP id p2so11308911uad.11 for ; Thu, 23 Dec 2021 10:11:00 -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:to; bh=BYcftKoW0o1040TFH4APF2avnZnSz1s1GcQb8kIvyao=; b=cQ6TfPZ7erP6pdPMS2A9Vv/mEbLZ+a1KLqFf1gAox6Wub/D4YZxgcj7ggV/gKlTZ0w 2OStwLCC9EP8wvz65/BfXKSE7c4Rd9wEHxfE67CjYJJuDqGMrQjWoxRH/D2QzyYvqzrF vDZAQly7J9NyX5TBTcbfIjeOxVqVupC5x6bVgR05ki3Ex7oSbHfSRDMJ7aSmS2oOnlgs rGJwIyqF+xV/CeEoYcvjz+y2d3EKRqM0b5/TCXAit0VnaxrPj7qYV/Rba59zimdMQaGm mM4Qi5bHgHB8fZs6KhZ6h+qHJnjzq77+3veGCkXkKBs8b4BLRxYJpA7vtnpXec1NxMu8 ugfw== 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; bh=BYcftKoW0o1040TFH4APF2avnZnSz1s1GcQb8kIvyao=; b=Gcf/8XSiQ5pavNBCY3C0ECG4jVhtcfM2ay3+7iBPJK8dhVLn31Z5TXxd2zcP0lcwv4 sLv2lBT+8eaJ32SK8E0cPBPcviYGyJb3+81Qa6xevYs0nzRAo5bpK25R7VCL3hns+P7N M5TUeTdsEDdwzi/koTDLuzZ+XRXob7EzkWERmMaX+tfG9xEfS0xjnExre43gJL+m8c0Y E/JKzAgSrKuH17OcRDAGcdFm9Ug9Hkll2x0mYi4Dcmg3qNWiFLEdo9hDbFDLApHL9xD3 NtnKvSIgZ+aMBexYWJD/kbyIiZ9u7AjXaK6XJMb/4rH/GSl2qFc8K1/ziLr5auCj6rGn 3mhQ== X-Gm-Message-State: AOAM532Nnq1YsLiq5xFbom4Oju3wvqBN+S4VDmGocL8tN3tH0ouFKqYM GvPKxX1VephHMH39E2uO74Kw9xhynjLOYYfcARVSh2pTHSA= X-Google-Smtp-Source: ABdhPJx6rh3Kv3ZSpz3tqXd1jvCh5O1O9HJeiOXEk1hYcpGIVpZ9C790UtXjp6KXEqOnSquyYWc26LEwiiypdaLFTqU= X-Received: by 2002:ab0:6414:: with SMTP id x20mr1189028uao.81.1640283059037; Thu, 23 Dec 2021 10:10:59 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Oscar Lafarga Date: Thu, 23 Dec 2021 13:10:48 -0500 Message-ID: To: Jeremy , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="00000000000010a80f05d3d429a7" X-Mailman-Approved-At: Thu, 23 Dec 2021 19:28:32 +0000 Subject: Re: [bitcoin-dev] [Bitcoin Advent Calendar] Decentralized Autonomous Organizations (DAOs) Will Save Bitcoin 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, 23 Dec 2021 18:11:01 -0000 --00000000000010a80f05d3d429a7 Content-Type: text/plain; charset="UTF-8" > > None of this particularly requires CTV, but it does require the type of > composable and flexible software that I aspire to deliver with Sapio. Does this imply that there is some kind of Sapio client to be run alongside a Bitcoin full node similar to how a Lightning node would operate? If so, are the computation, bandwidth, and liveness requirements for someone running Sapio contracts more or less comparable to Lightning? The implementation approach seems pretty interesting overall and reminds me of concepts like bitcoin bug bounties (https://bitcoinacks.com/ for example) but perhaps with the potential for more sophisticated functionality. Will try to take a closer look at the https://github.com/sapio-lang/sapio if that seems like a recommended starting point. Thanks! On Wed, Dec 22, 2021 at 10:47 PM Jeremy via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > Hi Devs, > > Enjoy! https://rubin.io/bitcoin/2021/12/22/advent-25/ > > I'm really excited about opportunities for capital formation to happen > natively in Bitcoin. This is actually a really big deal and something (I > think) to pay close attention to. This is basically like running a little > company with shareholders inside of Bitcoin, which to me really helps us > inhabit the "be your own bank" part of Bitcoin. None of this particularly > requires CTV, but it does require the type of composable and flexible > software that I aspire to deliver with Sapio. > > business matter: > > There are two more posts, and they will both be focused on getting this > stuff out into the wild more. If you particularly have thoughts on BIP-119 > activation I would love to hear them publicly, or at your preference, > privately. > > If you like or dislike BIP-119 and wish to "soft-signal" yes or no > publicly, you may do so on https://utxos.org/signals by editing the > appropriate file(s) and making a PR. Alternatively, comment somewhere > publicly I can link to, send it to me, and I will make the edits. > > edit links: > - for individuals/devs: > https://github.com/JeremyRubin/utxos.org/edit/master/data/devs.yaml > - organizations: > https://github.com/JeremyRubin/utxos.org/edit/master/data/bizs.yaml > - miners/pools: > https://github.com/JeremyRubin/utxos.org/edit/master/data/hashratesnapshot.json > > Best, > > Jeremy > > -- > @JeremyRubin > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > -- Oscar Lafarga https://www.setlife.network --00000000000010a80f05d3d429a7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
None of thi= s particularly requires CTV, but it does require the type of composable and= flexible software that I aspire to deliver with Sapio.
=

=C2=A0Does this imply that there is some kind of Sapio client to b= e run alongside a Bitcoin full node similar to how a Lightning node would o= perate? If so, are the computation, bandwidth, and liveness requirements fo= r someone running Sapio contracts more or less comparable to Lightning?
=
The implementation approach seems pretty interesting overall and remind= s me of concepts like bitcoin bug bounties (https://bitcoinacks.com/ for example) but perhaps with the potent= ial for more sophisticated functionality.

Will try to take a closer = look at the https://github.= com/sapio-lang/sapio if that seems like a recommended starting point.
Thanks!

On Wed, Dec 22, 2021 at 10:47 PM Jeremy via bitcoin-dev = <bitcoin-dev@li= sts.linuxfoundation.org> wrote:
Hi Devs,

Enjoy! https://rubin.= io/bitcoin/2021/12/22/advent-25/

I'm really excit= ed about opportunities=C2=A0for capital formation to happen natively in Bit= coin. This is actually a really big deal and something (I think) to pay clo= se attention to. This is basically like running a little company with share= holders inside of Bitcoin, which to me really helps us inhabit the "be= your own bank" part of Bitcoin. None of this particularly requires CT= V, but it does require the type of composable and flexible software that I = aspire to deliver with Sapio.

=
business matter:

The= re are two more posts, and they will both be focused on getting this stuff = out into the wild more. If you particularly have thoughts on BIP-119 activa= tion I would love to hear them publicly, or at your preference, privately.<= /div>

If you like or dislike BIP-119 and wish to "soft-signal&qu= ot; yes or no publicly, you may do so on https://utxos.org/signals by editing the appropri= ate file(s) and making a PR. Alternatively, comment somewhere publicly I ca= n link to, send it to me, and I will make the edits.

edit links= :
- for individuals/devs:=C2=A0https://github.com/JeremyRubin/utxos.org/edit/master/da= ta/devs.yaml
- organizations:= =C2=A0https://github.com/JeremyRubin/utxos.org/edit/= master/data/bizs.yaml
- miners= /pools:=C2=A0https://github.com/JeremyRu= bin/utxos.org/edit/master/data/hashratesnapshot.json

Best,<= /div>

Jeremy

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev


--
--00000000000010a80f05d3d429a7--