Tom [ARCHIVE] on Nostr: š Original date posted:2016-09-21 š Original message:On Tuesday 20 Sep 2016 ...
š
Original date posted:2016-09-21
š Original message:On Tuesday 20 Sep 2016 21:31:47 Luke Dashjr wrote:
> On Tuesday, September 20, 2016 5:15:45 PM Tom via bitcoin-dev wrote:
> > As the title suggests, I would like to formally request the assignment of
> > a
> > BIP number for my FT spec.
>
> Please open a pull request on the bitcoin/bips repo after this has been
> discussed a bit on the ML.
> It seems from the later comments, that it is the end of the transaction as a
> whole. Yet a separator between the txid and non-txid data would probably be
> valuable, rather than hard-coding txid to skip signature types (which may
> be unknown to old nodes, when extended).
>
> > The OP_CHECKSIG is the most well known and, as its name implies, it
> > validates a signature.
> > In the new version of 'script' (version 2) the data that is signed is
> > changed to be equivalent to the transaction-id. This is a massive
> > simplification and also the only change between version 1 and version 2 of
> > script.
>
> This seems to be a major regression. What is the replacement for
> SIGHASH_SINGLE and SIGHASH_ANYONECANPAY?
How is this a regression? Can you explain what functionality is lost please?
> When revising OP_CHECKSIG, it would also be nice to add the ability to use
> *only* a hash of the prevout's scriptPubKey in the input, so that *when* the
> prevtx is malleated, the spending one remains valid. (This use case is
> currently not supported.)
Maybe for the next version of script :)
> > Notice that the token ScriptVersion is currently not allowed
> What happens if I put ScriptVersion=1 here?
The transaction is invalid...
> > === Block-malleability ===
> >
> > For this reason the merkle tree is extended to include (append) the hash
> > of
> > the v4 transactions (and those alone) where the hash is taken over a
>
> > data-blob that is build up from:
>
> How should nodes know where in the merkle-tree the txids end, and the
> v4hashes begin?
Because the txid based ones are not going away. So the number of transactions
in the block can be used to determine when the pure tx-id segment stops and
when the v4 hashes begin. Then its up to the client to rebuild the tree from
that list based on the larger input set to get the same root-node.
I clarified many little things on my clone of the bips, check there if you
want to see the details.
š Original message:On Tuesday 20 Sep 2016 21:31:47 Luke Dashjr wrote:
> On Tuesday, September 20, 2016 5:15:45 PM Tom via bitcoin-dev wrote:
> > As the title suggests, I would like to formally request the assignment of
> > a
> > BIP number for my FT spec.
>
> Please open a pull request on the bitcoin/bips repo after this has been
> discussed a bit on the ML.
> It seems from the later comments, that it is the end of the transaction as a
> whole. Yet a separator between the txid and non-txid data would probably be
> valuable, rather than hard-coding txid to skip signature types (which may
> be unknown to old nodes, when extended).
>
> > The OP_CHECKSIG is the most well known and, as its name implies, it
> > validates a signature.
> > In the new version of 'script' (version 2) the data that is signed is
> > changed to be equivalent to the transaction-id. This is a massive
> > simplification and also the only change between version 1 and version 2 of
> > script.
>
> This seems to be a major regression. What is the replacement for
> SIGHASH_SINGLE and SIGHASH_ANYONECANPAY?
How is this a regression? Can you explain what functionality is lost please?
> When revising OP_CHECKSIG, it would also be nice to add the ability to use
> *only* a hash of the prevout's scriptPubKey in the input, so that *when* the
> prevtx is malleated, the spending one remains valid. (This use case is
> currently not supported.)
Maybe for the next version of script :)
> > Notice that the token ScriptVersion is currently not allowed
> What happens if I put ScriptVersion=1 here?
The transaction is invalid...
> > === Block-malleability ===
> >
> > For this reason the merkle tree is extended to include (append) the hash
> > of
> > the v4 transactions (and those alone) where the hash is taken over a
>
> > data-blob that is build up from:
>
> How should nodes know where in the merkle-tree the txids end, and the
> v4hashes begin?
Because the txid based ones are not going away. So the number of transactions
in the block can be used to determine when the pure tx-id segment stops and
when the v4 hashes begin. Then its up to the client to rebuild the tree from
that list based on the larger input set to get the same root-node.
I clarified many little things on my clone of the bips, check there if you
want to see the details.