Repository navigation
Conversation
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. |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
|
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
left a comment
There was a problem hiding this comment.
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
imports the Scroll posts as background chapters, converted from Substack's HTML
closes #72