EVENTUM / DOCUMENTATION

Protocol notes.

A short field guide to snapshots, relationships, and the contract boundary. The repository contains the complete implementation and release evidence.

Overview

Eventum is the semantic interoperability layer for prediction markets. It asks whether two independently authored markets would resolve identically under all materially relevant interpretations of their published rules.

It is not an odds feed, a market resolver, or an LLM similarity score. The protocol asset is the immutable snapshot, the consensus-backed relationship, and the direct evidence graph.

Protocol

Snapshot before judgment

A snapshot includes the provider market ID, canonical URL, title, description, outcome labels, resolution rules, authority, time fields, clarifications, retrieval timestamp, source hash, and normalized semantic facts. A changed source is a new version.

Relationships

The contract accepts eleven bounded relations: EQUIVALENT, CONDITIONAL_EQUIVALENT, SUBSET, SUPERSET, OVERLAPPING, CONFLICTING, TEMPORAL_MISMATCH, SOURCE_MISMATCH, OUTCOME_MISMATCH, UNRELATED, and AMBIGUOUS.

{
  relation: "TEMPORAL_MISMATCH",
  safe_to_compare: false,
  safe_to_aggregate: false,
  outcome_mapping: {},
  reason_codes: ["TIME_WINDOW_CONFLICT"],
  material_differences: ["…"],
  evidence_hashes: ["…", "…"]
}

Consensus

Market text is untrusted data. The Intelligent Contract puts it inside explicit evidence delimiters, asks for strict JSON, validates every field, and independently re-runs the semantic task in the validator function. If the result is malformed or unclear, the result is AMBIGUOUS or the transaction does not finalize.

Rationale explains a decision; it is not the consensus key. There is no protocol confidence percentage.

Integration

The first verified adapter is the public Polymarket Gamma API. The application accepts public /market/<slug> and single-market /event/<slug> URLs. Unsupported providers return a visible error rather than silently scraping.

Use Compare for the product flow, Graph for direct edges, and Status for configured deployment evidence.

Limitations

  • The first adapter does not assert canonical cross-market event hints, so a Polymarket preview may not authorize safe aggregation.
  • Studionet writes require a funded EIP-1193 wallet and can remain pending while GenLayer consensus progresses.
  • Only direct comparison edges are displayed. The graph deliberately does not infer A = C from A = B and B = C.
  • This internal review is not a third-party security audit.