Reference Wallet | dCorps Hub

Signing Scope

Reference interfaces (testnet) are the public tools that read or submit Hub actions, and wallets are the signing layer for approvals. Interfaces are reference access points; the protocol is the authority. Protocol scope is defined in the protocol overview. Entities retain control of funds; the Hub anchors authority and events. Operations are stablecoin-native; no fiat rails or custody.

Non-custodial Keys

Keys stay with the signer; the wallet never holds funds or approvals on your behalf.

Authority and Payments

Authority wallets approve roles and governance; operations wallets move funds under the approvals you set.

Gas and Stablecoins

Transactions use DCHUB for gas while payments move in stablecoins tagged to business context.

Reference Interface

Wallets sign actions; validation and correctness are defined by protocol rules on-chain.

Compatible Wallets

Testnet signing uses compatible EVM wallets today. MetaMask is a common option for Hub actions and approvals, with Rabby and WalletConnect-compatible wallets also supported for standard signing flows. A dCorps-aligned wallet is planned for a later phase (phase-gated) to surface roles, tags, and approvals with clearer prompts and default policies.

MetaMask

Popular EVM wallet for Hub testnet signing and approvals with standard transaction review.

Rabby Wallet

EVM-native wallet with clear signing previews for Hub actions and approvals.

WalletConnect

Connect supported mobile and desktop wallets for standard EVM signing flows.

dCorps Wallet (planned)

Purpose-built wallet planned for a later phase to surface Hub roles, tags, and approvals clearly.

Signing Flow

Turn approvals into on-chain, time-ordered, tamper-evident state by signing locally. The flow is the same across apps: prepare the action, review roles and routing, sign locally, then verify the posted event in public views before approvals settle.

Draft Action

Create the action in the official app or SDK with amounts, tags, and target wallets.

Review Authority

Check that the signer role and approval policy match the action scope and limits.

Sign Locally

Sign with the user-controlled key; the wallet never exports private keys or approvals.

Verify On-Chain

Confirm the transaction is posted and visible in explorer or indexer views.

Wallet Roles

Entities map different wallets to different duties so approvals and payments stay clear. Authority wallets hold the roles that can approve governance or policy changes, while payment wallets move funds for operations, payroll, merchant checkout, or donations. The wallet view shows which role is signing and which wallet will execute the transfer.

Authority Wallets

Controls owner or board approvals, role changes, and governance actions tied to the entity.

Operations Wallets

Handles day-to-day payments, vendor payouts, and expense flows under defined approval limits.

Treasury Wallets

Holds reserves and long-term balances, including DCHUB holdings, with stricter approval thresholds.

Merchant and Donation Wallets

Receive customer payments or donations routed from invoices, checkout links, or public giving pages.

Security Responsibility

Assign security to the entity and its operators. The wallet only signs what the user approves, and the protocol enforces role rules. This matrix clarifies who owns key storage, transaction review, and recovery planning so teams can assign accountability before they sign.

Responsibility	Owner	Notes
Key storage and access	Entity or signer	Keys stay with the signer; no custody or recovery services are provided.
Transaction review	Signer	Signer verifies amounts, tags, and destination before approval is submitted.
Role updates	Authorized owners or boards	Role changes require signed approvals and appear in on-chain views.
Device and backup hygiene	Entity or signer	Backups and device security follow the entity's internal policy.

Testnet Boundaries

These interfaces operate in testnet conditions where resets and partial coverage are normal. Status is testnet; no claims beyond current capability. Treat outputs as integration signals and confirm behavior against the current bundle before relying on them.

No Custody or Insurance

The wallet does not custody funds, insure keys, or provide recovery services for lost access.

Testnet Resets

Testnet resets can clear balances and history, so avoid relying on persistence.

Coverage Shifts

Coverage and tooling can shift as the protocol evolves; confirm outputs against the current release.

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.