Skip to main content

How Krang Works

Krang operates as a controlled, server-validated system designed to enable skill-based interaction under clearly defined rules.

Rather than relying on client-side logic or trust-based claims, Krang centralizes validation and decision-making on the backend. This ensures consistent behavior across all ecosystem components.

This section provides a high-level overview of how the system functions without going into implementation or game-specific details.

High-Level System Flow​

At a conceptual level, Krang follows this flow:

  1. A user interacts with a Krang-controlled interface
  2. Input events are transmitted to the backend
  3. The backend validates events against predefined rules
  4. Outcomes are determined centrally
  5. Results are applied within the ecosystem

Clients do not independently determine outcomes or rewards.

Role of the Client​

The client (browser or application) functions as an input and presentation layer.

Its responsibilities are limited to:

  • capturing user input
  • rendering visual feedback
  • displaying results provided by the backend

The client is not considered a trusted authority for scoring, reward calculation, or rule enforcement.

Backend Validation​

All relevant interactions within Krang are processed server-side.

Backend validation includes:

  • session state management
  • enforcement of time and score limits
  • verification of allowed actions
  • consistency checks across events

This design reduces manipulation vectors and ensures uniform rule application.

Sessions as a Structural Unit​

Interaction within Krang occurs in sessions.

A session represents a bounded interaction window with:

  • a defined start and end
  • predefined limits
  • scoped event handling

Sessions act as the primary container for validation and outcome determination.
Detailed session mechanics are documented in later sections.

Outcome Determination​

Outcomes within Krang are not generated locally.

Instead:

  • the backend evaluates validated session data
  • eligibility for rewards or progression is assessed
  • results are applied according to system rules

This approach ensures that outcomes are reproducible and auditable.

Token Interaction (Conceptual)​

The $KRANG token may be referenced during outcome processing.

At a conceptual level, the token can be used to:

  • represent in-platform rewards
  • gate access to certain interactions
  • support ecosystem-specific mechanics

Token usage is constrained to predefined contexts and does not alter validation logic.

Separation of Concerns​

Krang enforces a strict separation between:

  • interaction (client)
  • validation (backend)
  • representation (token or metadata)

This separation allows individual components to evolve without compromising system integrity.

Summary​

Krang functions as a centralized validation system layered on top of interactive environments.
Its architecture prioritizes clarity, control, and consistency over implicit trust.

Subsequent sections describe how these principles are applied within specific ecosystem components.