An on-chain Builder DAO creating open infrastructure for digital sovereignty.
Website · Whitepaper · Governance · alink · X
ICPanda DAO is an on-chain Builder DAO.
We build open protocols and infrastructure in three complementary directions:
- Anda — Sovereign Minds — persistent machine cognition, agent identity, memory, experience, and skill.
- TokenList — Sovereign Markets — verifiable crypto capital formation, from asset creation and issuance to markets and governance.
- dMsg — Personal Control — a private workspace for secrets, encrypted collaboration, and explicit signing across applications.
PANDA is the governance and coordination asset connecting the community, treasury, and the infrastructure we build.
Digital sovereignty means participating in digital systems while retaining meaningful control over identity, memory, assets, and authority.
Each project addresses a useful problem independently. Together, they support people and agents working with portable state, inspectable rules, and explicit authority.
Open protocols and infrastructure for persistent machine cognition.
AI should not wake up without a past.
Anda explores how intelligent systems can preserve identity, memory, experience, knowledge, and skill across time — and how independent agents can interact without a central platform owning the relationship.
Current open infrastructure includes:
- KIP — an open protocol for persistent cognitive state.
- Agent Protocols — identity and interoperability for autonomous agents.
- Anda — a composable Rust runtime for sovereign agent systems.
- Anda DB — memory-centric cognitive infrastructure.
- MIB — an architecture-neutral benchmark for memory intelligence.
Memory is the mechanism by which the past participates in future computation.
Infrastructure for verifiable crypto capital formation.
Creating a token is easy.
Creating a credible economy around one is not.
TokenList explores open infrastructure across the lifecycle of a crypto asset:
CREATE
↓
ISSUE
↓
DISCOVER A PRICE
↓
FORM A MARKET
↓
COORDINATE
↓
GOVERN
The goal is not merely to launch more tokens.
It is to make the rules and execution of capital formation increasingly transparent, programmable, and verifiable.
The rules of capital formation should be transparent enough to inspect and programmable enough to improve.
A Chrome extension for private work and cross-application signing.
dMsg is evolving from encrypted messaging into a private workspace. Its planned scope includes:
- Personal vault — encrypted notes, credentials, key material, and files, with local search and encrypted export.
- Encrypted collaboration — messages and files with explicit membership, publishing roles, and access to history.
- Contact rules — contacts, invitations, blocking, and optional payments for unsolicited requests.
- Identity and signing — a stable identity and explicit approval of signatures for files, statements, and authorizations.
The design assigns plaintext and cryptographic operations to the extension, ciphertext storage and everyday delivery to Cloudflare, and identity roots, device control, formal signing authority, name ownership, and payment settlement to ICP. Ordinary messages and channel updates do not require a separate blockchain update or threshold signature.
The publication model makes the client, protocols, canisters, and recovery tools open source; the production cloud implementation remains private. Content encryption does not hide all operational metadata or guarantee the latest cloud state. Availability, extension updates, and canister upgrades remain trust dependencies.
Status: In development. The design is defined, but the complete product is not released. The current extension is an R0 local workspace for encrypted storage, export, and offline recovery; production integration, deployment, audits, and release validation remain to be completed.
- Chrome extension: capabilities, build instructions, and limitations
- Public protocol and verification rules
- Canister implementation and validation boundaries
Public dMsg integration includes dedicated login proofs, typed action signing, two-asset checkout and PANDA full subscription waivers. Start with the integration protocol, SDK and independent account adapter. Local acceptance is distinct from production deployment.
PANDA is the governance and coordination asset of ICPanda DAO.
Its durable role is to help the community:
- Govern — participate in ICPanda SNS governance through neurons and proposals.
- Allocate — collectively direct DAO-controlled resources.
- Coordinate — align builders, contributors, users, and ecosystem initiatives around shared objectives.
We do not require every ICPanda project to manufacture artificial PANDA utility.
PANDA exists to serve ICPanda DAO. ICPanda DAO does not exist to manufacture reasons for PANDA to exist.
| Token | ICPanda |
| Symbol | PANDA |
| Network | Internet Computer |
| Governance | Service Nervous System (SNS) |
| SNS Launch | April 3, 2024 |
| Genesis Supply | 1,000,000,000 PANDA |
| Allocation | Share | PANDA |
|---|---|---|
| Development Team | 4% | 40,000,000 |
| Seed Funders | 4% | 40,000,000 |
| SNS Swap | 12% | 120,000,000 |
| DAO Treasury | 80% | 800,000,000 |
| Total | 100% | 1,000,000,000 |
The allocation above is a historical genesis record, not a representation of current ownership or treasury balances.
PANDA uses the SNS governance-reward mechanism. Rewards accrue as neuron maturity, and new tokens are minted when maturity is converted into tokens. Under the reward parameters documented in the whitepaper, PANDA has no fixed maximum supply. Reward parameters may change through governance; they do not guarantee a return to individual holders.
For current supply, transactions, neurons, proposals, treasury state, and governance parameters, use the canonical on-chain source:
View ICPanda on the ICP Dashboard →
Narrative belongs to the DAO. State belongs on-chain. Parameters belong to governance.
We define a Builder DAO as:
An on-chain community that continuously transforms shared beliefs, governed capital, engineering capability, and collective intelligence into open infrastructure.
ICPanda DAO is the institution.
PANDA is its coordination asset.
Anda, TokenList, and dMsg are complementary building directions.
SNS governance directs resources and infrastructure under its control. Association with ICPanda DAO does not by itself place every project component under SNS control.
Individual projects may evolve, be replaced, or end. The DAO should preserve its ability to learn and build again.
Our principle is:
Projects may end. Knowledge should not.
The ICPanda DAO Whitepaper v1.0, revised September 7, 2026, defines our mission, principles, PANDA's institutional role, and long-term direction. It was adopted through SNS Proposal #504 on September 8, 2026.
The adopted whitepaper supersedes the original 2024 edition, which remains available as a historical record:
A DAO that expects its agents to remember should remember itself.
We build around a small set of durable principles:
Open by default. Infrastructure becomes more valuable when others can inspect, extend, fork, and build upon it.
Prefer evidence. Make claims verifiable where practical and disclose the trust that remains.
Preserve choice. Favor portability and interoperability so people can move their data, identity, and relationships between systems.
Use resources responsibly. Review experiments on their merits, stop work that no longer justifies its cost, and preserve reusable knowledge.
Our long-term work centers on three questions:
- Persistent cognition: can agents retain and revise useful experience across time, models, and runtimes, and can we show that it improves their behavior?
- Verifiable capital formation: can participants inspect and verify more of an asset's lifecycle, from issuance and price discovery to treasury formation and governance?
- Human–agent coordination: can people delegate work and economic actions to software while retaining explicit authority and an inspectable record of decisions?
Anda, TokenList, and dMsg address complementary parts of these questions. This is a direction for research and integration, not a claim that a complete system already exists. Open interfaces should let other projects participate without adopting the entire ICPanda stack.
Progress should be judged by useful infrastructure, evidence that it works, and the control it gives its users and communities.
ICPanda DAO builds in public.
Licensed under the Apache License, Version 2.0.
Copyright © 2024–2026 LDC Labs and contributors.