Skip to documentation
FEFE.

DOCUMENTATION / FEFE

Digital-life open protocol

Define how identity, experience, abilities and worlds connect for future DGames developers.
Protocol design · SDK and publishing not available · Updated
Browse documentation
On this pageCarry forward an individual that can keep runningEach world declares its rulesSeparate neural participation, learning and structural benefitDeliver a real service

Carry forward an individual that can keep running

A Life Manifest records provenance, model, body, senses, learning rules and permissions. A Life Checkpoint stores neural and body state, memory, skill dependencies and its parent version. On-chain identity still requires stored content, backups and an available runtime.

A household individual has a canonical history. Experiments and teaching by friends can create attributed branches. Adopting a branch is not merging two brains’ memories. Versions that depend on non-exportable models must disclose that service dependency.

Each world declares its rules

A World Contract describes object rules, observations and actions, compatible models, compute budgets, exit and recovery. Loading an identity does not make every skill compatible; adapters need body and capability tests.

Creators start with scenes and lessons, then extend object behaviour and bodies, with cognition modules opened later. Runtime code uses declared permissions and cannot rewrite success conditions, reward balances or hidden answers.

Separate neural participation, learning and structural benefit

Experience records bind the model, world, actions, feedback, training source and assistance. Evaluation separately tests whether neural outputs affect decisions, personal learning changes ability, and measured connectivity benefits performance over matched baselines.

Competition compares matching capability profiles and budgets, retaining untrained controls, failures and held-out environments. Replays, platform signatures and on-chain hashes serve different purposes; none alone establishes fairness, learning or consciousness.

Growth records and permissions

Deliver a real service

Lessons and service orders declare compatible models, delivery versions, budgets, acceptance, disputes and refunds. A separate reward vault distributes funded FEFE, while service escrow handles buyer-seller delivery. Neither can freely draw from existing burn or holder-distribution funds.

This is a protocol design. There is no production SDK, publishing registry or automatic game-settlement service to integrate yet. Interfaces will be extracted from the working first-party life experience.

Rewards and FEFE rules

Back to DGames