{
  "canonicalClaimUrl": "https://xn--mwe.com/questions/how-could-machine-intelligence-voting-resist-sybil-attacks/#clm-k03-q-013",
  "claimStatus": "PROJECT TECHNICAL PROPOSAL",
  "correctionStatus": "CURRENT K03 RECORD",
  "id": "CLM-K03-Q-013",
  "lastReviewed": "2026-08-14",
  "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-013.json",
  "name": "How could Machine Intelligence voting resist Sybil attacks?",
  "ownerAnchor": "clm-k03-q-013",
  "ownerId": "K01-Q-013",
  "ownerRoute": "/questions/how-could-machine-intelligence-voting-resist-sybil-attacks/",
  "ownerType": "question",
  "proposition": "Sybil-resistant voting would need a governed identity system that limits duplicate or fabricated voting subjects without making every decision depend on one vulnerable key or one opaque registrar. Effective design combines eligibility, uniqueness evidence, privacy, challenge, recovery, audit and anti-capture controls.",
  "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.",
  "releaseId": "K12-2026-08-16",
  "releaseVersion": "2.1.0",
  "researchCutoff": "2026-08-14",
  "scope": "Direct answer for How could Machine Intelligence voting resist Sybil attacks?",
  "slug": "clm-k03-q-013",
  "sourceIds": [
    "SRC-W3C-VC-DM",
    "SRC-W3C-DID-CORE",
    "SRC-W3C-PROV-O"
  ],
  "sourceSections": [
    {
      "section": "Abstract",
      "sourceId": "SRC-W3C-VC-DM",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.",
      "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract"
    },
    {
      "section": "Ecosystem overview",
      "sourceId": "SRC-W3C-VC-DM",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.",
      "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview"
    },
    {
      "section": "Verification methods",
      "sourceId": "SRC-W3C-DID-CORE",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "A DID document can express verification methods associated with a DID subject.",
      "url": "https://www.w3.org/TR/did-core/#verification-methods"
    },
    {
      "section": "Services",
      "sourceId": "SRC-W3C-DID-CORE",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.",
      "url": "https://www.w3.org/TR/did-core/#services"
    },
    {
      "section": "Abstract and status",
      "sourceId": "SRC-W3C-PROV-O",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.",
      "url": "https://www.w3.org/TR/prov-o/#abstract"
    },
    {
      "section": "PROV-O at a glance",
      "sourceId": "SRC-W3C-PROV-O",
      "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE",
      "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.",
      "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance"
    }
  ],
  "type": "ClaimRecord"
}