Skip to content

import the Scroll posts as background chapters - #90

Draft
bc1cindy wants to merge 1 commit into
fungi-protocol:mainfrom
bc1cindy:scroll-posts
Draft

bc1cindy wants to merge 1 commit into
fungi-protocol:mainfrom
bc1cindy:scroll-posts

Conversation

@bc1cindy

@bc1cindy bc1cindy commented Nov 15, 2026 •

Copy link
Copy Markdown
Member

imports the Scroll posts as background chapters, converted from Substack's HTML

closes #72

Captura de Tela 2026-11-15 às 18 24 55 Captura de Tela 2026-11-15 às 18 25 22 Captura de Tela 2026-11-15 às 18 25 43 Captura de Tela 2026-11-15 às 18 26 10 Captura de Tela 2026-11-15 às 18 26 45

Five posts by Yuval Kogman on Spiral's Substack introduce wallet
clustering, its literature, intersection attacks and CoinJoin design,
as fungi-protocol#72 proposes. They are converted from the Substack API's HTML, with
the newsletter framing removed and links between posts pointing at the
chapters. Each chapter cites its original post. The figures are light
and dark pairs with transparent backgrounds, so they read on any book
theme and on GitHub.

This kind of Venn diagram, with two sets represented by two overlapping circles and the overlapping part highlighted, typically represents an intersection between two sets. Sets are unordered collections of elements, such as rows in a database, numbers, or anything else that can be mathematically defined. The intersection of two sets is the set of elements that are present in both sets. So, for example, within the voter registration list, we might talk about the subset of all entries whose ZIP code is 12345, and the set of all entries whose birth date is January 1, 1970. The intersection of these two subsets is the subset of entries whose ZIP code is 12345 *and* whose date of birth is January 1, 1970. In the Governor's case, there was just one entry in the subset of entries whose attribute values matched his attributes in the voter registration list.

For data sets with different structures, there’s a small complication: if we think of them as sets of rows, then their intersection would always be empty, because the rows would have different shapes. When computing the inner join of two database tables, only the values of columns which are present in both tables are in some sense intersected by specifying something like `JOIN ON a.zip = b.zip AND a.dob = a.dob`, or the less portable `USING(zip, dob)` syntax, but these intersecting values are related to the rows they came from, so the overall structure of linking two data sets is a bit more involved. Note that Sweeney’s diagram depicts the intersection of the columns of the data sets, emphasizing the more primary problem, which is that attributes included in the “anonymized” data set unintentionally had a non-empty intersection with the attributes of other publicly available data sets.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

SQL join example matches DOB to itself

a.dob = a.dob compares the column with itself, so for non-NULL values it matches every zip-compatible row regardless of b.dob rather than intersecting the two DOB columns as the sentence says; it should be a.dob = b.dob.

oakagent · automated · 904a3e1

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

the original post has this too

a.dob = a.dob compares the column with itself, so the join matches on ZIP alone, while the sentence and the USING(zip, dob) example describe matching on ZIP and date of birth

does it make sense to correct it to a.dob = b.dob here?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Yes. a.dob = a.dob is true for every non-NULL row, so the join only constrains ZIP, while the sentence and USING(zip, dob) describe matching on both ZIP and date of birth. a.dob = b.dob is the correction that makes the example agree with the text; the line is still a.dob = a.dob at the head.

oakagent · automated

@yuval-block
yuval-block marked this pull request as draft November 16, 2026 04:59
@yuval-block

Copy link
Copy Markdown
Collaborator

converted to draft until i find all of my originals, there are some formatting mistakes and substack also has latex limitations, however not all of my markdown originals have all the grammar corrections etc

@oakagent oakagent left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Typos in what this pull request adds:

docs/background/faces-of-coinjoin.md

  • l.61 - "PayJoins attempts" → "PayJoins attempt"
  • l.81 - "any the preceding" → "any of the preceding"

docs/background/headaches-of-coinjoin.md

  • l.124 - "broadly is likely" → "broadly are likely"
  • l.164 - "these coins be more" → "these coins would be more"

docs/background/history-of-wallet-clustering.md

  • l.20 - "WikiLeak’s" → "WikiLeaks’"
  • l.32 - "the other production" → "the other output"
  • l.78 - "CoinJoins transactions" → "CoinJoin transactions"

docs/background/intersection-attacks.md

  • l.85 - "sharing it to 3rd parties" → "sharing it with 3rd parties"

oakagent · automated

This branch has not been deployed

No deployments
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.

scroll posts in doc?

3 participants