BSV USA Associationin formation

Market access

The BSV Association call, Wednesday October 14

For the organizers, Gavin479 words/3 min read/modified

A first draft, prepared with AI assistance. Nothing in it is decided.

Contents · 6 sections
  1. 1What the call is
  2. 2John's program, the pre-read Connor receives
  3. 3The association segment, five minutes at the end
  4. 4What John will not say
  5. 5What comes back to the team
  6. 6Decisions we need from reviewers

1What the call is

John Calhoun speaks with Connor Murray of the BSV Association on Wednesday October 14 at 2:00 PM Eastern (7:00 PM London, 8:00 PM Zug). Connor may bring colleagues. The call was set up before the association existed, for John's own technical program, and that stays its first purpose. The association is the closing item.

2John's program, the pre-read Connor receives

Four public pages went to Connor on Monday morning. They describe an executable, machine-checked specification of BSV script consensus, a harness that runs SV-node, Teranode and the SDKs against it and produces a witness transaction for every disagreement, the application-layer machines above it, and the open Rust stack checked against them.

  1. The briefing: https://pub-0c965344954142909622d4c2aed91f87.r2.dev/cdn/JZTw98tksZgEranzhZLVpG
  2. Set in stone, why this compounds on BSV: https://pub-0c965344954142909622d4c2aed91f87.r2.dev/cdn/Wn1FEaqSnHqGSW2ZNERaay
  3. The node specification: https://pub-0c965344954142909622d4c2aed91f87.r2.dev/cdn/CZbX9jhM7P9VsREndwz9b6
  4. Write it down once, the method: https://pub-0c965344954142909622d4c2aed91f87.r2.dev/cdn/EhvDL7wnPjaZ5uEtN3T724

Why this matters to the association: when a listing team asks what changed since the 2021 attacks, part of the answer is a specification anyone can run and conformance evidence for every implementation. The program is John's. What the association adopts from it is a board decision under the conflict-of-interest policy.

3The association segment, five minutes at the end

One sentence opens it: John is the named Director of BSV USA, a US market-access working group in formation, and it wants to work with the BSV Association rather than around it. Then four asks.

ask acceptable outcome
A working-group MoU: BSV USA on US market access, the BSVA on protocol and brand agreement in principle, a named reviewer on their side, a date to review the draft
What "relistings underway" means, venue by venue, so nobody duplicates an application a shared tracker with venues coded where confidential, one contact per venue
A joint public line: neither body funds, brings or threatens litigation against exchanges wording agreed in principle, a named signer
Connor as a guest on the next weekly Space a date and the topics cleared

The MoU draft is in this packet. It is a leave-behind sent by email the day after the call, not a document to negotiate on the call.

4What John will not say

No listing dates or approvals, no funding, no formation documents that do not exist yet, no rename, nothing about the Robinhood contact until it is verified, nothing that binds the BSV Association.

5What comes back to the team

Within a day of the call: who was on it, what was agreed on each ask, the next date, and the MoU as sent. Nothing about the call is posted publicly before then.

6Decisions we need from reviewers

For Organizers, Gavin unless an item names someone. Reply in the group chat with the document and the number, for example "The BSV Association call, Wednesday October 14 D2".

  • D1
    Is there a fifth ask the association should make of the BSV Association on this call?
  • D2
    Should the MoU be sent before the call as well, or only after?
  • Something wrong or missing? Say so in the group chat. How to comment.