Complex Private Corporation Template

What It Is

CORP-COMPLEX-PRIVATE is the advanced dCorps company setup for multi-class private governance. It creates the public company profile, the core wallet set, board and committee roles, and approval rules for protected matters. Treasury tiers, class actions, and intercompany flows stay visible on-chain through tagged money movements and anchored approvals.

Template Code

Template code: CORP-COMPLEX-PRIVATE. This label keeps the template consistent across apps, links, and public views.

Committee Governance

Board and committee layers define approvals for protected matters, class actions, and treasury tiers.

Multi-Class Units

Multiple unit classes capture distinct rights, with approvals for issuances, conversions, and transfers.

Standard Wallet Types

Standard wallet types separate revenue, operating spend, reserves, and labeled treasury buckets.

Tagged Flows

Payments and capital flows carry tags that show purpose, approval tier, and class context.

Template Position

CORP-COMPLEX-PRIVATE sits at the top of the corporation template stack for private companies. It is for multi-class governance, committee approvals, and group structures that demand strict control. Simplify to CORP-VENTURE or CORP-PRIVATE-STD when committee layers or class complexity are no longer part of the model.

Venture Template

Use CORP-VENTURE for board governance and financings without committee layers or group structures.

Standard Private

Use CORP-PRIVATE-STD for multi-owner approvals without boards, committees, or multi-class equity structures.

Solo Template

Use CORP-SOLO when ownership consolidates to one controller and governance is minimal.

Best Fit

CORP-COMPLEX-PRIVATE fits mature private companies with multi-class equity, committees, and layered treasury policies. It suits holding groups, firms with audit or compensation committees, and teams managing complex capital actions. Day-to-day operations still move quickly, while protected matters follow strict approval tiers.

Multi-Class Equity

Multiple unit classes and conversions are supported with class-specific approvals and thresholds.

Committee Layers

Audit, finance, or compensation committees can approve scoped actions under delegated authority.

Group Structures

Built for parent and subsidiary setups with clear ownership chains and intercompany flows.

Advanced Controls

Treasury tiers, transfer rules, and evidence thresholds enforce stronger governance control overall.

Not a Fit

This template is not for early-stage teams or companies without committee governance. It is also not ideal when a single board layer is enough or when multi-class equity is not used. If you only require board approvals without committees, CORP-VENTURE is a better fit. Donation-led organizations should use nonprofit templates designed for fundraising and allocation.

Early Stage

Use CORP-SOLO or CORP-PRIVATE-STD for simpler ownership and approval setups in small teams.

Venture Grade

Standard venture governance without committees aligns with CORP-VENTURE for board-led approval cycles.

Nonprofit Model

Nonprofits follow donation and allocation workflows and align with nonprofit templates built for fundraising.

Ownership and Units

Keep percentages clear across classes and conversions by using base units. The template supports multiple unit classes, class-specific voting, and transfer rules tied to governance approvals. Entities can hold units in other entities so group ownership stays visible across the structure.

Base Units

Default 10,000 base units keep ownership splits clear and allow precision expansions later.

Class Rights

Classes define distinct voting and economic rights, with approvals for issuances and conversions.

Entity Holdings

Parent or subsidiary entities can hold units, so group ownership links are visible on-chain.

Authority and Governance

Combine board authority with committees and class approvals. Protected matters such as financings, conversions, and policy changes require the right approvals based on class and committee scope. Role changes and approvals stay visible on-chain so authority remains clear to the team and counterparties.

Board Authority

Board seats and quorum thresholds define who approves protected matters and capital actions.

Committee Scopes

Committees approve finance, audit, or compensation actions within their delegated scope limits.

Class Approvals

Class-specific votes can be required for actions that change class rights or ownership.

Protected Matters

Financings, conversions, and policy changes remain gated behind layered approvals for consistency.

Employee Role Wallets

Delegate work while keeping approvals with designated approvers by using role wallets. Operators can prepare invoices, tag payments, or stage payouts, and approvers sign before funds move. This keeps work moving while accountability stays shared.

Role Types

Role wallets can be set for operators, accountants, approvers, or payout executors across the team.

Scoped Permissions

Permissions can allow invoicing, tagging, or payout prep while blocking execution until required approvals sign.

Payee Separation

Payee wallets receive funds, while role wallets handle authority unless the company binds both together.

Delegation and Approval Limits

Set approval limits to define what can run automatically and what must be co-signed. Treasury tiers route payments to routine, protected, or extraordinary approvals, while unit actions follow class-specific thresholds. Limits can vary by wallet or category so each team follows clear guardrails.

Role Scope

Each role includes a clear scope that lists which actions it can prepare, approve, or execute.

Treasury Tiers

Routine, protected, and extraordinary tiers route approvals by amount or category limits.

Class Controls

Unit actions and conversions can require class or committee approvals before execution.

Wallet Structure

Separate money by purpose so activity is easy to follow. One wallet receives customer payments, another handles operating spend, and reserve wallets can hold long-term funds. Authority wallets sign approvals, while payment wallets receive and send funds. This keeps control separate from cash so activity stays easy to verify.

Merchant Wallet

Wallet type MERCHANT is the public payment wallet where customer revenue lands.

Operating Treasury

Wallet type OPERATING_TREASURY handles routine business spending and outgoing payments for vendors and contractors.

Reserve Wallets

Wallet type RESERVES can be labeled to track strategic buckets or restricted reserves.

Authority Separation

Authority wallets include board and committee signers, while payment wallets receive and send funds.

Operating Assets

Show operating totals in USDC so values stay stable and easy to compare. Treasury wallets can also hold DCHUB for gas or long-term exposure if you decide to keep it. Those holdings are tagged so summaries stay clear and do not mix with operating cash.

USDC Totals

All v0.1 totals use USDC so views stay stable across time and tools.

Treasury Holdings

Treasury and reserve wallets may hold DCHUB alongside stablecoins when you want network exposure.

Tagged Assets

DCHUB balances should carry asset_tag and BAL_DCHUB so explorers separate them from operating cash.

Gas Payments

Transaction fees are paid in DCHUB by the signing wallet each time it submits a transaction.

Commerce and Payment Modes

CORP-COMPLEX-PRIVATE supports both direct payments and invoices, so customers can pay in the way that fits them. Recurring plans cover subscription billing with scheduled payments that run on-chain. Every invoice carries a status so the team can see what is open, paid, or canceled at a glance.

Direct Payments

Customers can pay directly to the merchant wallet when the amount is known in advance.

Invoice Requests

Invoices are on-chain payment requests tied to the entity, with amount, due date, and payer reference.

Recurring Plans

Recurring plans schedule repeat billing so subscriptions or retainers can run without manual re-entry.

Status Updates

Each invoice status updates as it moves from open to paid or canceled, so follow-up is clear.

Catalog Items

Define what you sell once so invoices and payments stay organized as the business grows. Each item has a name, price, and ID that can be reused across invoices and tags. This creates a consistent view of sales without retyping details every time.

Item Reference

Create an item_id with a clear label and price so each product or service is easy to reuse.

Cost Baseline

Add an optional cost baseline so margins can be estimated later without retroactive guesswork.

Invoice Linking

Use item_id on invoices and tags to connect sales activity to totals and views.

Payroll and Contractor Flows

Tag payroll and contractor payouts so compensation is visible without mixing it with authority roles. Payee wallets receive funds, while approval roles control when payments go out. Apps can schedule or batch payouts to match payroll cycles.

Payee Wallets

Payee wallets receive salary or contractor payments directly, separate from any authority roles.

Tagged Payouts

Payouts carry payroll or contractor tags so compensation is easy to identify in summaries.

Optional Schedules

Apps or SDKs can schedule or batch payouts when you want recurring or grouped payments.

Tagging and Evidence

Tags are simple labels added to each payment so activity stays understandable over time. For protected matters and treasury tiers, you can attach proof by anchoring a secure reference to approvals, policies, or agreements. This creates a clear trail without publishing private files.

Core Required

These tags are required on every flow so views stay consistent. Pair reference_type with reference_id.

category_code counterparty_type reference_id reference_type

Operating Context

Optional tags split activity by team, product, project, or channel for clearer tracking.

business_unit_tag department_tag cost_center_tag project_tag product_tag item_id channel_tag region_tag counterparty_tag

Capital Context

Use these tags for rounds, securities, classes, pools, and debt-based financing actions.

round_tag security_type_tag equity_class_tag vesting_schedule_tag option_pool_tag debt_instrument_tag loan_id

Treasury Context

Use these tags to label wallet buckets, custody context, and asset tracking on flows.

wallet_tag treasury_bucket_tag asset_tag custody_tag

Evidence Anchors

Anchors link to policies, approvals, or agreements without publishing the document itself.

Materiality Threshold

Set a materiality threshold so larger items require evidence, with 1,000 USDC as the default.

Counterparty Directory and Privacy

Repeat clients or vendors can be labeled with private nicknames instead of real names. The real-world mapping stays off-chain under your control, which protects sensitive data. Public views show only the tag and wallet, not the underlying identity. You still get a consistent history of who pays and who gets paid without exposing identities.

Pseudonymous IDs

Use counterparty_tag to label repeat clients or vendors without exposing their legal names on-chain.

Off Chain Mapping

Keep the real-name mapping off chain so only your team can see it.

Repeat Counterparties

Track repeat counterparties across invoices and payments without publishing personal or business details.

Operating Flow

Move from setup to live activity with layered governance in place. Setup binds board and committee wallets, defines class rules and transfer policies, and sets treasury tiers. You register the entity, connect wallets, run payments, and tag what happens so views stay consistent. Each step writes to the on-chain history, keeping operations clear for the team and anyone checking.

Register and Bind Governance

Define Classes and Policies

Set class rights, transfer rules, and approval thresholds for protected capital actions.

Set Wallets and Tiers

Connect the standard wallets, label treasury buckets, and set approval tiers for spending.

Collect Revenue

Issue invoices or accept direct payments so revenue lands in the merchant wallet.

Tag and Anchor Evidence

Tag money in and out, and anchor approvals for policies, financings, or material items.

Review and Close

Review live views, then close a period if you want a fixed snapshot for later comparison.

Live On-Chain Views

Explorers show live summaries from tagged transactions without waiting for manual exports. You can see balances, recent activity, and tag coverage as it happens. Others can check the same numbers you see, which keeps public visibility in sync.

Wallet Balances

Wallet balances update as transactions confirm on-chain, so the numbers stay current.

Time Window Views

Time window views summarize activity over a period without waiting for a manual close.

Coverage Ratios

Coverage ratios show which flows are fully tagged and which still require context.

Data Exports

Exports are optional for offline analysis or backups when you want files outside the chain.

Registry, Logs, and Proof

Use the registry and governance log to verify identity, status, official wallets, approvals, class votes, and role changes. Each approval entry shows who signed and when, creating a clear decision trail. Anchors timestamp policies and agreements when proof is required, so the history stays durable and verifiable.

Registry Entry

The registry lists identity, status, and official wallet bindings so anyone can verify the current setup.

Governance Log

The governance log shows approvals, co-signs, and role changes in time order for clear accountability.

Anchored Proof

Anchors timestamp receipts and contracts so their existence can be verified later without publishing the files.

Lifecycle and Status

Signals show whether a company is active, paused, or closed, so people know if payments should go through. Apps can show the status automatically as a simple safety cue. This reduces confusion and prevents money from going to inactive entities.

Status States

Status labels show whether the entity is active and safe to pay, using a consistent color set.

draft active suspended dissolved

Payment Endpoints

Payment endpoints resolve from the entity ID and wallet type, so users do not copy raw addresses.

Interface Warnings

Interfaces can warn when an entity is suspended or dissolved so payers avoid sending funds.

Upgrade Paths

As the company simplifies, it can move to a different template without losing continuity. Simplification can step down to venture-grade or standard private structures when committees, class complexity, or group holdings are no longer required. The same entity history remains intact across transitions.

Venture Template

Template code CORP-VENTURE fits when board governance remains but committees are removed.

Standard Private

Template code CORP-PRIVATE-STD fits when board governance is no longer part of the model.

Solo Template

Template code CORP-SOLO fits when ownership consolidates to one controller without board layers.

Where to Operate and Verify

The official app handles day-to-day actions like registration, invoicing, and approvals. Public tools (registry, explorer, and official indexer) let anyone verify identity, status, and wallet bindings. This keeps what you do and what others see in sync across the network.

Official App

The official app is where you register, issue invoices, tag payments, and approve actions.

The Registry

The registry confirms identity, status, and official wallets so counterparties can verify who they are paying.

The Explorer

The explorer, powered by the official indexer, shows transactions, balances, and public history in one view.

Official Indexer

Reference data service that powers explorer summaries and reporting views for consistent public visibility.

dApps & SDKs

Third-party dApps and SDKs let you build custom flows or integrate payments into your own products.

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.