ICPanda DAO Has Evolved
Why we rewrote our whitepaper—and what we are building next.
ICPanda began in 2024 as a panda meme community on the Internet Computer. Our first whitepaper reflected that beginning: community incentives, badges, NFTs, and an early Web3 roadmap.
Two years of building changed our direction. Work on encrypted messaging, cryptographic identity, AI agents, and token issuance revealed problems that reached beyond any one product.
Our new whitepaper, From Sovereign Minds to Sovereign Markets, brings that work into a common purpose: open infrastructure for digital sovereignty. It is proposed for SNS governance adoption.
From a community to a Builder DAO
PANDA brought people together. SNS governance gave the community a way to direct shared resources. Building gave us a clearer understanding of what those resources could make possible.
We now describe ICPanda DAO as a Builder DAO: a community that uses shared governance, capital, and engineering to build open infrastructure.
The institution’s purpose is to learn, allocate resources, and build again. Products can evolve or end while their code and lessons remain useful. Our work currently follows three complementary directions.
Anda: give intelligence a past
AI agents can complete complex tasks yet struggle to carry experience from one task to the next. Retrieving an old statement does not tell an agent whether it remains true. Recording a failed action does not ensure that the next attempt improves.
Anda builds open protocols and infrastructure for persistent machine cognition: identity, memory, experience, and skill that can survive changes in applications and models.
The work spans KIP for persistent cognitive state, Agent Protocols for identity and interoperability, and Anda Runtime and Anda DB for implementation. MIB, the Memory Intelligence Benchmark, tests whether using relevant history improves future behavior.
The aim is intelligence that can learn from a past it can carry forward.
TokenList: make capital formation verifiable
Our own token economy exposed another set of problems. Creating a token is straightforward; distributing ownership, discovering a price, building liquidity, and governing shared capital require more care.
TokenList addresses that broader lifecycle: asset creation, issuance, markets, and governance.
Participants should be able to examine what is being offered, how allocation works, where proceeds go, and whether execution follows the stated rules. Auction mechanisms are part of this work, and their design should remain open to improvement.
Transparent rules give participants better evidence. They do not guarantee a successful market or establish legal compliance.
dMsg: keep control of private work
Our early messaging work continues in a new direction. dMsg is evolving into a Chrome extension for private work and cross-application signing.
Its design starts with individual utility: keep a private note, credential, or file. From there, users can share encrypted material with selected people, control incoming contact, and approve signatures for specific statements or files.
The architecture combines encryption on the device, cloud delivery, and ICP for identity, sensitive authorization, and settlement. It keeps application access separate from vault access and formal signing authority, while making the remaining cloud and upgrade dependencies explicit.
The new extension design is defined; implementation, deployment, audits, and release validation remain to be completed.
Why these directions belong together
Digital sovereignty means participating in shared systems while retaining meaningful control.
Anda addresses continuity of identity and experience. TokenList addresses verifiable economic rules. dMsg addresses personal data and explicit authorization. Each serves a practical need independently.
They also share a longer horizon. A community using agents to research proposals or assist with economic workflows needs reliable memory, inspectable rules, and clear authority. These projects address different parts of that problem. Their integration remains an area of exploration, with open interfaces intended to support other builders too.
PANDA coordinates the institution
PANDA’s lasting role is governance and coordination: helping the community make decisions, allocate DAO-controlled resources, and support shared work through the SNS.
Product utility should emerge where it improves a real system. We do not require every project to manufacture PANDA demand. Governance rewards and other monetary parameters remain subject to SNS decisions.
Leadership and expertise remain necessary. Our commitment is to make authority visible, treasury decisions transparent, and development open to scrutiny.
A new whitepaper, with our history intact
The new whitepaper explains this mission, the projects, PANDA’s role, and the principles guiding future work. Formal adoption belongs to SNS governance; product specifications and operational roadmaps remain in their own documents.
The 2024 Genesis Whitepaper stays public. It records what we believed, what we attempted, and how our direction changed.
We will continue to judge projects by what they contribute, preserve useful knowledge, and revise our plans as evidence improves. That capacity to keep learning is what we want ICPanda DAO to sustain.
Read the whitepaper · Explore ICPanda DAO · Follow SNS governance