PROTOCOL 4096
GENESIS NETWORK / ONLINE / 4,096 NODES

4,096
entities.

one system. unknown purpose.

An on-chain entity network from a single unexplained machine civilization. Acquisition is only the entry point. The protocol is what happens after.

READ THE SPECIFICATION
NETWORK ROBINHOOD CHAIN POPULATION 4,096 PROTOCOL ONLINE
GENESIS SPECIMEN NO. 0001
Protocol 4096 Entity 0001
X 032.14
Y 018.02
GRID / 64
STRUCTURE / OBELISK STATE / SEALED
STRUCTURE 24 · CORE 16 · INTERFACE 18 · MATERIAL 15 · STATE 15 · ANOMALY 205 · FUSION PAIRS 30

The collection is
only the surface.

Every entity is a sentence, not a bag of traits. Structure proposes a function. Core confirms or complicates it. Interface describes what the entity expects. Material records its era. State tells you what is happening now.

The visible NFT is only one layer. Deeper protocol classifications determine relationships, output and state transitions. Visual rarity and protocol relevance are deliberately decoupled.

01 SCAN read the machine
02 MATCH find compatibility
03 CONNECT activate the relation
04 OUTPUT generate protocol credits
GENESIS NETWORK ● ONLINE
ENTITIES 4,096
CHAIN ROBINHOOD
SCAN ENGINE READY
MATCH ENGINE READY
CREDIT ENGINE READY
FUSION ENGINE LOCKED
ACQUIRE / EXTERNAL
OPERATE / PROTOCOL 4096
THE OPERATING SURFACE

Acquire elsewhere.
operate here.

Acquisition happens on the marketplace. The Protocol website is where an owned entity becomes readable, relationships become discoverable, Credits begin to print, routes are selected and fusion becomes possible.

Inspect the
population.

4,096 records. Public traits below. Deeper classifications become relevant when the protocol scans an entity.

CONNECTED WALLET NOT CONNECTED
OWNED 0
CONNECT WALLET TO READ OWNED ENTITIES
ENTITY 0124
Protocol 4096 entity
SPECIMEN / 256 × 256 / NEAREST
ENTITY #0124 CONTAINED
PROTOCOL CLASS REDACTED Protocol relevance and compatibility identifiers are not public traits.
AWAITING SCAN

The collection
is a system.

Compatibility is not visual similarity. The network is formed by protocol relationships: sockets, core identities, state gates and consent.

NETWORK TELEMETRY
6 / 4,096 NODES VISUALIZED
AUTHored FUSION LINKS / 03
EXACT MATCH #0124 ↔ #2786 RECT-SLOT / GEOMETRIC CORE
EXACT MATCH #0256 ↔ #3071 HEX / LIQUID CORE
EXACT MATCH #0358 ↔ #2381 CIRCULAR-SMALL / ROTATING CORE

Credits are
output.

Connected protocol states generate Credits. The router assigns the output to a stock-linked reward market.

PROTOCOL CREDITS 0.00 +1.00 / HOUR
REWARD ROUTER ROUTE / NVDA
Active protocol entity
ACTIVE ROUTE NVDA STOCK-LINKED OUTPUT
AVAILABLE CREDITS 0.00
OUTPUT CLASS STOCK-LINKED
CONNECTION UNRESOLVED

Route activation requires at least one owned P4096 entity.

Change the
machine.

Connection preserves both entities. Fusion consumes the relationship and creates a Composite Entity. The production fusion action requires a permanent 100,000 $P4096 burn.

FUSION FUEL 100,000 $P4096 / REQUIRED
Fusion entity A #0124
+
Fusion entity B #2786
COMPATIBILITY 100% RECT-SLOT / GEOMETRIC CORE
FUSION READY / DEMO TERMINAL
OUTPUT CLASS COMPOSITE STATE TRANSFORMED TRAIT SOURCE A + B

Read the
machine.

The full specification explains the entity grammar, compatibility constraints, Absent Core system, matching logic, reward engine, stock-linked routing, $P4096 fusion fuel, anomalies, state transitions and worked examples from the actual collection.

OPEN FULL DOCUMENTATION
DOCUMENT / P4096-SPEC TECHNICAL SPECIFICATION WORKED ENTITY PAIRS COMPATIBILITY GRAPHS REWARD ROUTER STATE MACHINES FUSION MODEL