BSV USA Association: Claims ledger

1The rule

Nothing is said publicly until it sits in the data room with evidence.

This is the proposed rule for adoption. It covers posts, Spaces, interviews, applications, and statements made for the association. An unsupported historical claim stays in this ledger. It must not be repeated as established fact. A proposal must be called a proposal. A conversation, a support reply, a listing review, and an approved listing are different events.

Nancy (@NasdaqNancy) is the pseudonymous founder. John Calhoun (@johncalhooon) is the named Director and owns the technical half of the data room. Nancy owns the public claims record. John checks technical evidence. Gavin coordinates legal review with qualified counsel. The owner column assigns proposed follow-up responsibility. It does not establish a professional engagement or confirm the claim.

2Scope and status

This ledger covers substantive claims and commitments by the host or in association material found in the public-record research through 11 October 2026. The period starts on 28 September. It includes authored posts, agenda images, the draft CoinMarketCap profile, the diligence-plan images, and public Space claims described in that research. Full collected post text was checked where the research appendix used excerpts. Dates are Eastern time, UTC minus four hours. Space rows use the meeting date, even if the linked announcement was posted earlier.

Bare requests to call, greetings, jokes, personal device details, and reposts without added assertions are not separate association claims. Third-party comments do not become association statements merely because someone attended a Space. Policy proposals and predictions are labeled as such. Related parts of one claim share a row. Repeated material claims retain their post links. This is a bounded collection, not a claim that every post on X was captured.

• verified: Evidence supports the exact, limited claim in the row. For a proposal or invitation, only its publication is verified. This does not verify delivery or adoption.
• unverified: Evidence is missing, incomplete, conflicting, or does not support the stated scope. This does not mean false.
• withdrawn: The speaker has expressly retracted the claim. Keep the original and add the dated public withdrawal.
• corrected: A dated public correction and evidence support replacement wording. Preserve both versions.

No express withdrawal or public correction of the disputed claims has been authenticated for this draft. A contradiction is not silently marked corrected. A suggested correction is not an adopted statement.

This draft contains 139 rows: 27 verified within their stated limits and 112 unverified. Many verified rows establish only that a proposal or invitation was published. None verifies the claimed funding, legal formation, institutional agreements, Robinhood meeting, or an exchange listing commitment.

All hyperlinks below lead to public posts. Public primary documents are identified by publisher and title in the evidence notes. Private chat is not quoted or linked. A post proves that an assertion was made. It does not prove the asserted funding, meeting, legal status, or approval.

3Public claims

4Maintenance procedure proposed for adoption

Adding and checking claims. Nancy adds a row before any new public statement by the association. Anyone may flag an omission or submit evidence. John may add technical rows. The person making a claim supplies the evidence. Preserve the post ID, date, exact scope, evidence reference, owner, status, and last review date in the evidence register. Keep a dated public snapshot where permitted, since posts can change or disappear. New factual claims start as unverified. They cannot be announced as fact until the evidence is checked.

John reviews technical and counting evidence. Qualified counsel reviews legal claims through Gavin. An additional organizer checks Nancy's own factual claims. The reviewer records what was checked, the evidence date, and the approved public wording. Every status change must identify its claim ID, previous status, new status, reviewer, date, and evidence reference. An invitation authenticates only an invitation. A funding pledge authenticates only its stated terms. Neither proves completion. Restricted evidence needs a consented, public verification summary before it can support a public claim. Keep private correspondence out of the public ledger.

The weekly Space. Nancy puts ledger review on every weekly public Space agenda. John reports technical gaps. Gavin reports the status of counsel review without disclosing privileged advice. Read new rows, overdue evidence, contradictions, status changes, and corrections. Set an owner and due date for each open item. Publish recording-backed minutes and a change log afterward. Record any missed review and a new date. A vote cannot turn an unsupported statement into a verified fact.

Corrections and withdrawals. Preserve the original row and post link. Add the dated correction or withdrawal, replacement wording, evidence, reviewer, and reason. Do not erase an embarrassing claim or treat a deleted post as a retraction. For time-sensitive facts, state the date through which the evidence applies. Reopen a row as unverified if the evidence no longer supports its scope. Material errors should be corrected promptly rather than held for the weekly meeting. An unresolved Robinhood identity must not be described as confirmed impersonation.

The monthly BSV anchor. The proposed cutoff is the final day of each month at 23:59 UTC. Nancy closes the reviewed version. John exports the exact ledger bytes from the recorded Git commit into an immutable monthly snapshot, such as claims-ledger-2026-10.md. Publish that downloadable file as UTF-8 with LF line endings and a final newline. Record its byte count and SHA-256 digest. Preserve old snapshots when the live ledger changes.

After approval of a fee budget and payer, John or the authorized publisher writes that digest to a data output in a BSV mainnet transaction. Include a protocol label, format version, month, full Git commit, byte count, and previous anchor transaction ID. Use the following fields, with actual values replacing placeholders:

type: bsv-usa-claims-ledger
version: 1
period: 2026-10
algorithm: SHA-256
digest: <64 lowercase hexadecimal characters>
bytes: <exact byte count>
git_commit: <full commit identifier>
previous_txid: <previous anchor transaction ID, or null for the first>

Publish a separate receipt with the snapshot location, digest, transaction ID, data-output index, payload encoding, block height and hash, confirmation count, and check time. Identify the authorized publishing key or account. Do not insert the receipt into the already hashed snapshot. Put it in the release record and the next ledger version. If the transaction is unconfirmed or reorganized out, mark that state and preserve any replacement receipt.

How anyone checks it. Download the dated snapshot as a file, not text copied from a rendered page. Run:

shasum -a 256 claims-ledger-2026-10.md
wc -c < claims-ledger-2026-10.md

Compare the digest and byte count with the receipt and the decoded transaction output. Independently retrieve that BSV mainnet transaction using a node or public explorer. Confirm its block inclusion and current confirmations. For a proof-based check, verify the transaction's Merkle proof against the accepted header chain. Check the publishing identity and previous anchor reference as well. A changed byte produces a different digest. The anchor establishes a commitment to those bytes by the time of inclusion. It does not prove that the claims are true, the ledger is complete, or the publisher had legal authority.

Current anchor status: Not published. No transaction has been sent and no money has been spent for this draft. Network fees require an approved payer and budget. Until then, publish the local digest and mark the on-chain anchor pending. A local hash is not an on-chain record.