High-level protocol responsibilities

Protocol Architecture

A product-level map from Machine ownership and $WORKS through epochs, tokenized stocks, and distribution.

The protocol at a glance

System map

Engine Works connects Machine ownership, $WORKS, weight, eight-hour epochs, tokenized-stock purchases, and distribution.

FIG / 07HIGH-LEVEL PROTOCOL ARCHITECTURE

PROTOCOL FLOW

MACHINE$WORKSWEIGHT8H EPOCHSTOCK POTTOKENIZED STOCKSDISTRIBUTION

A Machine uses $WORKS to build weight. Epochs turn fees into tokenized-stock output and distribute it by weight.

The participation unit

Machine ownership

Machine: The owned unit that participates in Engine Works.
Owner: The wallet that owns and controls the Machine.
Transfer: Ownership and Machine state move together when a Machine changes hands.

Power becomes participation

$WORKS and weight

$WORKS pays for Machines and powers Machine actions. Burning $WORKS through those actions activates a Machine or builds its weight. Weight expresses the Machine’s proportional share of an epoch distribution.

Fees become output

Epochs and tokenized stocks

Engine Works runs in repeating eight-hour epochs. Protocol fees build the Stock Pot, which funds purchases of configured tokenized stocks. Those purchased stocks become the epoch’s stock output.

Output follows weight

Distribution

When an epoch settles, tokenized stocks and the distributable $WORKS output are divided across active Machines. Each Machine receives the share represented by its weight relative to total active weight.

Official sources only

Deployment information

Engine Works is built for Robinhood Chain.