Add supercharging-transactions-with-async-payjoin review to tabconf/2024

[muchai254]

This PR adds supercharging-transactions-with-async-payjoin transcript review to the tabconf/2024 directory.

[github-actions]

Your Transcript Preview is ready:

• tabconf/2024/supercharging-transactions-with-async-payjoin
• View All Transcript Sources

[dillamondgoat]

AI suggestions from the original transcript. May contain errors or hallucinations; please verify.

Omitted Sentences Analysis
In accordance with the critical guideline to NOT summarize or omit, and to preserve the speaker's original intent, vocabulary, and full narrative, the v1.md file is highly successful.

• No Major Omissions: Comparing the raw YouTube transcript to v1.md, the AI did an exceptional job retaining the speaker's full narrative. It successfully removed minor audio distractions ("um," "uh," "you know") without summarizing rambling sentences or deleting messy stories.
• Correct False Start Removal: In one instance describing the UI for the Nolooking project, the raw audio included a heavy stutter: "it would just it would o sorry it would fund". The AI accurately condensed this false start to "and then it would fund", which perfectly aligns with the clean verbatim guidelines.
• One Minor Word Drop: At the very end of the presentation, the speaker concludes with, "All right, thank you guys". The AI dropped the final word, ending abruptly at "All right, thank you".

Timestamped List for Contributors
To fix these issues easily and ensure accurate coherent paragraphing, contributors should navigate to the following timestamps to make direct edits:

• 00:00:05: Change multiple instances of "PageJoin" to "Payjoin" and "pagejoin.org" to "payjoin.org".
• 00:16:00 (Approx.): Fix "KoiJoin" to "CoinJoin".
• 00:19:00 (Approx.): Fix "BIF-78" to "BIP 78".
• 00:20:00 (Approx.): Fix "PSPT" to "PSBT".
• 00:29:00 (Approx.): Change "page one enabled" to "Payjoin enabled" (this error occurs twice). Fix "Thunder Hub" to "ThunderHub".
• 00:30:00 (Approx.): Change "no looking project" to "Nolooking project".
• 00:35:00 (Approx.): Change "PageOin" to "Payjoin" and "pageoindevkit.org" to "payjoindevkit.org".
• 00:35:30 (Approx.): Change "bit 77" to "BIP 77" and "Noster" to "Nostr".
• 00:36:45: Change "Nostra relay" to "Nostr relay" in Speaker 0's response.
• 00:37:49: Change "start 9" to "Start9". In this same sentence, change "alternative or altruistic" to "altruistic" (the speaker stammered "alter or altruistic" which the AI incorrectly formalized as "alternative").
• 00:39:15: Fix "Waxwang, Waxwing, I guess Waxwing Pageoin" to "waxwing, I guess waxwing Payjoin".
• 00:40:00: Change "Rayify" to "rifi" (occurs twice) and "PageOne" to "Payjoin".
• 00:42:25: Fix "improvement over PageWide" to "improvement over Payjoin".
• 00:44:54: Change "PageOin" to "Payjoin" (occurs twice in Speaker 0's block).
• 00:47:46: Add the missing word "guys" to the final sentence to restore the original "All right, thank you guys".

[dillamondgoat]

AI suggestions from your submitted transcript. May contain errors or hallucinations; please verify.

While many of the errors have been successfully addressed (such as correcting ThunderHub, nolooking project, Coinjoin, BIP 77, BIP 78, Nostr, and adding the missing word "guys" at the end), there are still several critical jargon errors and transcription guideline violations that were missed in this update.

Here are the remaining issues in v2.md that still need to be fixed:

1. Uncorrected Bitcoin Jargon & Typos

• 00:00:05: The website is still incorrectly spelled as "pagejoin.org" instead of "payjoin.org".
• 00:20:00 (Approx): The acronym for Partially Signed Bitcoin Transactions is still incorrectly written as "PSPT" instead of "PSBT" in the sentence: "then the sender will finalize that PSPT and broadcast it".
• 00:29:00 (Approx): The AI hallucination "page one enabled" is still present (twice). It should read: "if the Lightning server is Payjoin enabled and her wallet is Payjoin enabled".
• 00:37:49: The node software is transcribed as "start nine" but should be properly capitalized and formatted as "Start9".
• 00:40:00: The developer handle is incorrectly spelled and linked as "reyify (https://reyify.com/)". It should simply be "rifi".
• 00:44:54: Payjoin is misspelled as "Pagejoin" in the sentence "Speaking of distribution of Pagejoin...".

2. Clean Verbatim Violations (Failed to Remove Stammers/False Starts)
The Review Guidelines strictly state to remove minor audio distractions like stammers and immediate false starts. The v2.md file failed to clean these up in two specific places:

• 00:37:49: The text says "your own alternative or altruistic motive". The speaker stammered here; it should be cleaned up to just "your own altruistic motive".
• 00:39:15: The text says "Waxwang, Waxwing, I guess Waxwing Payjoin". This is a severe stammer that needs to be cleaned up to simply "waxwing, I guess waxwing Payjoin".

You will need to do one more targeted pass on v2.md to clear out these remaining errors so that it perfectly aligns with the Review Guidelines.

---

1. Frontmatter (Tags, Date, Speakers, Categories)
The general format of the metadata block at the top of the document is correctly structured as a list. However, there is a typo in the title:

• Title Typo: The title is written as 'Supercharging Bitcoin Transactions with Asyncronous Payjoin'. "Asyncronous" should be corrected to "Asynchronous".
• Tags: Listed correctly ('payjoin', 'coinjoin', 'psbt', 'payment-batching', 'coin-selection').
• Date: Formatted correctly ('2024-12-22').
• Speakers: Listed correctly ('Brandon Lucas').
• Categories: Listed correctly ('Privacy Enhancements', 'Fee Management').

2. Titles Format (Chapter Headings)
The document fails to follow the Review Guidelines for chapter title formatting.

• Error: The transcript currently uses #### (H4) formatting for all of its chapter headings (e.g., #### Introduction & talk overview, #### Satoshi's privacy assumption and the discovery of Coinjoin).
• Fix: The Review Guidelines explicitly state to "Start chapters with H2 formatting" (which uses ##). All chapter headers need to be changed from #### to ##.

3. Speaker Attribution Identification
There are major missing speaker attributions and formatting errors in the transcript, specifically in the Q&A section and at the beginning:

• Main Speaker Mix-up: At the start of the transcript, the main speaker is incorrectly labeled as Speaker 0: 00:00:05. Since he introduces himself immediately, this should be accurately attributed to Brandon Lucas: 00:00:05.
• Missing Q&A Attributions: The entire Q&A section fails to identify the individuals asking questions. The Review Guidelines require using square brackets for infrequent speaker contributions (e.g., [Audience]:). You will need to add [Audience]: to the following unmarked questions and comments:
  • "So while the directory seems very lightweight in terms of service..."
  • "Part one of the question, so go ahead."
  • "I guess as a follow-up to that, it seems to me..."
  • "Thanks so much for everything. You gave a great example..."
  • "Hi, I'm curious on the asynchronous aspect..."
  • "Speaking of distribution of Pagejoin..." (Note: payjoin is also misspelled here).
  • "Just briefly, in the spirit of busy polling bad..."
  • "Is because WebSockets is a raw TCP connection..." (This is another audience member answering).
  • "I think we're good. Thank you Brandon." (Likely the Host/MC).

[muchai254]

00:40:00: The developer handle is incorrectly spelled and linked as "reyify (https://reyify.com/)". It should simply be "rifi".

From the presentation, I could see that Brandon was looking up https://reyify.com. I'm not sure where rifi is coming from.

00:37:49: The text says "your own alternative or altruistic motive". The speaker stammered here; it should be cleaned up to just "your own altruistic motive".
00:39:15: The text says "Waxwang, Waxwing, I guess Waxwing Payjoin". This is a severe stammer that needs to be cleaned up to simply "waxwing, I guess waxwing Payjoin".

Not sure if these are stammers.

Missing Q&A Attributions: The entire Q&A section fails to identify the individuals asking questions. The Review Guidelines require using square brackets for infrequent speaker contributions (e.g., [Audience]:). You will need to add [Audience]: to the following unmarked questions and comments:
"So while the directory seems very lightweight in terms of service..."
"Part one of the question, so go ahead."
"I guess as a follow-up to that, it seems to me..."
"Thanks so much for everything. You gave a great example..."
"Hi, I'm curious on the asynchronous aspect..."
"Speaking of distribution of Pagejoin..." (Note: payjoin is also misspelled here).
"Just briefly, in the spirit of busy polling bad..."
"Is because WebSockets is a raw TCP connection..." (This is another audience member answering).

This is actually implemented in the latest commit, not unless I did it wrongly. This is the first time I am handling [Audience] attribution. Payjoin was correctly spelt here.

The rest of the suggestions from the latest comment were accurate and have been addressed. Requesting re-review.

[muchai254]

Requests have been implemented.

[dillamondgoat]

@muchai254 Please address the last typo. Thank you for your contribution!
@0tuedon Mind giving this a final look? I think it's good to go.