setavenger

Silent Payments notifications via Nostr

This write-up has the goal to discuss the approach of sending notifications for incoming Silent Payments transactions via Nostr. The design is an extension of the discussions around "Stealth addresses using nostr" which had a Nostr-only approach.

The design allows for notifications being sent outside of Nostr so for a clearer structure there is a Silent Payments and a Nostr part. The Silent Payments outlines why the schema is suggested as it is and the Nostr part discusses the using nostr as the communication layer for the notifications.

Silent Payments

Silent Payments offer a novel way for receiving payments without interactivity.

jamesob

// Open Inspect -> Console, copy-paste this in.

function load_all_gh_comments() {
  let buttons = Array.from(document.querySelectorAll('button'));
  let get_with_text = (text) => buttons.filter((b) => b.textContent.includes(text));
  let load_more_buttons = get_with_text("Load more");
  let nothing_loading = get_with_text("Loading…").length === 0;

  if (load_more_buttons.length === 0 && nothing_loading) { 
      console.log("done loading comments"); 

chjj

On October 11th, 2022, @ajtowns publicly disclosed a zero-day consensus fault in btcd in a github issue. The issue was posted on a public repo viewable by anyone.

According to gharchive.org logs, the github issue remained up for at least 10 hours before being deleted. The original github issue resided at https://github.com/Roasbeef/btcd/issues/35

The issue and comment can be found and reconstructed from the following JSON dumps:

• https://data.gharchive.org/2022-10-11-3.json.gz
• https://data.gharchive.org/2022-10-11-13.json.gz

Reconstruction of the issue and comment by @ajtowns