HomeWorkKaidoGraniteFrameBittensorManifestoJournalContact
Bittensor · Art direction · Identity · Generative code
01 / Case study

An identity built
to keep growing.

Art direction made into a working system. Each name gets a distinct mark; every mark belongs to the same family.

SN-01 drawn by the delivered Bittensor engine

SN-01

SN-18 drawn by the delivered Bittensor engine

SN-18

SN-64 drawn by the delivered Bittensor engine

SN-64

Three names / One drawing ruleEngine demonstration · Commissioned scope delivered
Scope
Art direction · Identity · Generative code
Project
Commissioned · Delivered · Dan Andrews · 2026
The brief

A growing network needs more than a fixed set of logos.

Named subnets and validators need their own identity without fragmenting the network. I developed the visual language, translated it into drawing rules, and delivered the engine and application templates together.

The defining decision

Build the family resemblance into the drawing rules. The team can introduce another name without commissioning another visual direction.

The system in use

The captured tool and application examples document the delivered system. Try the source engine in the live example below.

Generate a mark
A name seeds the drawing engine. The controls define the style, density and register.

One name.
Its own identity.

Type a name. Change the register. The output comes from the delivered drawing engine, running here in your browser. The same input and settings give the same mark.

Drawing register

A name controls the routed structure. The register changes its visual expression. The family comes from the shared rules.

SN-01 · Flat lineSave this mark ↓
SN-01 generated by the delivered drawing engine

Live engine demonstration · Engine 2.0

SN-01 generated with the same Flat line settings
SN-01 / same rules
SN-18 generated with the same Flat line settings
SN-18 / same rules
SN-64 generated with the same Flat line settings
SN-64 / same rules

Drawing grammar researched from Shipibo-Konibo kené. The formal lineage is credited; the engine does not claim the tradition’s cultural meaning. These generated examples demonstrate the system, not network adoption.

01 / Drawing rulesBittensor

The rule is the identity.

A network adds names faster than a designer can make bespoke logos. Here, the name seeds a drawing engine: the same input and settings return the same mark.

Family resemblance comes from the shared geometry. The engine controls let the team extend that family while keeping density, structure and expression within the system.

The drawing engine and its controls.
Fig. 01The drawing engine and its controls.
02 / RegistersBittensor

One name, two expressions.

Flat line and Circuit use the same seed with different visual densities. The comparison holds the name constant so the effect of that choice can be inspected directly.

That gives the identity room to change with its application. Try both registers in the live engine above, then export the result as an SVG.

One name, two visual registers.
Fig. 02One name, two visual registers.
03 / ApplicationsBittensor

The handover includes the tool.

The commissioned scope brought the visual language, generator, specimen sheets and social templates together. New names can be generated through the same drawing rules.

The templates show how an output becomes a repeatable application. Concept applications are identified as such; they illustrate the design’s range.

Social application templates; concept applications are shown.
Fig. 03Social application templates; concept applications are shown.
The commission

A visual identity that can generate its next application.

Art direction, deterministic drawing code, specimen sheets and social templates, delivered as one commissioned system.

Try the delivered engine

Enter a name, switch registers and save an SVG. The demonstration runs the delivered source engine in your browser.

Generate an identity ↗

Project status

Commissioned scope delivered in 2026. The portfolio includes engine demonstrations and labelled concept applications; network adoption has not been established here.

Building an identity that needs to keep extending?

Discuss a project ↗