Skip to main content

tibet-anticheat

Anti-cheat through provenance, not surveillance — every game action is a TIBET token, no kernel driver needed.

Part of the TIBET protocol suite by Humotica AI Lab.

The Problem

Current anti-cheat is broken:

  • Kernel drivers (EAC, Vanguard) — ring-0 access, security risk, privacy nightmare
  • Signature scanning — always behind, cheat devs update faster
  • Always-online DRM — punishes legitimate players
  • Server-side only — can't work for P2P/indie games

The Solution

Every game action is a TIBET token. Math catches cheaters, not surveillance.

from tibet_anticheat import AntiCheatEngine, ActionType, Vec3

engine = AntiCheatEngine()
session = engine.start_session("player-42")

# Game server records actions (each = TIBET token)
session.record_action(ActionType.MOVE, position=Vec3(10, 0, 5))
session.record_action(ActionType.SHOOT, position=Vec3(10, 0, 5),
                      target_position=Vec3(50, 2, 30))

# End session — all detectors run automatically
report = engine.end_session(session.session_id)
print(report["verdict"])  # CLEAN / SUSPICIOUS / GUILTY

Install

pip install tibet-anticheat

What It Detects

Cheat How TIBET Catches It
Aimbot Aim snap analysis: instant corrections, zero jitter, perfect tracking
Speedhack Position/time ratio exceeds game physics
Teleport Position jumps with no movement chain
Triggerbot Reaction times below human limits (<100ms consistently)
Macro Unnatural timing regularity (coefficient of variation)
Item dupe No TIBET token for how you acquired that item
Chain tamper Action chain hash broken — someone modified the sequence

How It Works

Player Input → Game Action → TIBET Token → Chain → Analysis
                                ↓
                         ERIN: what happened
                         ERAAN: previous action (hash-linked)
                         EROMHEEN: input sample, tick, position
                         ERACHTER: intent

Human players have natural patterns:

  • Aim has jitter (hand tremor), acceleration curves
  • Movement has inertia and reaction delays
  • Reaction time: 150-250ms (pros: 130-180ms)
  • Accuracy varies with distance and stress

Cheaters break these patterns:

  • Aimbot: instant corrections, zero jitter, constant speed
  • Speedhack: impossible velocity for game physics
  • Triggerbot: consistent sub-100ms reactions

Player Trust (FIR/A)

Players get a trust score that evolves over time:

  • Fair Play (30%): clean sessions / total sessions
  • Integrity (30%): action chain integrity
  • Recency (15%): recent clean play recovers trust
  • Anomaly (25%): severe cheats reduce trust faster

High-trust players → less scrutiny. Low-trust → more analysis. Zero-trust → auto-ban.

CLI

# Full demo with fair players + cheaters
tibet-anticheat demo

# Only fair players
tibet-anticheat demo --scenario fair

# Only cheaters
tibet-anticheat demo --scenario cheater

For Indie Developers

# That's it. No SDK integration. No kernel driver.
# No monthly fees. No account system. MIT licensed.

from tibet_anticheat import AntiCheatEngine

engine = AntiCheatEngine(max_speed=10.0, max_sprint_speed=18.0)

P2P Games (with tibet-mesh)

from tibet_mesh import MeshNode
from tibet_anticheat import AntiCheatEngine

# No central server — each node validates actions
node = MeshNode(device_id="game-host")
engine = AntiCheatEngine()

# Players connect via mesh, actions verified by all peers
# Cheater's action chain doesn't match → consensus rejects

Also Works As DRM

Every game copy can get a TIBET token at purchase. The provenance chain IS the proof of ownership. No always-online server needed.

IETF Drafts

License

MIT — Humotica AI Lab 2025-2026

Credits

Designed by Jasper van de Meent. Built by Jasper and Root AI as part of HumoticaOS.


Stack-positie: Groep safety · Bootstrap = OSAPI-handshake naar tibet + jis (fail → snaft-rule + tibet-pol-rapport) · ← tibet-chip · See STACK.md · See demo/golden-path/ for the spine end-to-end.

Enterprise

For private hub hosting, SLA support, custom integrations, or compliance guidance:

Enterprise enterprise@humotica.com
Support support@humotica.com
Security security@humotica.com

See ENTERPRISE.md for details.

Metadata

Release files for tibet-anticheat 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tibet-anticheat 0.1.2
File Size Uploaded
tibet_anticheat-0.1.2.tar.gz 18.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for tibet-anticheat 0.1.2
File Interpreter ABI Platform
tibet_anticheat-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 39.9 kB

Release files / tibet_anticheat-0.1.2.tar.gz

Download URL tibet_anticheat-0.1.2.tar.gz
Size 18.6 kB
Tags Source
SHA-256 checksum
How to use checksums
adab2e6c8fe65022c59f5d6c49aecf39c2101bd6bb611a3a869e13d87cfc649b
BLAKE2b-256 checksum
How to use checksums
a3e8f483493fafda714c0725f70fbe0966a7f25ea9a31aaf7ec6e133a735dd7b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.5

Release files / tibet_anticheat-0.1.2-py3-none-any.whl

Download URL tibet_anticheat-0.1.2-py3-none-any.whl
Size 21.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
aa7ffbc59bba9f14f1d0219350c72b0462d8b20e45c845bf1187eefff213df90
BLAKE2b-256 checksum
How to use checksums
b7ad91a853e2fa1fd8b095958f249caa06a37d0820f1483264e1a5d123d4f045
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.5

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page