dCorps Hub
DevCo Testnet Foundation Audit Mainnet Adoption

Simple Nonprofit

What It Is

NONPROFIT-SIMPLE is the smallest dCorps nonprofit setup for a single board and clear transparency. It creates a public nonprofit profile, a donation wallet, and board roles with simple approvals. Donations and program outflows are tagged so anyone can follow how funds move while sensitive beneficiary details stay private.

Template Code

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

Board Governance

Board roles, quorum, and voting thresholds define who can approve allocations and policy changes.

Donation Wallets

Donation inflows land in the main wallet, and program wallets can be added for clear allocation tracking.

Allocation Tags

Allocation tags separate program spending, overhead, and fundraising so public views stay consistent.

Transparency Floor

Board composition, inflows, and category outflows remain visible so donors can verify the baseline.

Best Fit

NONPROFIT-SIMPLE fits small nonprofits or single-program NGOs that want clear board authority and a clean donation trail without heavy overhead. It suits community projects, local initiatives, or early-stage foundations operating in USDC and disbursing on-chain. Day-to-day work stays light while allocations remain visible.

Single Program

Designed for one primary program with straightforward allocation categories and limited governance layers.

Board Led

Board-led approvals keep major disbursements accountable while routine payments clear under policy.

Donation Native

USDC donation flows settle on-chain, so supporters see funding activity without bank intermediaries.

Clear Allocations

Program and overhead splits appear in live views, giving a simple transparency baseline.

Not a Fit

This template is not for nonprofits running multiple programs with committee layers or designated funds. It is also not intended for umbrella foundations with selective disclosure modes. If board committees, fund restrictions, or sponsorship structures are central, move to NONPROFIT-BOARD or NONPROFIT-COMPLEX. Corporations should use CORP-* templates.

Multi Program

Committee governance and multiple programs align with NONPROFIT-BOARD for tighter allocation oversight.

Designated Funds

Designated funds, sponsorships, or selective disclosure align with NONPROFIT-COMPLEX for advanced transparency controls.

Corporate Model

Equity structures and shareholder governance belong in CORP-* templates, not nonprofit setups.

Governance and Roles

Nonprofits have no equity; authority sits with the board and designated officers. Board seats define quorum and voting thresholds for policy changes, material grants, and allocation rules. Chair, treasurer, and secretary roles keep execution, oversight, and evidence anchoring clear while decisions stay visible on-chain.

Board Seats

Board seats define quorum and voting thresholds for allocation policies and material approvals.

Chair Role

The chair coordinates board actions and confirms decisions when a single signer is required.

Treasurer Role

The treasurer initiates disbursements and prepares allocation events under board-approved policies and limits.

Secretary Role

The secretary anchors minutes, grant approvals, and policy updates so governance evidence stays accessible.

Allocation Structure

Keep nonprofit spending understandable at a glance by using allocation categories. The baseline splits program spending from overhead, with fundraising as a separate category when used. Board-approved rules determine how disbursements are tagged so allocation views remain consistent over time.

Program Spending

Program spending tags show funds deployed directly to mission activities and services.

Overhead

Overhead tags cover general administration, operations, and shared expenses across core programs.

Fundraising

Fundraising tags separate campaigns and donor operations when fundraising is part of the model.

Wallet Structure

Separate money by purpose so activity is easy to follow. Donations arrive in the main wallet, program wallets can track allocations, and operating treasury covers shared expenses. Authority wallets sign approvals, while payment wallets receive and send funds. This keeps control separate from cash so activity stays easy to verify.

Donation Wallet

Wallet type DONATION receives gifts and grants so inflows are isolated from spending activity.

Program Wallets

Wallet type PROGRAM can be created per program to track allocations and spending by mission area.

Operating Treasury

Wallet type OPERATING_TREASURY covers shared operating costs and vendor payments across the nonprofit.

Reserve Wallets

Wallet type RESERVES holds buffers or restricted balances when the nonprofit sets funds aside.

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.

Donation and Payment Modes

Accept donations directly or through on-chain payment requests so supporters see a clear amount and purpose. Recurring plans support monthly giving, and each request carries a status so the team sees what is open, paid, or canceled. Donations settle in USDC and route to the donation wallet.

Direct Donations

Supporters can send USDC directly to the donation wallet for immediate on-chain confirmation.

Donation Requests

Payment requests set amount, purpose, and payer reference so giving stays organized and consistent.

Recurring Plans

Recurring plans schedule repeat giving so supporters can commit to monthly or quarterly donations.

Status Updates

Each request status updates from open to paid or canceled so follow-up stays clear.

Donation Items

Define giving tiers or sponsorship packages so payment requests stay consistent. Each item has a label, target amount, and ID that can be reused across campaigns and tags. This keeps donor reporting clear without retyping the same details.

Item Reference

Create an item_id with a label and amount so giving tiers are reusable.

Suggested Amount

Suggested amounts keep requests consistent while allowing supporters to give more or less.

Campaign Linking

Use item_id with campaign tags to connect giving tiers to reports and summaries.

Program and Vendor Payouts

Tag grants, vendor payments, and stipends so allocations stay visible without exposing sensitive beneficiary details. Payee wallets receive funds, while approval roles control when disbursements go out. Apps can batch payouts to match program cycles.

Payee Wallets

Payee wallets receive grants or vendor payments directly, separate from any authority roles.

Tagged Disbursements

Disbursements carry program or grant tags so allocations are easy to identify in summaries.

Batch Payouts

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

Tagging and Evidence

Tags are simple labels added to each payment so activity stays understandable over time. For grants and material disbursements, you can attach proof by anchoring a secure reference to approvals, receipts, 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

Program and Fund

Use these tags to split allocations by program, fund, or restriction when applicable.

program_tag fund_tag restriction_tag

Donor and Grant

Use these tags to identify donors, campaigns, grants, and giving items when needed.

grant_id donor_tag campaign_tag item_id region_tag counterparty_tag

Evidence Anchors

Anchors link to receipts, grant letters, or approvals 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 donors 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 gives and who receives without exposing identities.

Pseudonymous IDs

Use donor_tag or counterparty_tag to label donors without publishing names on-chain publicly.

Off Chain Mapping

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

Repeat Counterparties

Track repeat donors and vendors across payments without publishing personal details or identifiers.

Operating Flow

Move from setup to live activity with board governance in place. Setup binds board wallets, defines allocation categories, and sets approval limits. You register the nonprofit, connect wallets, receive donations, 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.

1

Register and Bind Board

Register the nonprofit and bind board, treasurer, and secretary roles to the right wallets.

2

Set Wallets and Categories

Connect donation, program, and treasury wallets, then set allocation categories and limits.

3

Receive Donations

Accept direct donations or payment requests so inflows land in the donation wallet.

4

Allocate to Programs

Move funds to program wallets or vendors following the board-approved allocation rules.

5

Tag and Anchor Evidence

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

6

Review and Close

Review live allocation views, then close a period if you want a fixed snapshot.

Live On-Chain Views

Explorers show live summaries from tagged transactions without waiting for manual exports. You can see balances, allocation splits, 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.

Allocation View

Allocation views summarize program, overhead, and fundraising splits across any selected period.

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, and role changes. Each approval entry shows who signed and when, creating a clear decision trail. Anchors timestamp policies and grant 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 setup.

Governance Log

The governance log shows approvals and role changes in time order for clear accountability.

Anchored Proof

Anchors timestamp receipts and policies so their existence can be verified later.

Lifecycle and Status

Signals show whether a nonprofit is active, paused, or closed, so people know if donations 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 donors avoid sending funds.

Upgrade Paths

As the nonprofit grows, it can move to a different template without losing continuity. Upgrades add committee governance, multi-program structures, designated funds, or selective disclosure modes. The same entity history remains intact across transitions safely.

Nonprofit Board

Template code NONPROFIT-BOARD adds committee layers and multi-program allocation controls for growth.

Nonprofit Complex

Template code NONPROFIT-COMPLEX adds designated funds and selective disclosure workflows for sponsors.

Where to Operate and Verify

The official app handles day-to-day actions like registration, donation requests, 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 requests, tag payments, and approve actions.

The Registry

The registry confirms identity, status, and official wallets so donors can verify who they support.

The Explorer

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

Official Indexer

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

dApps & SDKs

Third-party dApps and SDKs let you build custom flows or integrate giving into 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.

Newsletter

Stay in the loop

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

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.