BSV USA Association: Data room index

The packet

The data room is what an exchange's listing team would receive: six dated documents, an evidence register, and a change log. Each document must say who owns it, what has been checked, and what is missing. The same core packet goes to each venue. A short cover sheet maps it to that venue's current questions. No exchange has accepted this packet.

Nancy (@NasdaqNancy) is the pseudonymous founder. John Calhoun (@johncalhooon) is the named Director and owns the technical half. Other assignments below are proposed. Gavin coordinates legal work with qualified counsel. This does not identify Gavin as retained counsel or imply that a law firm has been engaged.

The host proposed a six-document packet in the 10 October public Space, at 08:18 to 10:28. The later public plan images used different headings. This index follows the six headings below. It places screening evidence in documents 2 and 3, trading commitments in document 6, and the membership record in document 5. It adds an explicit litigation statement. It does not treat the screenshots as completed diligence or as an exchange checklist.

Status is based on material reviewed as of 12 October 2026. Missing means not supplied or authenticated for this packet. It does not prove that a document cannot exist elsewhere. Hyperlinks in this draft lead only to public posts. Other public source documents are identified by publisher and title so reviewers can locate them. Private correspondence and chat are not quoted or linked.

1Security and incident report since the 2021 attacks

Owner: John. Seek an independent technical reviewer. No reviewer has been appointed in this draft.

Contents outline:

• An incident register from the 2021 reorg attacks through the report date. A reorg replaces previously accepted blocks. Record UTC dates, block heights and hashes, depth, double-spend evidence, affected services, losses if established, response, and recovery. Separate observed events from reported allegations.
• A coverage map for every period. Name the data sources, retention limits, outages, and unknown intervals. An empty search result is not proof of an incident-free period.
• A public reorg monitor. Publish its address, source version, observation points, competing tips, chain work, reorg depths, last successful observation, and alert history. Include a downloadable event log. Name an operator and backup. Test alerts and record the results. Show outages as outages.
• Confirmation-depth guidance for exchange deposits. State the network assumptions, deposit-value tiers, monitoring inputs, and residual risk. Set halt and resume rules for competing tips, reorgs, stale data, and abnormal hashpower. Have the receiving venue approve its own thresholds. Do not invent a universally safe confirmation count.
• Hashrate transparency. Publish the calculation method, observation windows, difficulty inputs, estimated network rate, pool shares, and unknown share. Distinguish pool labels from control of mining power. Explain uncertainty and concentration. Label any rented-hashpower estimate with its date and limits.
• Evidence for each claimed improvement. Include release versions, configurations, incident exercises, independent findings, unresolved issues, and an emergency contact. Explain that more confirmations and SPV do not remove majority-hash risk.

Status today: The 2021 baseline is documented. Robinhood's 2022 Form 10-K describes the August 2021 attack. The same filing says support ended on 25 January 2023 after a listing-framework review. It does not establish that the attacks were the sole reason. No complete history since 2021, monitor deployment, tested thresholds, current concentration series, or independent safety conclusion has been supplied.

Sources: Robinhood Markets, 2022 Form 10-K, pages 49 and 56, SEC accession 0001783879-23-000045, checked on 12 October. The public safety-plan proposal identifies the work sought. The finished report must also cite dated node logs, block headers, affected operators' incident reports, and independent observations. Those records remain to be assembled.

Missing: The incident dataset and its coverage map; public monitor and logs; named response coverage; measured hashrate series; reviewed deposit policy; test evidence; independent review. Do not publish a claim of no attacks since 2021 or of proven safety.

2Technical integration guide

Owner: John. Nancy and Gavin help obtain written provider answers. Each provider must confirm its own services.

Contents outline:

• A listing-grade node package built around headers and transaction proofs. Include pinned source versions, licenses, build instructions, release hashes, deployment settings, resource measurements, dependencies, and an upgrade and rollback process. Provide an exchange engineer with a reproducible setup and a support contact.
• Simplified Payment Verification, or SPV. Check header linkage, proof of work, applicable difficulty rules, chain work, and Merkle inclusion proofs. Define the trusted inputs, peer selection, and proof sources. Explain what needs a full validating node or another service. Inclusion in a block does not prove every consensus rule was checked by the client.
• Deposit and withdrawal flows. Cover address formats, network identification, BSV and BCH separation, transaction creation, fee policy, UTXO management, broadcast, confirmation tracking, and reconciliation. Show how credits are held or reversed during a reorg.
• Wallet and custody runbooks. Document signing controls, key custody, approvals, backups, recovery, audit logs, deposit detection, withdrawals, and incident response. Keep keys and credentials out of the packet. Identify the legal custodian separately from its software provider.
• Tests for invalid and missing proofs, stale headers, competing tips, double spends, reorg recovery, provider outages, restoration from backup, and realistic load. Record the environment and results. Test-network success alone does not establish production readiness.
• A provider matrix for custody and transaction screening. Record product, native BSV mainnet asset identifier, supported operations, region, limitations, source date, and confirmation contact. Include Fireblocks, BitGo, Anchorage, and screening providers as enquiries, not assumed partners.

Status today: In the 10 October Space, around 24:14 to 25:24, David Case described using headers and transaction proofs. Speaker attribution comes from a transcript without diarization. This is an architectural lead, not evidence that an exchange package has shipped. The public bsv-blockchain/block-headers-service repository exists. No association release, deployment benchmark, or exchange acceptance test has been supplied.

Fireblocks' public Supported Digital Assets catalog includes Bitcoin SV and Bitcoin SV Test, checked on 12 October 2026. This is a catalog observation only. Written confirmation of the required product, region, account access, signing, deposits, withdrawals, and support terms is still missing. Qualified custody has not been established by that catalog entry. Do not report either full integration approval or lack of all Fireblocks support.

Sources: The public Space; BSV Blockchain's Block Headers Service repository and BSV Code Academy's SPV Verification guide; Fireblocks' Supported Digital Assets catalog. Pin exact upstream revisions in the eventual evidence register. Use provider-issued confirmations for commercial scope. The public plan also proposes screening evidence, which still needs authentication.

Missing: A packaged release; independently reproduced build; configuration and tests; recovery drills; custody confirmation; screening coverage and limits; named support arrangements. No integration sponsorship or paid service is authorized here.

3Counsel's classification memo

Owner: Qualified US counsel selected through Gavin or a BSV Esq. referral. John supplies technical facts. Nancy supplies organizational facts. Appointment and scope are unresolved.

Contents outline for a commodity-style letter:

1. Identify the client, asset, recipient, jurisdictions, review date, purpose, and limits on reliance. Distinguish native BSV from any token or fundraising arrangement using the association's name.
2. Describe the facts counsel has checked. Cover issuance, mining, distribution, control, utility, governance, promotional claims, fundraising, and any rights or promises to holders.
3. Analyze the applicable securities and commodity questions using current primary law. Explain assumptions, contrary facts, unsettled questions, and facts that could change the conclusion. A requested commodity-style conclusion is not a predetermined outcome.
4. Address the venue's compliance questions. Identify relevant sanctions and transaction-screening evidence, jurisdiction limits, and regulatory proceedings. Separate the association's obligations from the exchange's obligations.
5. State the actual conclusion and qualifications. Attach the factual record and authorities. Identify counsel, firm, licensing jurisdiction, signature, and date. Set a review trigger for material changes.

Status today: No signed opinion, engagement letter, or authenticated appointment is in the reviewed packet. A public plan calling Gavin counsel of record does not establish qualifications or a retainer. This outline makes no legal classification finding.

Sources: The public packet proposal and plan images. Bitstamp's Digital Asset Listing Framework, legal and compliance sections, was checked on 12 October. Counsel must select and cite current statutes, regulations, court decisions, and official agency materials in the memo.

Missing: Client identity and authority; counsel and conflict checks; engagement scope; fact schedule; current legal analysis; signed opinion; permission to share. Cost estimates in posts are not an approved budget or funds received.

4Litigation posture

Owner: John, with Nancy providing organizational records and Gavin coordinating counsel's review. An authorized signatory must be established before signature.

Contents outline: A one-paragraph statement, signing authority, approval record, review date, and a factual schedule of relevant funding and proceedings. Any summary of third-party litigation must use current court records. The association cannot speak for other organizations, claimants, funders, or individual members acting independently.

Draft statement for signature after verification:

The BSV USA Association funds, brings or threatens no litigation against any exchange. It does not direct or authorize another person to do so on its behalf. Its approach to exchange access is voluntary technical, legal and commercial review. This statement concerns the association and conduct on its behalf. It makes no representation about independent third parties or the outcome of their cases. We will publish a dated correction if these facts change. Signed for the BSV USA Association: [authorized signatory], [capacity], [date], [signature].

Status today: Unsigned and not adopted. Nancy has publicly rejected the prior litigation approach. That statement is not a treasury audit, an adopted policy, or a representation binding unrelated parties.

Sources: That public post and the public account of litigation. The latter attributes its information to an AI response and is not a court source. Before signature, counsel needs organizational records, payment records, relevant agreements, and current official case records.

Missing: Verification of the paragraph's factual scope; any past payments or commitments; authority to sign; counsel review; adoption and signature. Do not promise settlement or discontinuance of someone else's case.

5Governance and formation status

Owner: Nancy, with John as named Director and counsel responsible for legal verification.

Contents outline:

• A status sheet: organizing group, proposed legal name and form, jurisdiction, filing date and number if filed, and registry evidence. State clearly when an entry is unknown or draft.
• A role map naming Nancy as pseudonymous founder and John Calhoun as Director. Record each person's responsibilities, appointment record, signing power, conflicts, and limits. Do not identify a real person behind Nancy's account.
• A register of governing documents. Separate drafts from executed documents and adopted resolutions. Cover charter, bylaws, membership eligibility, voting, quorum, elections, conflicts, antitrust policy, and complaints.
• A membership register with consent and defined categories. Separate members, volunteers, advisers, donors, and listeners. Explain US membership and overseas participation. Preserve poll questions, options, dates, totals, eligibility, and any binding effect.
• A treasury status sheet. Separate donations received, conditional pledges, operating costs, professional fees, and market liquidity. Include authority to spend, reporting, and any restrictions.
• A relationship map for the existing BSV Association and other bodies. List agreements only when executed. Record the limits of any mandate concerning the coin, ticker, protocol, and outside organizations.

Status today: Public invitations, two public Spaces, agendas, a reported association-name vote, and public proposals exist. John Calhoun is the named Director. His formal appointment instrument has not been supplied for this packet. Nancy's formation and funding statements do not supply registry records or signed documents. No incorporation, tax status, signed governing packet, verified funding balance, or formal BSVA affiliation has been established in the reviewed material. Work being drafted is not adoption.

Sources: Public posts on documents sent for signature, documents described as finished, meeting 1 priorities, overseas volunteers, reported name vote, and meeting 2 agenda. These evidence statements and proposals. Obtain registry documents and signed records to establish legal facts.

Missing: Filing evidence; signed documents; appointment and signing authority; membership and voting rules; poll archive; budget and funding records; adopted policies; any formal affiliation agreement. No draft legal form or tax treatment should be presented as decided.

6Demand and liquidity evidence

Owner: Nancy. John owns the counting method and reproducible report. A human reviewer checks the records before release.

Contents outline:

• Define the period, venue, geography, and population counted. Count people, businesses, and verified customers separately. One person counts once per venue per reporting period. Deduplicate across channels. Report repeat requests separately. Show claimed customer status separately from checked status.
• Record consent, date, source, venue, broad location, and evidence quality for each eligible entry. Use a private random record ID for deduplication. Publish aggregate totals and the method. Redact account numbers and identifying screenshots. A post, wallet, transaction, like, or poll vote is not automatically a unique customer.
• Keep request counts, membership, stated buying interest, operating donations, liquidity pledges, and funded trading commitments separate. Do not convert hypothetical purchase amounts into money committed.
• Report venue-specific order-book depth, spread, slippage for stated order sizes, volume, withdrawal availability, and observed market-maker coverage. Include dates, sample windows, quote currency, geography, source, and known data gaps. Flag suspected wash activity. Transaction throughput alone does not establish trading liquidity.
• Obtain written market-maker terms if offered. Record identity, capital, venue, pairs, quote depth, duration, conditions, and termination rights. An expression of interest is not an executable commitment.
• Agents count only and never message exchanges. They may deduplicate and summarize authorized records. They must not send emails, DMs, support tickets, or replies, impersonate customers, or multiply requests. Any human request must reflect that person's own interest through an appropriate official channel. Do not organize repeated support messages.

Status today: The record contains public demand assertions, an automated-message claim, and a proposed 1,000-person sheet. It contains no authenticated unique-customer total or market-maker contract. The suggestion that 1,000 requests trigger Robinhood review is unverified. No volume, funding, or liquidity figure in this packet has been certified.

Sources: Nancy's automated-message claim, Kraken demand assertion, and proposed demand and trading documents. Use authorized request records, provider-issued market data, and signed trading terms for the actual report. Public post metrics establish only those metrics at their capture time.

Missing: Counting rules approved by reviewers; consent and retention rules; deduplicated evidence; market observations; independent checks; any verified trading commitment. No outreach or money movement is part of preparing this index.

Release and venue handling

John maintains versions, checksums, evidence references, and a change log. Nancy maintains claims and the submission register. Counsel clears legal representations. Each release needs a date, owner, reviewer, file hash, and list of unresolved items. A public statement must already have evidence in the data room. Restricted evidence needs a shareable verification summary; private chat is not public proof.

The evidence register should connect each factual statement to its claim ID in the claims ledger. Record the source publisher, document or post identifier, relevant page or timestamp, capture date, saved-file hash, reviewer, and permitted public wording. Mark whether a source proves an event, reports someone else's assertion, or describes a proposal. Include an expiry or recheck date for changing facts such as custody support and market access. A release is ready only when a second person can follow those references and reproduce the material checks.

The Bitstamp source is its public Digital Asset Listing Framework, checked on 12 October. Robinhood's acquisition announcement has a 2 June 2025 closing update. Neither source supports a promised listing timetable. Suggested venue order remains a proposal. No application, contact, payment, or chain transaction is authorized by this draft.