Complex Nonprofit Template

What It Is

NONPROFIT-COMPLEX is the advanced dCorps nonprofit setup for designated funds, umbrella sponsorships, and privacy-aware disclosure. It creates a public nonprofit profile, donation and program wallets, and committee roles with defined scopes. Fund policies, allocations, and material grants stay visible on-chain through tagged flows and anchored evidence.

Template Code

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

Board + Committees

Board and committee roles define approvals for fund policies, sponsorship onboarding, and material disbursements.

Designated Funds

Restricted and unrestricted funds use labels and tags so money stays separated and policies remain clear.

Umbrella Programs

Program wallets and sponsorship tags keep partner initiatives distinct while supporting consolidated views.

Selective Disclosure

Disclosure modes allow public aggregates with private detail while preserving the transparency floor.

Best Fit

NONPROFIT-COMPLEX fits umbrella NGOs, fiscal sponsors, and foundations managing designated funds and partner programs. It suits teams with finance, audit, grants, or sponsorship committees that operate under formal fund policies. Day-to-day payments stay efficient while large allocations and policy changes follow defined approvals.

Fund Controls

Fund policies and restrictions separate restricted and unrestricted money across programs and reporting views.

Sponsorship Programs

Partner projects run under sponsorship agreements with committee approvals and clear disbursement tracking.

Audit Ready

Evidence anchors and governance logs support audits, grant compliance, and policy change histories.

Privacy Modes

Selective disclosure keeps sensitive line items private while public aggregates remain verifiable.

Not a Fit

This template is not for small single-program nonprofits or for board-only structures without designated funds. It is also not meant for groups that only require committee oversight without sponsorship or privacy modes. If designated funds or selective disclosure are not in scope, NONPROFIT-BOARD or NONPROFIT-SIMPLE is a better fit.

Simple Nonprofit

NONPROFIT-SIMPLE fits single-program teams without committee layers or designated fund policies today.

Board Nonprofit

NONPROFIT-BOARD covers committee governance without designated funds or selective disclosure modes yet.

Corporate Model

Equity structures and shareholder governance belong in CORP-* templates instead of nonprofits.

Governance and Roles

Nonprofits have no equity; authority sits with the board and delegated committees. Board seats define quorum and voting thresholds for fund policy changes, major allocations, and sponsorship approvals. Committee roles handle finance, audit, grants, and sponsorship oversight, while secretary roles anchor decisions for public evidence.

Board Seats

Board seats define quorum and voting thresholds for fund policies and material allocations.

Committee Roles

Committees cover finance, audit, grants, and sponsorship approvals with defined scopes and thresholds.

Treasurer Role

The treasurer initiates disbursements and prepares allocation events under board and committee policies.

Secretary Role

The secretary anchors minutes, fund policies, and sponsorship agreements for public evidence.

Designated Funds and Programs

Separate restricted and unrestricted money while keeping program budgets clear. Program wallets and tags tie disbursements to specific funds, projects, or sponsorship agreements. Fund policies are anchored so donors and auditors can verify how restrictions apply across programs.

Restricted Funds

Restricted funds carry policy tags so spending follows donor or grant constraints.

Unrestricted Funds

Unrestricted funds stay flexible while still labeled so overall allocation remains transparent.

Program Wallets

Program wallets map funds to initiatives, keeping disbursements aligned with specific missions.

Sponsorship Agreements

Sponsorship agreements anchor partner projects to program wallets and approval scopes clearly.

Allocation Policy

Define routine and protected disbursements across programs and funds with on-chain allocation policies. Committees can set thresholds for grants, program transfers, or fund changes, while the board approves policy updates. Evidence anchors tie policy decisions to supporting documents so allocation shifts remain accountable.

Program Rules

Program rules define which wallets and tags apply to each program allocation.

Fund Restrictions

Fund restrictions enforce how restricted money can be moved or spent properly.

Approval Tiers

Approval tiers separate routine disbursements from protected grants and policy changes clearly.

Wallet Structure

Separate money by purpose so activity is easy to follow. Donations arrive in the main wallet, program wallets 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 tracks program budgets, designated funds, and sponsorship disbursements by mission area.

Operating Treasury

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

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 scheduled 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.

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.

fund_tag restriction_tag program_tag project_tag

Donor and Reporting

Use these tags for donors, grants, campaigns, and impact reporting when applicable.

grant_id donor_tag campaign_tag item_id beneficiary_tag impact_area_tag region_tag counterparty_tag

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 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.

Disclosure Modes

Control what is public while preserving a transparency floor. Mode A shows full on-chain detail. Mode B publishes aggregates with commitments to private data. Mode C anchors private execution when private zones are used, while public totals and governance updates remain visible.

Mode A Full

Full detail is public, showing every tagged flow and wallet movement clearly.

Mode B Aggregate

Public aggregates are shared with commitments, while private data goes to authorized reviewers.

Mode C Private

Private execution anchors commitments on-chain while public totals and governance updates remain visible.

Counterparty Directory and Privacy

Repeat donors, grantees, 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.

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 sensitive personal details.

Operating Flow

Move from setup to live activity with board and committee governance in place. Setup binds board and committee wallets, defines fund policies, and sets disclosure mode. 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.

Register and Bind Governance

Define Funds and Policies

Define designated funds, approval thresholds, and policy rules for restricted money flows.

Set Wallets and Disclosure

Connect donation, program, and treasury wallets, then set the disclosure mode and tags.

Receive and Allocate

Accept donations and move funds to designated programs or partners per approved policies.

Tag and Anchor Evidence

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

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, program and fund 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, fund, and overhead 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, policy changes, and role updates. 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 simplifies, it can move to a different template without losing continuity. Simplification can step down to board or simple nonprofit structures when designated funds or disclosure modes are no longer used. The same entity history remains intact across transitions.

Nonprofit Board

Template code NONPROFIT-BOARD fits when committee governance remains but funds simplify.

Simple Nonprofit

Template code NONPROFIT-SIMPLE fits when committees and fund policies are removed.

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.

Request testnet access

Newsletter

Stay in the loop

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