Contributing

April 20, 2026 ยท View on GitHub

This report is a moving snapshot of a fast-changing landscape. Corrections and additions are welcome via pull request.

What we accept

  • Factual corrections with a primary-source citation (official press release, GitHub repo, IETF draft, etc.). Secondary reporting is OK if a primary source isn't available - flag it as such.
  • New protocol entries that fit the report's existing buckets (HTTP 402, traditional-rail, commerce, regional). Include a brief rationale for which bucket and what differentiates the protocol from existing entries.
  • Updates to existing entries when launch dates, partner counts, or technical details change. Include the source URL and the date you verified it.
  • Footnote URL fixes if cited sources move, return 403, or no longer match the cited claim.

What we don't accept

  • Promotional additions to Section 6 or anywhere else. Vendors of competing products may submit factual corrections to existing protocol profiles but cannot add their product as a standalone entry.
  • Unsourced claims, including ones backed only by social media posts or vendor marketing pages.
  • Speculation about protocol roadmaps, market share, or company strategy that isn't grounded in published statements.

How to submit

  1. Fork the repo
  2. Make your edit on a feature branch
  3. Open a PR with:
    • The claim being added or corrected
    • The primary source (URL + date verified)
    • A brief explanation of what changed and why

Maintainer review usually takes a few days. Major restructuring (new sections, bucket changes) should be discussed in an Issue first.

House style

  • Hyphens, not em-dashes
  • Footnotes for every load-bearing factual claim
  • Quotes from sources should be exact (verbatim) - if paraphrasing, drop the quotation marks
  • Hedge superlatives ("most", "first", "only") unless directly supported by the source