EVENTUM / SEMANTIC MARKET INFRASTRUCTURE

One event. Many markets. One shared meaning.

Eventum determines whether independently authored prediction markets would settle identically under every materially relevant interpretation of their published rules.

01

Snapshot first. Titles are not markets. Eventum preserves outcomes, time windows, authorities, exceptions, and source hashes.

02

Consensus decides. Natural-language rules are adjudicated by GenLayer validators, not a centralized similarity endpoint.

03

Edges stay direct. A = B and B = C does not silently become A = C.

THE PROBLEM

Same wording ≠ same settlement.

Two markets can point at the same headline and still disagree on the clock, threshold, authority, or what happens when the world gets messy.

Read the rules beneath the question.

Market A

Resolves on the announced result.

Market B

Resolves when the change is implemented.

Eventum

Temporal mismatch. No shared settlement identity.

Illustrative rule contrast — not a live market result.

RELATIONSHIP TAXONOMY

Similarity is not a protocol.

The result names what an integrator may safely do with two markets. Every edge carries evidence for its limits.

Settlement identity

Equivalent

Rules settle the same way across materially relevant interpretations.

Needs conditions

Conditional

Compatible under a stated assumption, but not safe as an unconditional identity.

One direction

Subset / superset

One rule implies the other without mutual equivalence.

Partial relation

Overlapping

Some outcomes or world-states intersect; aggregation is unsafe.

Material conflict

Conflict

Rules disagree on a material criterion such as time, threshold, or authority.

No conclusion

Unrelated / ambiguous

Evidence is disconnected or inconclusive. Fail closed.

THE METHOD

Evidence in. Direct edge out.

Eventum is deliberately narrow: preserve the published source, ask a checkable semantic question, and make the result reusable.

01

Resolve

Fetch a supported market through its public provider API and normalize the published rules.

02

Snapshot

Hash an immutable version with outcomes, dates, authority, exceptions, and retrieval provenance.

03

Adjudicate

GenLayer validators independently assess the structured evidence through a strict JSON decision.

04

Reuse

Read the direct relationship, outcome map, reason codes, and material differences onchain.

MARKET EQUIVALENCE GRAPH

Meaning, with edges you can audit.

Snapshots are nodes. Consensus-backed comparisons are direct edges. The graph never turns transitive convenience into settlement truth.

Snapshot APublished rule
Snapshot BDirect edge
Snapshot CSeparate proof
Conceptual model · inferred edges are not displayed as adjudicated.
WHY GENLAYER

Interpretation is the hard part.

Deterministic code can hash evidence and index edges. It cannot, by itself, decide whether “announcement,” “implementation,” and “official result” are the same settlement condition across authored rule sets.

Untrusted by default

Source text is quoted evidence. Prompt injection cannot rewrite the adjudication instructions.

Checkable fields

Validators compare relation, safety, and outcome mapping — not a made-up confidence score.

Persisted result

Consensus-backed direct edges become reusable protocol state, not a transient API answer.

CONTRACT PROOF

Read the source of truth.

Live status below is read from the configured deployment. Empty means unavailable — never a demo substitute.

Proof of record

Eventum stores the relationship decision, evidence hashes, and outcome map on the Intelligent Contract.

Networkstudionet · 61999
ProtocolNot read
Contract0x7809d1…AdD1d6Fc
Read statusUnavailable

Evidence before theater

The product never substitutes a made-up comparison while the contract is unavailable. Configure the tested deployment to enable writes.

Inspect status Contract not yet live
START WITH THE QUESTION

Would these markets resolve identically?

Inspect two public rules before trusting a shared event identity.

Open compare