{
  "schema": "phishdestroy.text-export.v1",
  "object_type": "Published page text and corresponding PDF digest",
  "id": "output_steam_network/index.html",
  "language": "en",
  "title": "Architecture, Not Exploit: The Automation Network — The Steam Dossier",
  "source_url": "https://phishdestroy.io/steam_dossier/output_steam_network/index",
  "source_html_sha256": "3873107bd24d0aac30853e6a6e8a9dd4a856f8ffdfd277728dda8df2055b17a8",
  "exported_at": "2026-09-30T21:13:41.847Z",
  "scope": "Print reading edition. Research prose is retained; raster images and identified visual catalogues are replaced by source links. See editorial_scope for exact omissions. Support archive exports retain the core discussion and link the full gallery.",
  "editorial_scope": {
    "policy": "Research prose, conclusions, methodological limits and analytical tables retained without paragraph truncation. Named catalogues and visual galleries are linked; raster images are not embedded.",
    "linked_sections": [],
    "raster_images_replaced": 0
  },
  "license": {
    "identifier": "CC0-1.0",
    "url": "https://creativecommons.org/publicdomain/zero/1.0/",
    "rights_statement_url": "https://phishdestroy.io/steam_dossier/steam_tos_assets/license-rights.json",
    "rights_statement_sha256": "80d67354f8e5efd65b03696be950fb0f95c188d0089b1604281d0a4daff3f4cb",
    "application": "Authored research materials; third-party materials retain their own rights."
  },
  "pdf": {
    "filename": "output_steam_network__index.pdf",
    "url": "https://phishdestroy.io/steam_dossier/exports/pages/en/output_steam_network__index.pdf?v=print-20260930-links-v6",
    "sha256": "560790b0aa47111d4badbd97317d3b074f8df6a098781330951e5c9f458ff80b",
    "bytes": 65968,
    "pages": 3
  },
  "integrity": {
    "signed_object": "output_steam_network__index.content.json",
    "scope": "The exact UTF-8 bytes of this JSON file. It contains the published text and identifies the corresponding PDF by SHA-256. It is distinct from the separately signed rights statement.",
    "signature_file": "output_steam_network__index.content.json.asc",
    "digest_file": "output_steam_network__index.content.json.sha256",
    "format": "ASCII-armored detached OpenPGP",
    "signing_key_fingerprint": "129FC7F39C40C69D2EF3C329BFCF9E8DD295EE01",
    "public_key": "https://phishdestroy.io/.well-known/pgp-key.txt",
    "verify": [
      "gpg --import pgp-key.txt",
      "gpg --verify output_steam_network__index.content.json.asc output_steam_network__index.content.json",
      "sha256sum -c output_steam_network__index.content.json.sha256"
    ]
  },
  "content": {
    "text": "Dieses Material ist auf Englisch verfügbar.Zurück zum Dossier · Deutsch ↗\nExhibit VII · Technical Architecture Analysis\nSteam Network Architecture — Protocol Fidelity & Ecosystem Analysis\n\nAutomation is Valve's Architecture. Not an Exploit.\n\nWHAT THIS SECTION PROVES\n\nThis module maps the technical topology of 252 developer repositories, 3,320 GitHub profiles, and 4,214 contributor pairs underpinning the Steam automation ecosystem. It proves that third-party automation relies on Valve's official Connection Manager protocol, Protobuf schemas, and Web APIs without exploit code. By engineering algorithmic Steam Guard confirmation tokens and collecting minimum transaction fees up to 66.7%, Valve functions as the intentional architect and primary commercial beneficiary of automated ecosystem operations.\n\n← Back to Executive briefing\n\nWhen Valve addresses regulators, payment processors, or scam victims, it attributes skin theft and market manipulation to \"unauthorized third-party exploits\" and \"rogue illicit automation.\" The engineering reality of this 252-repository network establishes the exact opposite: every automation framework, trading bot, and farming fleet operates strictly within the official protocol definitions, Web APIs, and authentication mechanisms engineered, documented, and monetized by Valve Corporation.\n\nForensic Finding: Conscious Architecture vs. Illegitimate Breach\n\nThe software analyzed in this module — including SteamKit, node-steam-user, ValvePython/steam, and ArchiSteamFarm — contains zero software vulnerabilities, zero memory corruptions, and zero zero-day exploits. They are clean, robust open-source implementations of Valve's proprietary Connection Manager (CM) client protocol, Google Protocol Buffers (Protobufs), and Web APIs. Valve designed these APIs to accept programmatic logins, designed Steam Guard to allow algorithmic confirmation tokens (identity_secret), and collects an advertised 15% fee that escalates to up to 66.7% in Valve's favor on the high-velocity cards and commodity drops that automated botnets liquidate.\n\nPillar 01 · Protocol Fidelity\nOfficial Protobuf Schemas\n\nAutomation libraries do not bypass security gates. They serialize official Protobuf messages (steammessages_clientserver.proto) over TCP/WebSockets directly to Valve's official CM clusters, exactly as the Steam Client does.\n\nPillar 02 · Algorithmic 2FA\nProgrammatic Trade Authorization\n\nThe entire multi-billion-dollar skin trading economy depends on Valve's IEconService API and mobile authenticator TOTP keys. Valve intentionally engineered Steam Guard to enable machine-to-machine trade confirmations.\n\nPillar 03 · Commercial Beneficiary\nMonetized Machine Traffic: Up to 66.7% Fee Floor\n\nValve advertises a 15% fee, but on the high-volume commodity items automated bots trade — trading cards, cases, and cheap drops priced at $0.03 to $0.05 — Valve's two-cent minimum fee floor ($0.01 Steam + $0.01 publisher) extracts 50% to 66.7% in Valve's favor (2¢ taken out of a 3¢ card, leaving the seller with 1¢). Plus $5.00 per account ($26.8M on the scanned fleet alone).\n\nModule 01 · Repository & Protocol Evidence\nPublic Developer & Repository Infrastructure\n\nDetailed forensic catalog of 252 open-source repositories powering Steam automation. Traces how standard software engineering tools implement Valve's published API endpoints without exploits.\n\n252Repositories\n4,554Role Links\nInspect repository evidence →Module 02 · Ecosystem Demographics\nGlobal Engineering Ecosystem Metrics\n\nGeographic and institutional breakdown of 3,320 software engineers contributing to the Steam automation ecosystem, including corporate affiliations across major technology employers.\n\n3,320Engineers\n98,902Connection Pairs\nInspect ecosystem metrics →Module 03 · Interactive Visual Graph\nInteractive Protocol & Developer Network Graph\n\nComprehensive Vis.js interactive network graph mapping repositories, protocol libraries (SteamKit, Steamworks, ASF), and cross-project contributor overlaps. Visually demonstrates the legitimate, interconnected open-source software architecture powering Steam's automation ecosystem.\n\nInteractiveVis.js Engine\nCluster IsolationLive Search\nZero ExploitsStandard APIs\nLaunch interactive network graph →\nRegulatory & Legal Context (GDPR Article 25 & Consumer Protection):\nUnder the principle of Data Protection by Design and by Default, a platform architecture that permits silent API-key generation, unnotified trade cancellation, and machine-automated asset liquidation is an architectural choice of the platform operator. When Valve systematically rejects consumer reimbursement claims by asserting that losses were caused by \"external cyberattacks,\" it conceals that the attack vector is Valve's own intentionally designed Web API architecture.\n\nINTERACTIVE VIEW\n\nFull interactive visualisation of the 252-repository, 3,320-developer network graph is available at network.html. Aggregate metrics are on the BI Metrics page.\n\nThe Steam Dossier · Technical Architecture Archive · Public Source Records · All rights surrendered to humanity.",
    "headings": [
      {
        "level": 1,
        "id": null,
        "text": "Steam Network Architecture — Protocol Fidelity & Ecosystem Analysis"
      },
      {
        "level": 3,
        "id": null,
        "text": "Official Protobuf Schemas"
      },
      {
        "level": 3,
        "id": null,
        "text": "Programmatic Trade Authorization"
      },
      {
        "level": 3,
        "id": null,
        "text": "Monetized Machine Traffic: Up to 66.7% Fee Floor"
      },
      {
        "level": 2,
        "id": null,
        "text": "Public Developer & Repository Infrastructure"
      },
      {
        "level": 2,
        "id": null,
        "text": "Global Engineering Ecosystem Metrics"
      },
      {
        "level": 2,
        "id": null,
        "text": "Interactive Protocol & Developer Network Graph"
      }
    ],
    "links": [
      "https://phishdestroy.io/steam_dossier/de/output_steam_network/index.html",
      "https://phishdestroy.io/steam_dossier/de/#briefing-heading",
      "https://phishdestroy.io/steam_dossier/de/output_steam_network/valve_ru_farming_isolated.html",
      "https://phishdestroy.io/steam_dossier/de/output_steam_network/steam_ecosystem_dashboard.html",
      "https://phishdestroy.io/steam_dossier/de/output_steam_network/network.html"
    ]
  }
}