Overview

What It Is

dCorps is a dedicated Hub chain built as an Arbitrum Orbit rollup (Rollup mode) that records canonical entity state for corporations and nonprofits and settles to Ethereum. It standardizes identity, authority roles, governance actions, wallet types, tagged treasury flows, and evidence anchors so any interface can read an entity with the same rules. Payments are stablecoin-native (USDC) and remain in entity-controlled wallets.

Why It Exists

dCorps exists to make organization identity, authority, and wallet bindings verifiable without relying on a single platform. It provides a shared standard for roles, approvals, and treasury events so different observers can independently read the same entity history. This reduces ambiguity about who can act and where funds should go.

What It Records

dCorps records the minimum shared facts an organization needs to be verified. It captures who the entity is, who can act, what decisions were approved, which wallets are official, and how funds and evidence are tracked over time. This keeps public views consistent across apps and explorers.

• Records identity

  It defines a public entity profile with type and status so anyone can verify who it is.

  This answers: Who is this entity?

• Records authority (roles and permissions)

  It binds roles to wallets so people can see who can propose actions, approve changes, or sign payments.

  This answers: Who is allowed to act?

• Records governance decisions

  It records proposals, approvals, and votes in time order so decisions stay auditable.

  This answers: What was decided, and when?

• Records treasury activity

  It records tagged inflows, outflows, and transfers from official wallets so money movements stay interpretable.

  This answers: What happened to the money, and why?

• Records document proof (anchors)

  It anchors a document hash so later reviewers can confirm a document matches, without publishing the file on-chain.

  This answers: Can we prove this document existed and was not changed?

Who It Serves

Different groups rely on different layers (kernel record, templates, reporting, adapters, or apps). The common requirement is a shared record that is easy to verify.

What It Is Not

dCorps is not a bank, broker, exchange, or custodian. It does not provide legal recognition or regulatory compliance, and it makes no guarantees about external legal outcomes.

dCorps is not:

How It Works

The Hub stores a single canonical record for each entity. It includes identity, authority roles, governance actions, official wallets, tagged treasury events, and evidence anchors. The record is time-ordered on-chain, so changes leave a visible trail while interfaces remain downstream.

The Hub core includes:

Key properties:

Entities and Templates

Organizations register on the Hub as entities (corporations and nonprofits). Templates are default role, approval, and wallet setups built on the same kernel record. Start with the closest fit and move as ownership or approvals change, without rewriting history or implying legal status.

Entities

Templates

Templates define default roles, approval thresholds, and wallet structure.

What all templates share

Modules and Adapters

Add optional workflows or context on top of the kernel through modules and adapters. They can express jurisdiction, sector, disclosure, or assurance rules without changing core authority. If an extension is not present, the kernel still provides the full operating foundation.

Modules and adapters may include:

Key boundary:

Treasury, Accounting, and Outputs

Stablecoin events from official wallets are recorded with tags to form treasury history. Funds remain in entity-controlled wallets (non-custodial), while evidence anchors link material actions to documents. Reports are derived from the same on-chain record, so different observers can compute matching totals.

Treasury and operating assets

Accounting building blocks

Event sources

Reporting outputs

Reports are derived from the tagged event record, so two people can independently compute the same totals.

Privacy, Disclosure, and Lifecycle

dCorps records a disclosure mode so interfaces can show what is public versus aggregated. It also records lifecycle status so anyone can see whether an entity is draft, active, suspended, or dissolved. This reduces confusion and helps prevent payments to inactive entities.

Registration status

DCHUB Token

Network utility comes from DCHUB: it pays gas, is used for protocol governance, and can be required for protocol-level fees such as entity registration, renewals, and module registry actions. Entities may hold it in treasury, but it is optional.

Entities may also hold DCHUB in treasury for gas and protocol fees, but it is optional.

Protocol Governance

On-chain governance changes parameters and upgrades through proposals, voting, and execution. Proposals are submitted, voted on, and executed in time order, creating a visible change trail.

Governance steps:

Interfaces and Apps

Tools render views and submit actions, but the on-chain record remains the source of truth.