• Start recording
• Welcome & antitrust notice
• Introduction of new members
• Agenda review

• Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.
• New Members:

• ACTION: Drummond Reed to see if 15:00-16:00 PT / 23:00-24:00 UTC (after daylight savings) will work for APAC members and then set up the calendar invite starting Thursday Nov 4.
• ACTION: Drummond Reed to work with LF staff to add TF members to the TSWG mailing list.
• ACTION: Drummond Reed to add edit permission for Scott Perry and offer it up to any other member who wants to offer their proposal.
• ACTION: ALL to submit any new or revised proposals to the Protocol Stack Diagram slide deck before our meeting next week.

Suggestions to simplify admin and note-taking:

• Publish one Meeting Notes page for each set of Thursday meetings (not two separate pages).
• Keep the notes from the first (NA/EU) meeting, then save the page.
• Re-open editing of the page for the second (APAC) meeting and append notes for each agenda item.
• Post the combined notes and Action Items after the APAC meeting.

• Listen to the Oct 15 A16Z podcast "Crypto Security and the New Web3 Mindsets for Users". If you don't have time for all 30 mins:
  • Start at 27:00 and listen to 28:30 to hear the part about "a security network" (which pretty much exactly describes what we are building with ToIP).
  • Then listen from 28:55 to 30:45 to understand why they recommend using DIDs to have as many keys as you want and be able to rotate keys.

• The Community Review draft of Design Principles for the ToIP Stack is ready.
• We will review the document for the key principles that apply to the ToIP protocol stack.

• Do we have consensus about the Hourglass Principle?
• Do we agree on Sam Smith's "waist and neck" diagram (that he got from another paper)?
• If so, how does this affect the layering of the protocols immediately above and below?
• Is there agreement that the trust-spanning layer is a DID-to-DID communications protocol?
• What are the candidates for that protocol?

• Review decisions/action items
• Planning for next meeting