Foundry flow: fuel -> primitives -> chip -> PoD

FabOut Protocol: meme fuel becomes mining Chip NFTs.

$FABO mints NAND, CLOCK, CORE and SILICON. The canvas turns them into a netlist. Tape-out burns the primitives into a Chip NFT, and PoD scores that design as mining hardware.

Fuel $FABO starts the foundry
Chip tape-out mints the NFT
PoD design weight mines rewards
foundry://fabout/tapeout-flow
01 Fuel $FABO mint budget
02 Primitive NAND / CLK raw components
03 Tape out Chip NFT burned netlist
04 PoD Mine design weight
primitive cost36 NAND
asset outputChip NFT
PoD weight12.8x
flow: $FABO -> PRIMITIVES -> CHIP NFT -> PoD status: pre-launch / contracts not live

The primitive layer

Everything starts as a mintable chip primitive.

$FABO is the foundry fuel. Each processor can expose its own primitive supply, price and mint window before designs begin to consume it.

0x00 / LOGIC

NAND

The base gate. It turns design from a meme into something that can be wired, counted and burned.

0x01 / TIME

CLOCK

The tick source. A chip without time cannot run a mining route, epoch or stateful proof.

0x02 / REF

CORE

A finished circuit dropped back into the canvas as a black box, ready to be reused by strangers.

0x03 / BASE

SILICON

The substrate. It limits high-grade tape-outs and makes scarce chips feel manufactured, not printed.

Canvas

Drag parts, wire pins, simulate locally, then tape out on chain.

The browser is a free workbench. The chain only sees the final netlist, validates it, burns the consumed primitives and mints the permanent Chip NFT.

Live wiring before gas.

A user can experiment with NAND, CLOCK, CORE references and SILICON limits before committing anything. The visible wire is the interface. The on-chain output is a compact netlist.

TAPE OUT creates the asset.

When a design is sealed, components stop being inventory and become silicon. The resulting Chip NFT can be held, listed, composed as a CORE, or routed into PoD.

Processor factory

Anyone can launch a processor with its own primitive market.

A processor is the foundry account: name, symbol, primitive supply, mint price, creator revenue and future circuit namespace.

Processor accountpending
NAND / CLOCK / CORE / SILICON mints4 supplies
Creator earningswithdrawable
Parameter statuspermanent after seal
Mint window Genesis primitives open in

Every cycle gives the foundry a fresh launch window for NAND, CLOCK, CORE and SILICON.

00days
00hours
00minutes
00seconds
PRE-MINT

Market and data

Primitives trade before fabrication. Chips trade after tape-out.

FabOut separates raw manufacturing inventory from finished designs. The market gives demand to primitives; the data layer makes the foundry legible.

OPEN BIDS 128

NAND, CLOCK, CORE and SILICON orders waiting for sellers.

CHIP LISTINGS 37

Finished Chip NFTs listed as reusable compute modules.

FOUNDRY FEES 1%

Protocol fee route for market fills and future PoD settlement.

Proof of Design mining

Mining becomes a demand sink for better chips.

PoD rewards the design route, not raw electricity. Better compositions receive higher design weight, while weaker chips can still participate as early hardware.

The miner is a Chip NFT.

A tape-out can enter mining once it exposes a valid proof route. Weight can depend on primitive cost, silicon scarcity, reusable CORE depth, clock stability and epoch difficulty.

This creates the loop: users mint components, burn them into chips, route chips into PoD, then use mining demand to price the next primitive cycle.

epoch00042active
chipFO-0112.8x
routeSHA gatevalid
difficulty0x0000ffsettling
reward$FABOpending

Protocol notes

A chip should be callable, composable and hard to rewrite.

These notes are the public shape of the FabOut concept before contracts ship.

Netlist

Each element appends its output to the signal stream. CORE references let finished chips return as black boxes.

Evaluation

The browser and the contract must settle the same signals, so what users test is what the chain accepts.

The seal

Parameters freeze first. Logic freezes after audit. Until then, the protocol should be treated as mutable.