Skip to content

Conversation

harding
Copy link
Collaborator

@harding harding commented Apr 28, 2020

Preview: https://deploy-preview-395--bitcoinops.netlify.app/

Includes the SuredBits field report by @rorp (CC: @Christewart)

@harding harding marked this pull request as draft April 28, 2020 10:27
@harding harding mentioned this pull request Apr 28, 2020
5 tasks
@harding harding force-pushed the 2020-05-06-newsletter branch from ced303c to c9d0598 Compare May 3, 2020 15:49
@harding harding marked this pull request as ready for review May 3, 2020 15:50
Copy link
Member

@adamjonas adamjonas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @harding!

Comment on lines 80 to 82
- **Grokking Bitcoin** Kalle Rosenbaum participated in a [Socratic
Seminar][] at London Bitcoin Devs one week and gave a presentation the
next week. The seminar focused on the role of Bitcoin technical
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This lead is a little awkward. He is a slight improvement though not my favorite:

Suggested change
- **Grokking Bitcoin** Kalle Rosenbaum participated in a [Socratic
Seminar][] at London Bitcoin Devs one week and gave a presentation the
next week. The seminar focused on the role of Bitcoin technical
- **Grokking Bitcoin** Kalle Rosenbaum led a [Socratic
Seminar][] at London Bitcoin Devs and gave a presentation the
following week. The seminar focused on the role of Bitcoin technical

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure Kalle led the seminar (the transcript is unattributed for privacy, but it seemed to me that someone else was leading).

Copy link
Collaborator

@jonatack jonatack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of nits so far.

as previously discussed (see [Newsletter #83][news83 alt
tiebreaker]).

- *Updated nonce generation recommendadions:* the suggested method
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/recommendadions/recommendations

[taproot][topic taproot]. The major changes include:

- *Alternative x-only pubkey tiebreaker:* this changes which variant
of a public key to use when only the key’s x-coordinate is known,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggest: "when only the x-coordinate of the key is known,"

as previously discussed (see [Newsletter #83][news83 alt
tiebreaker]).

- *Updated nonce generation recommendadions:* the suggested method
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/srecommendadions/recommendations

@harding
Copy link
Collaborator Author

harding commented May 5, 2020

Made requested edits (thanks all!) and ACK @bitschmidty's description of 16528 (also thanks!).

transactions to improve wallet privacy FIXME:bitschmidty
- [Bitcoin Core #18038][] improves privacy when initially broadcasting a
transaction by reducing the frequency that a wallet will attempt to resend
from about 30 minutes to about once a day. Previously, an entity surveilling
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggest s/about once a day/once every 12-36 hours/

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer 'about once a day'. The exact distribution seems too low-level for a summary write-up, and people who are interested can click through to the PR for full details.

@jnewbery jnewbery force-pushed the 2020-05-06-newsletter branch from 37d2463 to b4848f8 Compare May 5, 2020 12:51
@jnewbery
Copy link
Contributor

jnewbery commented May 5, 2020

I've rebased on master since this wasn't a clean fast-forward merge.

@jnewbery jnewbery force-pushed the 2020-05-06-newsletter branch from b4848f8 to 19fb0e4 Compare May 5, 2020 13:12
@jnewbery
Copy link
Contributor

jnewbery commented May 5, 2020

I've squashed commits together for the different sections.

@jnewbery jnewbery force-pushed the 2020-05-06-newsletter branch from 19fb0e4 to 12da6cf Compare May 5, 2020 13:37
@jnewbery
Copy link
Contributor

jnewbery commented May 5, 2020

Pushed a change to make the image background transparent instead of white.

Copy link
Contributor

@jnewbery jnewbery left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I've left a bunch of nits inline. Because my review is late, I've pushed those suggested changes in a commit. @harding - please feel free to revert any of those changes that you don't like.

- **QR codes for large transactions:** QR codes can practically contain
up to about 3 kilobytes of data, which is enough to accommodate
typical user transactions but far too small to contain the largest
transactions users can normally send (about 400 kilobytes). Riccardo
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I suggest removing "(about 400 kilobytes)". I believe you're right that the largest transaction allowed under standardness rules would be 101k vbytes, which would equate to 404k if the entire transaction consisted of witness. There's also overhead in the PSBT format, which carries additional data. I think it's best to just remove the number here.

## Recently transcribed talks and conversations

*[Bitcoin Transcripts][] is the home for transcripts of technical
Bitcoin presentations and discussions. In this new <!-- TODO: remove "new" next month --> monthly feature, we
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest we don't promise that this will be monthly until we see how the first one is received and have had a chance to discuss internally.

the challenge of estimating onchain fees months in advance.
Jager discussed the challenges of [multipart payments][topic multipath
payments] including the splitting algorithm, what happens when the
shards of the payment arrive at different times, and strategies for
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: "strategies for dealing with when a...."./ "strategies for handling ..."

the channel abstraction work that made this possible.
([transcript][lnd10 xs], [video][lnd10 vid])

- **Grokking Bitcoin** Kalle Rosenbaum both participated in a [Socratic
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: remove 'both'

([transcript][lnd10 xs], [video][lnd10 vid])

- **Grokking Bitcoin** Kalle Rosenbaum both participated in a [Socratic
Seminar][] and gave a presentation at London Bitcoin Devs. The
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this link would be very meaningful for readers. I suggest either removing the link entirely and rewording to "developer meetup" or linking to https://bitdevs.org/running-a-great-socratic-seminar/.

[Bitcoin Improvement Proposals (BIPs)][bips repo], and [Lightning
BOLTs][bolts repo].*

*Note: the commits to Bitcoin Core mentioned below apply to its master
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This boilerplate warning was added last week as well. What's the justification for doing this? Doesn't the same warning apply to commits for other repos?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This boilerplate warning was added last week as well.

Variations on the notice also appear in newsletters 9, 10, 11, 12, 13, 14, 37, 40, 41, 42, 43, 67, and 68. (Search for "master" in any of those newsletters.)

What's the justification for doing this?

Without the warning, I think people will expect the changes we describe to appear in the next Bitcoin Core release (e.g. 0.20 in a few weeks).

Doesn't the same warning apply to commits for other repos?

No. Both LND and C-Lightning RCs releases are just tags on their master branch. I think that's also the case for Eclair, but I'm not sure. Rust-Lightning has tags that GitHub shows as releases but there's no release notes and they're all version 0.0.x, so I've been assuming they're not real releases. The other repos don't do releases.

In short, AFAICT, Bitcoin Core is the only project we monitor that branches from master prior to a major release. (Indeed, I'm unable to think of any other free software project I've followed that does that.)

As an alternative to the warning, we could simply not report on Bitcoin Core commits to master during RC cycles, though that would leave us with a huge backlog when at the end of each cycle.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah ok. Makes sense. Thanks!

transactions to improve wallet privacy FIXME:bitschmidty
- [Bitcoin Core #18038][] improves privacy when initially broadcasting a
transaction by reducing the frequency that a wallet will attempt to resend
from about 30 minutes to about once a day. Previously, an entity surveilling
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer 'about once a day'. The exact distribution seems too low-level for a summary write-up, and people who are interested can click through to the PR for full details.

harding and others added 4 commits May 6, 2020 06:20
Authored-by: Roman Taranchenko
Co-authored-by: David A. Harding <dave@dtrt.org>
Authored-by: Michael Folkson <michaelfolkson@gmail.com>
Co-authored-by: David A. Harding <dave@dtrt.org>
@bitschmidty bitschmidty force-pushed the 2020-05-06-newsletter branch from a418bc6 to 7714654 Compare May 6, 2020 11:29
@bitschmidty bitschmidty merged commit fbc154b into bitcoinops:master May 6, 2020
@bitschmidty
Copy link
Contributor

Nice newsletter this week, team!

@harding @michaelfolkson and @rorp from Suredbits all authoring. Also thanks for edits from @jnewbery and reviews from @jonatack and @adamjonas

@michaelfolkson
Copy link
Contributor

Thanks @bitschmidty. Very impressed with the rigor and thought that goes into these. I was already a fan but you get a new perspective trying to get something in. Keep me posted with how the transcript section is received. I'm interested in how much use people get out of the transcripts (if any) and which ones in particular are useful. Other than engagement with Bryan's tweets I am flying a little blindfolded on this. Thanks for all your work on this, it is a fantastic resource.

@harding harding mentioned this pull request Mar 20, 2024
2 tasks
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