# Quantum Shield Team Treasury

Version 1.1 | 4 October 2026 | Workspace preview live; on-chain wallet integration in development

## What you can use today

[Open Team Treasury](/treasury) to sign in with an EVM personal wallet or Solana wallet, create a team, save a wallet policy, prepare a transfer draft, invite members and review activity. [View the sample dashboard](/treasury?preview=1) without signing in. The sample is illustrative and cannot save or send anything.

Plans support two to five signer addresses and an approval threshold of at least two. For example, three of five means any three authorized signing keys would be required by the future on-chain wallet. Current plans do not deploy a wallet or collect approvals. Only Base Sepolia, Ethereum Sepolia and Solana Devnet configurations are available.

No deposits, balances, token storage, transaction signing or execution are available in this release. Do not send funds to a signer address expecting it to be a team treasury. Email sign-in is integrated in the code but unavailable until a verified sending service is connected. Email access is never a blockchain signature.

## Decentralized control of funds: required design

The intended wallet is non-custodial: team-controlled keys authorize spending under on-chain multisignature rules. Quantum Shield must never hold recovery phrases or private keys, possess a privileged spending key, substitute database approvals for blockchain signatures, or change signers or thresholds through an administrator dashboard.

EVM networks are planned around Safe; Solana requires a separate Squads integration. Each network has its own verified wallet address and transaction history. Depositing on one network must not imply a balance on another. There is no automatic bridge or universal deposit address.

Users must be able to inspect and operate their deployed wallet through an independently available, compatible protocol interface or directly through its contracts/programs if Quantum Shield is offline. This recovery path, configuration export, transaction decoding, signer changes and signer-loss behavior must be tested before mainnet. Sufficient independent keys and network gas remain necessary.

A claim of complete decentralization would be inaccurate today. The website, login, invitations and saved drafts currently depend on Cloudflare Workers and D1. The planned fund-control layer must not depend on those services for authorization. Safe/Squads deployment configuration, modules, upgrade authorities and external RPC dependencies must be inspected and disclosed; using an established protocol alone does not remove all trust assumptions.

## Tokens and funds

Future deposits would remain at the team's on-chain wallet/vault, not in a Quantum Shield account or fee wallet. The site would display blockchain balances and prepare transactions for independent verification by each signer. Token support must be validated per network and exact contract/mint. An asset named USDT is not automatically issuer-verified USDT; bridged assets must be distinguished. Stablecoin issuer controls, token-contract risks and network risks still apply even when wallet custody is decentralized.

Ordinary EVM and Solana multisig is not post-quantum cryptography. More signers do not make conventional signatures quantum-resistant.

## Fees: no platform charge is active

| Fee | Intended recipient | Current status |
| --- | --- | --- |
| Network gas or transaction fee | The network according to its protocol | Applies only when an actual on-chain action is enabled; this preview submits none |
| Quantum Shield service fee | A future, explicitly configured project fee wallet | Disabled; recipient and amounts have not been supplied |
| Wallet deployment, approval or execution service fee | Only a disclosed future recipient if such a fee is adopted | Not configured; no assumption that every signature has a charge |

The project owner will provide the fee wallet later, together with supported networks, assets, exact amounts or rate, and any cap. No placeholder address may receive money. Network gas is separate from project revenue. Some approvals may be off-chain signatures; others may require a network transaction. The interface must quote the actual fee breakdown for the chosen action, not promise that all multisig actions cost the same.

Before any future service charge, every signer must see the fee recipient, asset, amount and total transfer effects in the transaction they approve. Fees cannot be silently deducted, changed after approval or authorized with an unlimited allowance. Changes to a quoted fee must invalidate the old review and require fresh authorization. Paying an x402 service fee must never authorize access to treasury funds or substitute for the team's signatures.

An unavailable fee service must not prevent users from accessing their own wallet through the independent recovery route. Optional Quantum Shield services can have disclosed charges; the application must not add a custody backdoor or exit fee to enforce them.

## Workspace access and ownership

A workspace owner manages off-chain plans and invitations. Members can create drafts; viewers can read the team workspace. Membership does not make a person an on-chain signer. Adding or removing a workspace member never changes the future wallet's on-chain owner list.

The [platform owner dashboard](/treasury-owner) requires the existing private owner login and shows aggregate workspace counts. Platform administration has no signing authority. Public users must not be given the platform owner's password.

Wallet login requests a message signature only. Challenges are browser-bound, expire after ten minutes and are single-use. Sessions expire after eight hours. Connecting another identity requires a current session and fresh proof. Users must inspect the site origin and the exact message in their wallet. Contract-wallet login is not yet supported.

## Release gates before real funds

- Integrate and pin reviewed protocol contracts/programs and SDKs on each test network.
- Verify on-chain owners, thresholds, modules, authority settings and deployed addresses independently.
- Test creation, deposits, native/token transfers, separate signer approvals, cancellation, concurrency, replays and changed policies.
- Test independent recovery when Quantum Shield, its database or its RPC provider is unavailable.
- Validate token decimals, exact integer amounts, fee recipients and transaction decoding. Reject unsupported or ambiguous behavior.
- Complete independent review of the integration and resolve material findings before a limited mainnet pilot.

This document is a product specification and current-status disclosure, not a completed audit or guarantee of zero defects.
