Newsletters: add 62 (2019-09-04) #219

harding · 2019-08-31T22:52:17Z

~~Based on #218, ignore first commit~~
#218 has been merged

jnewbery · 2019-09-03T14:14:37Z

I merged #218 and rebased this on master.

jnewbery

Looks great. Thanks @harding . Three small comments inline.

jnewbery · 2019-09-03T14:16:51Z

_posts/en/newsletters/2019-09-04-newsletter.md

+  to be disclosed at the end of this month affect older LN
+  implementations.  If you are using any of the following software
+  versions, upgrading to a more recent version is [strongly
+  recommended:][cve ln]


super nit: anchor around strongly recommended, not strongly recommended:

jnewbery · 2019-09-03T14:21:00Z

_posts/en/newsletters/2019-09-04-newsletter.md

+[cve ln]: https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-August/002130.html
+[bolts608]: /en/newsletters/2019/08/28/#bolts-608
+[bolts]: https://github.com/lightningnetwork/lightning-rfc/
+[snicker]: https://gist.github.com/AdamISZ/2c13fb5819bd469ca318156e2cf25d79#storage-of-keys


Why is this linking to the #storage-of-keys id?

This was a mistake (I grabbed that link for a separate discussion about that aspect of the proposal and then reused it here without thinking about it). Thanks to you and @jonatack for catching this, I'll fix it.

jnewbery · 2019-09-03T14:24:40Z

_posts/en/newsletters/2019-09-04-newsletter.md

+
+## News
+
+- **SNICKER proposed:** Adam Gibson posted to the Bitcoin-Dev mailing


I suggest we link to the mailing list post (https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2019-September/017283.html) as well as the draft BIP.

I also think we could link to Adam's blog post (https://joinmarket.me/blog/blog/snicker/)

adamjonas · 2019-09-03T15:18:01Z

_posts/en/newsletters/2019-09-04-newsletter.md

+  as described in [last week's newsletter][bolts608].
+
+- [Eclair #899][] implements extended queries as proposed in [BOLTs
+  #557][], allowing an LN node to only request gossip updates that


nit: to only request -> only to request (split infinitive)

jonatack

Interesting newsletter as always and great to see Adam Gibson's proposal discussed! A few comments below.

jonatack · 2019-09-03T14:44:10Z

_posts/en/newsletters/2019-09-04-newsletter.md

+---
+This week's newsletter relays a security announcement for LN
+implementations, describes a non-interactive coinjoin proposal, and
+notes a few changes in popular Bitcoin Infrastructure projects.


suggestion: lowercase "infrastructure"

jonatack · 2019-09-03T14:45:31Z

_posts/en/newsletters/2019-09-04-newsletter.md

+lang: en
+---
+This week's newsletter relays a security announcement for LN
+implementations, describes a non-interactive coinjoin proposal, and


proposed to Adam to drop by and have a look-see

jonatack · 2019-09-03T14:49:49Z

_posts/en/newsletters/2019-09-04-newsletter.md

+  also be able to derive from Alice's public key.  With the shared
+  secret and Bob's public key, Alice is able to create a new public key
+  that only Bob can sign for.  That new public key is used to create the
+  new address for Bob's coinjoin output.  Nobody besides Alice and Bob


suggestion: s/Nobody/No one/

jonatack · 2019-09-03T14:59:17Z

_posts/en/newsletters/2019-09-04-newsletter.md

+  both possibilities.-->{% endcomment %}
+
+  With information about the inputs and the outputs, Alice creates a
+  [BIP174][] Partially-Signed Bitcoin Transaction (PSBT) containing the


Each time I read "Partially-Signed..." it strikes me as a (minor, perhaps pedantic) grammar error. "Partially" can only be an adverb. IIUC, dashes are only appended to adverbs when they can also be adjectives (or other), to clarify when they play the part of an adverb and modify the word they precede.

I'm going to leave this as-is since I have a busy todo list today and we've used this construction many times before, but tomorrow I'll look into this in more detail and will either get back to you with an explanation or will open a PR to remove the hyphen across the repository. (Omitting the hyphen feels wrong to me and I have a vague recollection of a rule requiring (or at least suggesting) it, but I need to research it.)

Hyphens, thank you. As a recovering liberal hyphenizer before coming across the rule I mentioned, I'm interested in your conclusion. Could imagine a possible exception to the rule for titles or proper nouns.

jonatack · 2019-09-03T15:01:54Z

_posts/en/newsletters/2019-09-04-newsletter.md

+- **SNICKER proposed:** Adam Gibson posted to the Bitcoin-Dev mailing
+  list with a [proposal][snicker] for *Simple Non-Interactive Coinjoin
+  with Keys for Encryption Reused* (SNICKER), a two-step method for
+  allowing wallets to create coinjoins non-interactively.  In the first


suggestion: name the two steps (proposal/reception) before launching into the detail about each one

jonatack · 2019-09-03T15:05:54Z

_posts/en/newsletters/2019-09-04-newsletter.md

+  This completes the proposer step in SNICKER.
+
+  If Bob participates in the scheme, his wallet can begin the second
+  step (*receiver* step) by periodically checking the server to see if


perhaps: s/receiver step/reception/

jonatack · 2019-09-03T15:08:12Z

_posts/en/newsletters/2019-09-04-newsletter.md

+  SNICKER exchange server.
+
+  The main downside of the proposal is that it requires the proposer
+  (Alice) know the public key of the receiver (Bob).  Almost all


suggestion: s/know/to know/

alternatively, s/requires the/requires that the/

jonatack · 2019-09-03T15:09:45Z

_posts/en/newsletters/2019-09-04-newsletter.md

+  The main downside of the proposal is that it requires the proposer
+  (Alice) know the public key of the receiver (Bob).  Almost all
+  transactions today pay an address that doesn't include a public key,
+  although that may to change if the proposed [taproot][bip-taproot]


s/may to change/may change/

jonatack · 2019-09-03T15:13:34Z

_posts/en/newsletters/2019-09-04-newsletter.md

+  transactions today pay an address that doesn't include a public key,
+  although that may to change if the proposed [taproot][bip-taproot]
+  soft fork is activated and becomes widely adopted.  In the meantime,
+  the SNICKER proposal suggests using reused addresses where public keys


suggestion: s/using reusing addresses where/reusing addresses whose/

jonatack · 2019-09-03T15:20:48Z

_posts/en/newsletters/2019-09-04-newsletter.md

+[cve ln]: https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-August/002130.html
+[bolts608]: /en/newsletters/2019/08/28/#bolts-608
+[bolts]: https://github.com/lightningnetwork/lightning-rfc/
+[snicker]: https://gist.github.com/AdamISZ/2c13fb5819bd469ca318156e2cf25d79#storage-of-keys


Is the #storage-of-keys part of this URL desired? IIUC the link is used in the intro sentence "Adam Gibson posted to the Bitcoin-Dev mailing list with a [proposal][snicker] for Simple Non-Interactive Coinjoin with Keys for Encryption Reused"...

AdamISZ · 2019-09-03T17:07:28Z

Had a quick read through, it's a very good concise summary of the main idea, better than either that of mine, probably.

"map of addresses and public keys" - I think using the term 'map' here is a bit suboptimal in terms of understanding for the reader. Maybe better something like 'scans the blockchain to make lists of candidate public keys, either from reused addresses or from inferring connections between inputs an outputs, or perhaps via some watermarking in transactions'. Or ... a shorter version of that, if you prefer :)

I agree with your de-emphasis of encryption here ('perhaps encrypted') given our earlier conversation. Perhaps 'perhaps' is too faint though :) But no worries, that's fine.

But one last point - I do think the use of anonymous network connections to the server should probably be mentioned. Just because it serves to further emphasize that the "bulletin board" server is just that; identities or accounts are not involved, at least not within the proposal as-is.

Thanks for writing this @harding and thanks for the ping @jonatack !

harding · 2019-09-03T18:15:02Z

Pushed edits for feedback. Thanks everyone for the reviews!

jonatack · 2019-09-03T18:51:27Z

_posts/en/newsletters/2019-09-04-newsletter.md

-  If Bob participates in the scheme, his wallet can begin the second
-  step (*receiver* step) by periodically checking the server to see if
+  If Bob participates in the scheme, his wallet can begin the
+  receiver by periodically checking the server to see if


s/receiver/receiver step/ ?

jnewbery · 2019-09-03T18:48:51Z

_posts/en/newsletters/2019-09-04-newsletter.md

+  This completes the proposer step in SNICKER.
+
+  If Bob participates in the scheme, his wallet can begin the
+  receiver by periodically checking the server to see if


s/begin the receiver/begin the receiver step/

jnewbery · 2019-09-03T18:50:18Z

_posts/en/newsletters/2019-09-04-newsletter.md

+  people via a variety of servers, selecting whichever proposal he
+  prefers (or none at all).  Either party can also spend their UTXO
+  normally at any time, automatically invalidating any pending proposals
+  without any harm done.  The PSBTs can be exchanged using any medium that doesn't require users identify themselves,


s/doesn't require users identify/doesn't require users to identify/

jnewbery · 2019-09-03T18:50:59Z

_posts/en/newsletters/2019-09-04-newsletter.md

+
+  The main downside of the proposal is that it requires the proposer
+  (Alice) know the public key of the receiver (Bob).  Almost all
+  transactions today pay an address that doesn't include a public key,


perhaps: almost all transactions outputs today pay to an address

jonatack · 2019-09-03T18:52:42Z

_posts/en/newsletters/2019-09-04-newsletter.md

  SNICKER exchange server.

  The main downside of the proposal is that it requires the proposer
  (Alice) know the public key of the receiver (Bob).  Almost all
  transactions today pay an address that doesn't include a public key,
-  although that may to change if the proposed [taproot][bip-taproot]
+  although that may change if the proposed [taproot][bip-taproot]
  soft fork is activated and becomes widely adopted.  In the meantime,


note that here ("widely adopted") you did not use a hyphen 👼

jonatack · 2019-09-03T18:56:12Z

Verified the new links are 🆗

jonatack · 2019-09-03T20:54:57Z

in b4 @bitschmidty

Takes a few steps to make a snicker newsletter
Big Dave wrote up the rhymes then he dropped the hammer
MC Adam G did B-I-P author review
Give it up for John-Jonas-Jon,Triple-J Review Crew
PSBTs be rockin with Alice & Bob
Pass the mic to MC Mike to finish the job

harding · 2019-09-04T03:38:12Z

Pushed edits for @jonatack and @jnewbery second-round feedback. Thanks!

bitschmidty

tACK 17aa336

bitschmidty · 2019-09-04T11:23:00Z

my little ditty comments are getting redundant
much better rhymes becoming abundant

Adam Gibson on the mail list has spoken
'You're not you when you're hidden' is the new SNICKER slogan

rebased, squashed and merged! thanks @harding and reviewers!

jnewbery force-pushed the 2019-09-04-newsletter branch from 9aa2e30 to f91f3d9 Compare September 3, 2019 14:14

jnewbery reviewed Sep 3, 2019

View reviewed changes

adamjonas reviewed Sep 3, 2019

View reviewed changes

jonatack reviewed Sep 3, 2019

View reviewed changes

jnewbery reviewed Sep 3, 2019

View reviewed changes

jonatack reviewed Sep 3, 2019

View reviewed changes

bitschmidty reviewed Sep 4, 2019

View reviewed changes

Newsletters: add 62 (2019-09-04)

016c3cc

bitschmidty force-pushed the 2019-09-04-newsletter branch from 17aa336 to 016c3cc Compare September 4, 2019 11:07

bitschmidty merged commit 58bc106 into bitcoinops:master Sep 4, 2019

harding mentioned this pull request Sep 4, 2019

Grammar: remove hyphen from "Partially-Signed" #220

Merged

jnewbery mentioned this pull request Dec 24, 2019

Change 'partially-signed' to 'partially signed' in topic page #308

Merged

murchandamus mentioned this pull request Jul 17, 2023

Newsletter 257 translate in french #1182

Merged

murchandamus mentioned this pull request Aug 1, 2023

Harmonize titles of French Newsletters #1222

Merged


		## News

		- SNICKER proposed: Adam Gibson posted to the Bitcoin-Dev mailing

Newsletters: add 62 (2019-09-04) #219

Newsletters: add 62 (2019-09-04) #219

Uh oh!

Conversation

harding commented Aug 31, 2019 • edited by jnewbery Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jnewbery commented Sep 3, 2019

Uh oh!

jnewbery left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jonatack left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AdamISZ commented Sep 3, 2019

Uh oh!

harding commented Sep 3, 2019

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jonatack Sep 3, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jonatack commented Sep 3, 2019

Uh oh!

jonatack commented Sep 3, 2019

Uh oh!

harding commented Sep 4, 2019

Uh oh!

bitschmidty left a comment

Choose a reason for hiding this comment

Uh oh!

bitschmidty commented Sep 4, 2019

Uh oh!

Uh oh!

harding commented Aug 31, 2019 •

edited by jnewbery

Loading

jonatack Sep 3, 2019 •

edited

Loading