Hardware

Hardware is the matter layer of the stack. It senses, computes, signs, stores, transmits, verifies, or acts so software can touch the world and move trusted data through a growth loop.

Use this section when the question is what machine, device, node, phone, sensor, GPU, local AI box, or edge setup should exist before the software stack can do useful work.

Choose The Route

If you need to...	Start here	Why
Buy or operate DePIN hardware	DePIN Devices	See the current device catalogue and what each device contributes.
Map agents, instruments, and devices	DePIN Agent And Instrument Loop	Connect physical devices to agents, receipts, and verification.
Understand wallet phones and device UX	Phones	Study phone hardware as a wallet, identity, and interaction surface.
Assemble local AI compute	Local AI Stack	Future guide for Macs, GPUs, storage, runtimes, and eval proof.
Run blockchain or IoT nodes	Node And Sensor Stack	Future guide for validators, light clients, gateways, sensors, and telemetry.

Hardware Positions

Every hardware stack fills positions. The names change. The jobs do not.

Position	Job	Examples
Compute	Run local inference, training, rendering, indexing, or node workloads.	Mac with unified memory, GPU workstation, edge server, mining or render rig.
Sensing	Capture state from the physical world.	Weather stations, cameras, vehicle telematics, occupancy sensors, RTK devices.
Networking	Move data between machines, people, and protocols.	Phones, hotspots, routers, gateways, satellite links.
Storage	Keep data, model weights, receipts, logs, and local corpora.	NAS, SSD arrays, archival storage, on-device secure storage.
Identity	Prove which device, user, wallet, or agent acted.	Secure enclave, hardware wallet, SIM/eSIM, device key, TEE.
Settlement	Turn verified work into value flow.	Blockchain node, signer, wallet phone, oracle, DePIN reward device.
Action	Move or manipulate the world.	Robots, drones, actuators, vehicles, industrial machines.

Stack Flow

HARDWARE captures or computes
    -> SOFTWARE routes and interprets
    -> PROTOCOLS verify and settle
    -> AI learns and decides
    -> SCOREBOARD measures the loop
    -> HARDWARE improves the next pass

The useful question is not "what device is cool?" It is "what data, proof, or action can this hardware pass into the rest of the stack?"

Context

• depends-on Software Tech Stack — Hardware complements the software positions that move, store, and interpret data.
• pairs-with AI Engineering Stack — Local compute only matters when the AI harness, evals, and observability can prove useful work.
• applies-to Economy of Things — Devices become economic actors when they discover, transact, and settle.
• applies-to DePIN Tokens — Token incentives shape which hardware gets deployed.
• proved-by Benchmarks — Hardware claims need latency, cost, reliability, safety, or output proof.
• risk-governed-by Governance — Devices create legal, regulatory, jurisdictional, and data-sovereignty questions.
• pairs-with Intelligent Hyperlinks — Hardware pages should link by typed relationship, not loose association.

Questions

What physical device would make your software stack more truthful?

• Which hardware position is the current bottleneck: compute, sensing, networking, storage, identity, settlement, or action?
• What data must pass from the device into the software stack for growth to flow?
• What proof says the hardware improved the loop instead of adding a toy?