FAQ

A Machine is the owned Engine Works unit that can be activated, build weight, and participate in epochs.

Mint one through the official Engine Works path, paying in $WORKS, or acquire one through a supported transfer.

Machines sit on a bonding curve: the price depends on how many already exist and rises with the square of that count. The first costs 33,333 $WORKS and the last of the 3,333 costs 250,000. The price for any serial is deterministic and readable before you mint.

Squaring the count keeps the curve flat early and steep late, so early minters pay close to the floor. Machine 1,000 costs about 52,800 $WORKS; Machine 2,500 costs roughly 155,200.

$WORKS pays for Machines and powers Machine actions. Protocol-routed burns activate Machines and contribute to their weight.

The burn is an irreversible input that changes Machine participation. A successful Machine action destroys the supplied tokens and records the related Machine state atomically.

Weight is a Machine’s proportional share of an epoch distribution: Machine weight divided by total active weight.

No. Minting gives you the Machine. Weight comes only from a separate activation or weight burn performed against that Machine ID.

Each Machine keeps its own identity, activation state, weight, and epoch allocation. The connected wallet can inspect all Machines it controls through Garage.

An epoch is one production accounting cycle that connects fees, mint proceeds, the two pots, purchases, settlement, burn, and distribution.

Eight hours.

Two things: tokenized stocks purchased with protocol fees, and $WORKS released from the Works Pot. Both are divided by the same weight share.

Protocol fees enter the Stock Pot. The Stock Pot funds tokenized-stock purchases that become part of the epoch’s distributable output.

The epoch's assets are not divided and not lost. They carry forward and are added to the next epoch that has active weight to divide them.

No. Unclaimed output stays credited to the Machine and remains claimable. It also follows the Machine if ownership changes.

Each asset is claimed independently, so a restricted or frozen token cannot block the claim of any other. A balance that fails to transfer stays credited rather than being lost.

Supply only decreases. There is no post-construction mint path, and two mechanisms remove tokens: owners burning $WORKS to build weight, and the Works Pot burning half of every mint payment at settlement.

No. It is $WORKS that already existed, paid by minters and recirculated to Machine holders. Distribution moves tokens rather than creating them.

Yes. Nothing prevents it, and the protocol treats those tokens like any others. Doing so increases that Machine's share of future epochs.

It tends to, yes. Holders who consistently reinvest distributions build weight faster than those who do not. This is a property of the design, stated here rather than left for you to discover.

Yes. Weight is recorded when the transaction confirms and is not averaged over the epoch, so weight added shortly before a settlement counts fully toward it.

No. Public product surfaces and documentation are readable without a wallet. A wallet identifies ownership and signs authorized onchain actions.

Engine Works is built for Robinhood Chain.

The public interface keeps protocol transaction controls disabled until official Engine Works deployments are published and connected.

Official Engine Works contract addresses will be published here when the protocol is live.