Skip to content

Conversation

@droark
Copy link
Contributor

@droark droark commented Jul 29, 2015

The sentence regarding empty byte arrays being used to indicate an invalid ECDSA signature is confusing. I attempted to make it clearer. If I screwed it up or can make it even clearer, please let me know.

Thank you.

The sentence regarding allowing empty byte arrays to indicate an invalid ECDSA signature is confusing. I attempted to make it clearer. If I screwed it up or can make it even clearer, please let me know.

Thank you.
@jonasschnelli
Copy link
Contributor

@fanquake
Copy link
Member

@jonasschnelli This is the bips repo

@jonasschnelli
Copy link
Contributor

Aii.. Ignore my comment then. Sorry.

@laanwj
Copy link
Member

laanwj commented Aug 24, 2015

Don't feel strongly about it but "the empty byte array" is strictly correct. There is only one possible empty byte array.

@droark
Copy link
Contributor Author

droark commented Aug 25, 2015

@laanwj - Sorry if my comment wasn't totally clear. I mentioned the empty byte array because that was, to me, the most unique phrase in the affected sentence. (Granted, I think "empty byte array" still sounds weird, but I won't rewrite that.) I've highlighted the differences below. In particular, "for with" is definitely a typo.

Original: "To provide a compact way to deliberately create an invalid signature for with OP_CHECKSIG and OP_CHECKMULTISIG the empty byte array (the result of OP_0) is also allowed."

Revision: "To provide a compact way to deliberately create an invalid signature for OP_CHECKSIG and OP_CHECKMULTISIG, an empty byte array (i.e., the result of OP_0) is also allowed."

@luke-jr
Copy link
Member

luke-jr commented Sep 3, 2015

@sipa ACK please, when you get a chance?

@sipa
Copy link
Member

sipa commented Sep 3, 2015

ACK

luke-jr added a commit that referenced this pull request Sep 3, 2015
Minor grammatical change
@luke-jr luke-jr merged commit 7b19058 into bitcoin:master Sep 3, 2015
luke-jr pushed a commit to luke-jr/bips that referenced this pull request Jun 6, 2017
…coin#176)

This commit fixes an advisory error in the current spec draft. We
currently use `fee-per-kw` where `kw = 1000` weight to determine the
proper fee to pay for commitment transactions. Currently, the spec
advises implementer to take the typical sat/Kb at _multiply_ by 4. This
will result in implementations overpaying for commitment transactions
as the scaling should actually be in the _opposite_ direction. As the
weight is scaled up by 4, for fee-per-kw should be scaled down by 4.
So: sat/Kb * 1/4, instead of sat/Kb * 4.

[Minor fixup: "1/4th" to "1/4", better english, and doesn't trip spellcheck. -- RR]
pinheadmz pushed a commit to pinheadmz/bips that referenced this pull request Dec 15, 2019
Linearity makes sign-for-sum-of-keys easier, not possible entirely.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants