Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-22 Thread Anthony Towns via bitcoin-dev
On Wed, Mar 16, 2022 at 02:54:05PM +, ZmnSCPxj via bitcoin-dev wrote: > My point is that in the past we were willing to discuss the complicated > crypto math around cross-input sigagg in order to save bytes, so it seems to > me that cross-input compression of puzzles/solutions at least merits

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-19 Thread Bram Cohen via bitcoin-dev
On Wed, Mar 16, 2022 at 7:54 AM ZmnSCPxj wrote: > My point is that in the past we were willing to discuss the complicated > crypto math around cross-input sigagg in order to save bytes, so it seems > to me that cross-input compression of puzzles/solutions at least merits a > discussion, since it

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-16 Thread Bram Cohen via bitcoin-dev
On Thu, Mar 10, 2022 at 8:46 PM Anthony Towns wrote: > Note that PTLCs aren't really Chia-friendly, both because chia doesn't > have secp256k1 operations in the first place, but also because you can't > do a scriptless-script because the information you need to extract > is lost when signatures a

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-16 Thread Bram Cohen via bitcoin-dev
On Wed, Mar 9, 2022 at 10:47 PM Anthony Towns wrote: > > To redo the singleton pattern in bitcoin's context, I think you'd have > to pass in both the full tx you're spending (to be able to get the > txid of its parent) and the full tx of its parent (to be able to get > the scriptPubKey that your

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-16 Thread Bram Cohen via bitcoin-dev
On Wed, Mar 9, 2022 at 6:30 AM ZmnSCPxj wrote: > I am pointing out that: > > * We want to save bytes by having multiple inputs of a transaction use the > same single signature (i.e. sigagg). > > is not much different from: > > * We want to save bytes by having multiple inputs of a transaction use

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-16 Thread ZmnSCPxj via bitcoin-dev
Good morning Bram, > On Wed, Mar 9, 2022 at 6:30 AM ZmnSCPxj wrote: > > > I am pointing out that: > > > > * We want to save bytes by having multiple inputs of a transaction use the > > same single signature (i.e. sigagg). > > > > is not much different from: > > > > * We want to save bytes by hav

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-16 Thread ZmnSCPxj via bitcoin-dev
Good morning aj et al., > On Tue, Mar 08, 2022 at 03:06:43AM +, ZmnSCPxj via bitcoin-dev wrote: > > > > > They're radically different approaches and > > > > it's hard to see how they mix. Everything in lisp is completely > > > > sandboxed, > > > > and that functionality is important to a lot

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-10 Thread Anthony Towns via bitcoin-dev
On Tue, Mar 08, 2022 at 03:06:43AM +, ZmnSCPxj via bitcoin-dev wrote: > > > They're radically different approaches and > > > it's hard to see how they mix. Everything in lisp is completely sandboxed, > > > and that functionality is important to a lot of things, and it's really > > > normal to b

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-09 Thread Anthony Towns via bitcoin-dev
On Tue, Mar 08, 2022 at 06:54:56PM -0800, Bram Cohen via bitcoin-dev wrote: > On Mon, Mar 7, 2022 at 5:27 PM Anthony Towns wrote: > > One way to match the way bitcoin do things, you could have the "list of > > extra conditions" encoded explicitly in the transaction via the annex, > > and then chec

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-09 Thread ZmnSCPxj via bitcoin-dev
Good morning Bram, > On Mon, Mar 7, 2022 at 7:06 PM ZmnSCPxj wrote: > > > But cross-input signature aggregation is a nice-to-have we want for > > Bitcoin, and, to me, cross-input sigagg is not much different from > > cross-input puzzle/solution compression. > > Cross-input signature aggregation

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-09 Thread Bram Cohen via bitcoin-dev
On Mon, Mar 7, 2022 at 7:06 PM ZmnSCPxj wrote: > > But cross-input signature aggregation is a nice-to-have we want for > Bitcoin, and, to me, cross-input sigagg is not much different from > cross-input puzzle/solution compression. > Cross-input signature aggregation has a lot of headaches unless

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-09 Thread Bram Cohen via bitcoin-dev
On Mon, Mar 7, 2022 at 2:56 PM ZmnSCPxj wrote: > > > while in the coin set model each puzzle (scriptpubkey) gets run and > either assert fails or returns a list of extra conditions it has, possibly > including timelocks and creating new coins, paying fees, and other things. > > Does this mean it

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-09 Thread Bram Cohen via bitcoin-dev
On Mon, Mar 7, 2022 at 5:27 PM Anthony Towns wrote: > One way to match the way bitcoin do things, you could have the "list of > extra conditions" encoded explicitly in the transaction via the annex, > and then check the extra conditions when the script is executed. > The conditions are already b

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-07 Thread ZmnSCPxj via bitcoin-dev
Good morning aj et al., > > They're radically different approaches and > > it's hard to see how they mix. Everything in lisp is completely sandboxed, > > and that functionality is important to a lot of things, and it's really > > normal to be given a reveal of a scriptpubkey and be able to rely o

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-07 Thread Anthony Towns via bitcoin-dev
On Sun, Mar 06, 2022 at 10:26:47PM -0800, Bram Cohen via bitcoin-dev wrote: > > After looking into it, I actually think chia lisp [1] gets pretty much all > > the major design decisions pretty much right. There are obviously a few > > changes needed given the differences in design between chia and

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-07 Thread ZmnSCPxj via bitcoin-dev
Good morning Bram, > while in the coin set model each puzzle (scriptpubkey) gets run and either > assert fails or returns a list of extra conditions it has, possibly including > timelocks and creating new coins, paying fees, and other things. Does this mean it basically gets recursive covenants

[bitcoin-dev] bitcoin scripting and lisp

2022-03-07 Thread Bram Cohen via bitcoin-dev
> > After looking into it, I actually think chia lisp [1] gets pretty much all > the major design decisions pretty much right. There are obviously a few > changes needed given the differences in design between chia and bitcoin: > > - having secp256k1 signatures (and curve operations), instead of >

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-05 Thread Russell O'Connor via bitcoin-dev
The circuit generated from Simplicity was larger than the hand made one. On Sat, Mar 5, 2022 at 6:20 PM ZmnSCPxj wrote: > Good morning Russell, > > > On Sat, Mar 5, 2022 at 8:41 AM Jeremy Rubin via bitcoin-dev < > bitcoin-dev@lists.linuxfoundation.org> wrote: > > > > > It seems like a decent con

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-05 Thread ZmnSCPxj via bitcoin-dev
Good morning Russell, > On Sat, Mar 5, 2022 at 8:41 AM Jeremy Rubin via bitcoin-dev > wrote: > > > It seems like a decent concept for exploration. > > > > AJ, I'd be interested to know what you've been able to build with Chia Lisp > > and what your experience has been... e.g. what does the Ligh

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-05 Thread Russell O'Connor via bitcoin-dev
On Sat, Mar 5, 2022 at 8:41 AM Jeremy Rubin via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > It seems like a decent concept for exploration. > > AJ, I'd be interested to know what you've been able to build with Chia > Lisp and what your experience has been... e.g. what does the Li

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-05 Thread Jeremy Rubin via bitcoin-dev
It seems like a decent concept for exploration. AJ, I'd be interested to know what you've been able to build with Chia Lisp and what your experience has been... e.g. what does the Lightning Network look like on Chia? One question that I have had is that it seems like to me that neither simplicit

Re: [bitcoin-dev] bitcoin scripting and lisp

2022-03-04 Thread ZmnSCPxj via bitcoin-dev
Good morning aj, > On Sun, Feb 27, 2022 at 04:34:31PM +, ZmnSCPxj via bitcoin-dev wrote: > > > In reaction to this, AJ Towns mailed me privately about some of his > > thoughts on this insane `OP_EVICT` proposal. > > He observed that we could generalize the `OP_EVICT` opcode by > > decomposin

[bitcoin-dev] bitcoin scripting and lisp

2022-03-03 Thread Anthony Towns via bitcoin-dev
On Sun, Feb 27, 2022 at 04:34:31PM +, ZmnSCPxj via bitcoin-dev wrote: > In reaction to this, AJ Towns mailed me privately about some of his > thoughts on this insane `OP_EVICT` proposal. > He observed that we could generalize the `OP_EVICT` opcode by > decomposing it into smaller parts, includi