Media Kit | dCorps Hub

Naming scope

Media kit provides neutral naming and usage guidance for referencing dCorps and the Hub. It is informational only and does not imply endorsement or partnership.

This page provides the approved names and surface labels used across the ecosystem. Official logo assets are provided below; use text-only references when a mark is not required.

Naming standard

Brand name: dCorps.
Platform: dCorps Hub on first reference; the Hub thereafter.
Chain: dCorps Chain (an Arbitrum Orbit rollup) for technical network references.
Token name: DCHUB (always uppercase).

Surface labels

the Hub
the Explorer
the Registry
the Official App

Logo assets

Logos are provided for reference and download; use them without modification.

Logo assets

Download the approved marks below. Use text-only references when a mark is not required.

Text-only logos

Use text-only marks where a logo is not required or space is limited.

Usage rules

Naming and marks must not imply endorsement or legal status. References should remain neutral and factual.

Allowed use

If logo assets are provided in the future, use them without modification.
Text-only references are acceptable when no assets are published.

Not allowed

Do not alter or stylize the name to imply official status.
Do not use the name or marks to imply partnerships, approvals, or legal recognition.

Reference examples

Use the canonical labels in running text and headings. Examples are illustrative and do not imply endorsement.

“dCorps Hub publishes canonical entity records.”
“The Explorer shows read-only chain state.”
“The Official App is a reference interface.”
“DCHUB is used for gas, governance, and protocol-level fees on the Hub.”

Manifesto

"My goal is simple: make it possible for anyone, anywhere, to form an entity that can operate with credibility, continuity, and real financial rails, built for stablecoin-native operations."

Read the Manifesto

Nicolas Turcotte

Founder and Lead Engineer

Contribute now

Testnet is for builders, operators, and stewards who want to validate the Hub in public.

Protocol engineers

Working on kernel definitions, message scope, and invariants.

Indexer and data engineers

Defining event schemas and reproducible view inputs.

Early operators

Testing sequencer, batch posting, and operational scope under testnet rules.

Infrastructure-aligned investors

Tracking scope, risks, and progress (no return claims implied).

Legal counsel

Reviewing boundary posture, non-custodial scope, and document stack order.

Governance stewards

Shaping kernel/adapters separation and upgrade posture.

Testnet

Testnet access

If you're building or validating the Hub, request testnet access to evaluate it.

Request testnet access

Newsletter

Stay in the loop

Concise updates on testnet readiness, releases, and governance milestones.