How a machine becomes a drawing

Principles

• Identity first. A machine's peaqID decides what it looks like. Its body, name and rhythm never change, so people learn to recognise it.
• The record is visible. Credit rating, activity and bond change the finish and the motion, so a machine's standing can be read at a glance.
• Read-only and open. The drawing only reads data peaqOS already publishes. No wallet, no keys, no protocol change. All code is MIT-licensed.
• Drawn, not generated. Every body is hand-drawn pixel by pixel in an architectural language: front elevation, 1:16 scale, dimension lines, callouts and a title block.

Data

Records come from the public peaqOS Machine Credit Rating (MCR) API, one call per machine:

• mcr.peaq.xyz/mcr/did:peaq:<id> for machines homed on peaq
• mcr-20.peaq.xyz/mcr/did:peaq:<id> for machines homed on Solana

The fields used are mcr, mcr_score, event_count, bond_status, negative_flag, revenue_trend, home_chain and rating_unavailable. Activated machines can be browsed at app.peaq.xyz/machines.

Mapping

Each field controls one part of the drawing.

peaqOS data	What it changes
peaqID	The seed: picks the body, the name, and the timing of blinking and breathing
Operator	The drafting grid, so a whole fleet is drawn on the same paper
Credit rating	The finish: Drafting Paper until rated, Field for B and BB, Night Shift for BBB and A, Blueprint for AA, Gilded for AAA
Event count	How alive the core is: pulse speed, glow and scanner. No events, no scanner
Bond status	Bonded machines breathe and blink. Unbonded machines are greyed out with their eyes shut
Negative flag	A redline revision stamp: flagged, under review
Trend, home chain	Recorded in the title block

Determinism

The DID is hashed into a 256-bit seed, which drives a small seeded random generator (sfc32). Every choice is made from that seed in a fixed order, so the same DID gives the same machine on every device, every time. Activity and rating only change the finish and the motion, never the body. Animation uses elapsed time only, never randomness.

Bodies

The demo borrows its bodies from GRID_ARCHITECT_SERIES, 100 robots hand-drawn by ARKAIN STUDIO. The production version gets its own body system, drawn only for peaq: modular heads, hulls, drives and tools that combine into thousands of distinct machines, matched to the machine types peaqOS reports.

Every part shares one house style: perfect symmetry, a 1-pixel outline, light from the left, and peaq's palette of white, indigo and cyan. The first two prototypes:

Architecture

• One static page renders every drawing in the browser with Canvas 2D. No framework, no build step.
• One small server function, /api/mcr, reads the record from peaq and returns it to the page. It holds no keys, stores no data, and caches each answer for 5 minutes to spare peaq's API.
• If the live record can't be read, the page falls back to the ID alone, and also accepts a pasted API response.
• Hosted on Vercel, with the source on GitHub.

Known limits

• Machines registered under peaq's earlier DID system (IDs that start with 0x) have no MCR record. They are drawn from their ID alone, on drafting paper. Reading them from the peaq chain is planned.
• The MCR API has no list of all machines, so a full public gallery needs an index built from on-chain registration events.
• The bodies in the demo come from an existing NFT collection and are not the final peaq set.

Roadmap

1. Open library and live data. An npm package that renders any machine on peaq from its DID, peaqOS or earlier, with tests that prove the same input always gives the same image.
2. The peaq body system and an image endpoint. A modular set drawn for peaq machine types, and a public URL per machine that returns its current drawing, ready for apps, posts and Machine NFT metadata.
3. Elevation certificates. A dated, verifiable snapshot of a machine's sheet, recording its identity, rating and history at that moment, so a machine's reputation becomes a portable visual asset.
4. Gallery, fleet sheets and a launch kit. A public gallery of the Machine Economy, one sheet per operator fleet, and an embeddable widget that gives new teams a ready visual identity from their first machine.