Venture Corporation Template

What It Is

CORP-VENTURE is the venture-grade dCorps company setup for teams with board governance and investor rounds. It creates the public company profile, the core wallet set, board and officer roles, and approval rules for protected matters. Financing, equity grants, and treasury actions stay visible on-chain through tagged flows and anchored approvals.

Template Code

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

Board Governance

Board roles, quorum thresholds, and protected matters define who can approve financings and major policy changes.

Multi-Class Units

Supports common and preferred units, plus pools for grants, with board approvals for issuances and transfers.

Standard Wallet Types

Standard wallet types separate revenue, operating spend, and reserves so capital flows stay easy to follow.

Tagged Flows

Payments and capital events carry tags that show purpose, approval path, and round context.

Template Position

CORP-VENTURE sits above CORP-PRIVATE-STD when board approvals, financings, and pools become part of the operating model. It keeps governance clear without adding committee layers or multi-entity complexity. Simplify to CORP-PRIVATE-STD if board controls are no longer required, or upgrade to CORP-COMPLEX-PRIVATE when committees or multi-entity holdings appear.

Standard Private

Use CORP-PRIVATE-STD for multi-owner teams that require approvals but not board governance.

Complex Private

Use CORP-COMPLEX-PRIVATE for committees, protected matters, and multi-entity holdings with layered approvals.

Solo Template

Use CORP-SOLO when ownership consolidates to one controller and board governance is not needed.

Best Fit

CORP-VENTURE fits venture-backed teams that operate with a board and investor approvals. It suits startups preparing for repeated financings, option pools, and vesting while keeping treasury operations fast and traceable. Day-to-day actions can move quickly, while protected matters follow board thresholds.

Board Governance

Board-led approvals handle financings, unit actions, and policy changes so protected matters are consistent.

Financing Ready

Built for repeat rounds, SAFE or note flows, and capital events that require clear approvals.

Pools and Vesting

Option pools and vesting schedules support hiring and incentives while keeping unit changes governed.

Investor Protections

Transfer restrictions and approval routing keep investor rights aligned with board policy.

Not a Fit

This template is not for teams that do not require board processes or investor approvals, and it is not built for multi-entity or committee-heavy structures. If you only require basic multi-owner approvals, CORP-PRIVATE-STD is a better fit. Donation-led organizations should use nonprofit templates designed for fundraising and allocation.

No Board Process

Use CORP-SOLO or CORP-PRIVATE-STD when board approvals are not required for day-to-day governance.

Complex Governance

Committees, multi-entity holdings, or class-specific approvals belong in CORP-COMPLEX-PRIVATE with layered controls and reporting.

Nonprofit Model

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

Ownership and Units

Keep percentages clear across rounds and grants by using base units. The template supports common and preferred classes plus pools for employee and advisor grants, with approvals for issuances and transfers. Unit actions are protected matters so the board can control dilution and rights.

Base Units

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

Preferred Classes

Preferred and common classes capture investor terms while keeping approvals tied to the board.

Pools and Vesting

Option pools and vesting schedules support grants while keeping unvested units locked by policy.

Authority and Governance

Board authority sets protected matters while officers execute daily operations. Financings, unit actions, and transfer policy changes require board approvals and, when configured, investor consents. Role changes and approvals remain visible on-chain so current authority is clear.

Board Authority

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

Officer Execution

Officers run operating decisions and treasury actions within board-approved policies for day-to-day execution.

Investor Consents

Investor approvals can be required for specific actions to align with term-sheet protections.

Protected Matters

Financing rounds, unit issuances, and transfer policy changes stay gated behind board approvals.

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. Board thresholds keep larger treasury transfers and unit actions waiting for approvals while routine payments clear quickly. Limits can vary by wallet or category so teams follow clear guardrails.

Role Scope

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

Board Thresholds

Board thresholds set the spend or action level that triggers co-sign approvals.

Transfer Controls

Unit transfers and pool grants can require board or investor approval before execution.

Wallet Structure

Separate money by purpose so activity is easy to follow. One wallet receives customer payments, another handles operating spend, and a reserve wallet 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 Wallet

Wallet type RESERVES holds buffers or long-term funds when you decide to set some aside.

Authority Separation

Authority wallets can include board signers for approvals, while payment wallets receive and send funds so control stays separated from cash.

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-VENTURE 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 financings and protected matters, you can attach proof by anchoring a secure reference to board consents, term sheets, or grant 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

Evidence Anchors

Anchors link to board consents, term sheets, or grant letters 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 board controls in place. Setup binds owner and board wallets, defines treasury and transfer policies, and sets cap table or pool rules. 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 Board

Set Wallets and Policies

Connect the standard wallets and set treasury policies with board thresholds and approval rules.

Define Units and Pools

Set the cap table, option pools, and vesting references so equity actions follow board approvals.

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 financings, grants, 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, board approvals, investor consents, and role changes. Each approval entry shows who signed and when, creating a clear decision trail. Anchors timestamp documents 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 grows or simplifies, it can move to a different template without losing continuity. Upgrades add committee governance, multi-entity holdings, or multi-class complexity, while simplification can step down to standard private or solo. The same entity history remains intact across transitions.

Complex Private

Template code CORP-COMPLEX-PRIVATE adds committees, protected matters, and multi-entity holdings for advanced governance.

Standard Private

Template code CORP-PRIVATE-STD fits when board approvals are no longer required but multi-owner roles remain.

Solo Template

Template code CORP-SOLO fits when ownership consolidates to one controller and approvals are minimized.

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.