On Thursday, 22 September 2016 21:59:12 CEST Jonas Schnelli via bitcoin-dev
wrote:
> Hi Tom
>
> > I think you misunderstand tagged systems at a very basic level. You
> > think that html can only use a bold tag once in a document? Thats
> > equivalent to what you are saying.
>
> Would the "addi
Hi Tom
> I think you misunderstand tagged systems at a very basic level. You think
> that html can only use a bold tag once in a document? Thats equivalent
> to what you are saying.
Would the "additional" segment contain the same amount of
nSequence-equivalent token as the number of inputs in
On Thursday, 22 September 2016 14:26:18 CEST Peter Todd wrote:
> > «The way towards that flexibility is to use a generic concept made
> > popular various decades ago with the XML format. The idea is that we
> > give each field a name and this means that new fields can be added or
> > optional field
On Thursday, 22 September 2016 14:27:29 CEST Peter Todd wrote:
> CSV uses per-input sequence numbers; you only have a per-tx equivalent.
I think you misunderstand tagged systems at a very basic level. You think
that html can only use a bold tag once in a document? Thats equivalent
to what you
On Thu, Sep 22, 2016 at 10:47:03AM +0200, Tom via bitcoin-dev wrote:
> On Wednesday 21 Sep 2016 18:45:55 adiabat via bitcoin-dev wrote:
> > Hi-
> >
> > One concern is that this doesn't seem compatible with Lightning as
> > currently written. Most relevant is that non-cooperative channel close
> >
On Wed, Sep 21, 2016 at 11:32:33AM +0200, Tom wrote:
> Thanks for your email Peter!
>
> On Tuesday 20 Sep 2016 17:56:44 Peter Todd wrote:
> > On Tue, Sep 20, 2016 at 07:15:45PM +0200, Tom via bitcoin-dev wrote:
> > > === Serialization order===
> > >
> > > The tokens defined above have to be seria
On Thursday 22 Sep 2016 13:10:49 Christian Decker via bitcoin-dev wrote:
> On Thu, Sep 22, 2016 at 10:56:31AM +0200, Tom via bitcoin-dev wrote:
> > On Wednesday 21 Sep 2016 18:01:30 Gregory Maxwell via bitcoin-dev wrote:
> > > On Tue, Sep 20, 2016 at 5:15 PM, Tom via bitcoin-dev
> > >
> > > wrote
On Thu, Sep 22, 2016 at 10:56:31AM +0200, Tom via bitcoin-dev wrote:
> On Wednesday 21 Sep 2016 18:01:30 Gregory Maxwell via bitcoin-dev wrote:
> > On Tue, Sep 20, 2016 at 5:15 PM, Tom via bitcoin-dev
> >
> > wrote:
> > > BIP number for my FT spec.
> >
> > This document does not appear to be con
Hi,
Is your simulation code available somewhere?
I was just wondering why mycelium generates a very big UTXO set for <1000sat,
because change outputs will never be smaller than
5460sat (=TransactionUtils.MINIMUM_OUTPUT_VALUE). If the change would be lower,
it simply is skipped and added to the
On Wednesday 21 Sep 2016 18:01:30 Gregory Maxwell via bitcoin-dev wrote:
> On Tue, Sep 20, 2016 at 5:15 PM, Tom via bitcoin-dev
>
> wrote:
> > BIP number for my FT spec.
>
> This document does not appear to be concretely specified enough to
> review or implement from it.
>
> For example, it doe
On Wednesday 21 Sep 2016 18:45:55 adiabat via bitcoin-dev wrote:
> Hi-
>
> One concern is that this doesn't seem compatible with Lightning as
> currently written. Most relevant is that non-cooperative channel close
> transactions in Lightning use OP_CHECKSEQUENCEVERIFY, which references the
> seq
11 matches
Mail list logo
