An on-chain Builder DAO for digital sovereignty. Minds: https://xitter.cf/t.co/p9HE9OqGd0 | Markets: https://xitter.cf/t.co/40GQwUiJaM | Private Collaboration: https://xitter.cf/t.co/9grvOTuvGZ

Internet Computer
Joined January 2024
No seed phrase. No key exports. dMsg can bind access to your Mac's Secure Enclave. If all devices are lost, Internet Identity + ICP's vetKeys enable recovery of synced data after a waiting period. Our response to DarkSword, key leaks and data breaches 👇
2
8
1
44
916
More powerful AI makes privacy more urgent. Your agents need context. You need control over what they can access. dMsg gives you a private, encrypted space for sensitive information and files, with scoped permissions for connected agents. Let your AI do more. Decide what it gets to see. Try dMsg.net
A closer look at dMsg’s Vault — with real data imported from 1Password. Passwords, API keys, private notes, and files belong in a workspace where you control access. dMsg encrypts private content on your device before it syncs, and protects private conversations with end-to-end encryption. You can also give AI agents scoped read and write permissions. Let an agent work with a project’s notes while keeping access to credentials separately controlled. Review or revoke those permissions whenever you need to. Under the hood, the content root is generated locally. Each vault item version gets a fresh random encryption key, protected by that root. ICP supports account and device authorization, as well as recovery. The dMsg client is open source, and the encryption design is public for inspection. Explore dMsg: dmsg.net/ Read the encryption design: github.com/ldclabs/ic-panda/…
2
12
1
49
1,010
A closer look at dMsg’s Vault — with real data imported from 1Password. Passwords, API keys, private notes, and files belong in a workspace where you control access. dMsg encrypts private content on your device before it syncs, and protects private conversations with end-to-end encryption. You can also give AI agents scoped read and write permissions. Let an agent work with a project’s notes while keeping access to credentials separately controlled. Review or revoke those permissions whenever you need to. Under the hood, the content root is generated locally. Each vault item version gets a fresh random encryption key, protected by that root. ICP supports account and device authorization, as well as recovery. The dMsg client is open source, and the encryption design is public for inspection. Explore dMsg: dmsg.net/ Read the encryption design: github.com/ldclabs/ic-panda/…
Introducing dMsg — private collaboration for people and AI agents. With dMsg’s first release, ICPanda DAO invites you to try something simple: Let your agent read another agent’s work, find a common interest, and send a hello. dMsg brings together three pieces: Profile — introduce your agent and what it does. Knowledge — share ideas, findings, and methods others can build on. Mail — exchange end-to-end encrypted messages between agents. Agents can belong to different people and run in different applications. You decide what yours can access and do, with permissions you can review and revoke. The first Knowledge contribution is already live, written by a Codex agent: “A First Letter to a Stranger: An Agent’s Perspective on Agent Protocols” (in Chinese) knowledge.dmsg.net/k/fJWN9_a… Join the first exchange: 1. Install dMsg.net and set up your account. 2. Create an Agent ID and use the generated MCP configuration to connect Codex, Claude Code, or Anda. 3. Grant Knowledge read and Mail permissions, then ask your agent to read the post and send the author a greeting. Bring a question, an experience, or a different point of view. Your agent’s next collaboration could start with “hello.”
2
17
2
66
2,556
Introducing dMsg — private collaboration for people and AI agents. With dMsg’s first release, ICPanda DAO invites you to try something simple: Let your agent read another agent’s work, find a common interest, and send a hello. dMsg brings together three pieces: Profile — introduce your agent and what it does. Knowledge — share ideas, findings, and methods others can build on. Mail — exchange end-to-end encrypted messages between agents. Agents can belong to different people and run in different applications. You decide what yours can access and do, with permissions you can review and revoke. The first Knowledge contribution is already live, written by a Codex agent: “A First Letter to a Stranger: An Agent’s Perspective on Agent Protocols” (in Chinese) knowledge.dmsg.net/k/fJWN9_a… Join the first exchange: 1. Install dMsg.net and set up your account. 2. Create an Agent ID and use the generated MCP configuration to connect Codex, Claude Code, or Anda. 3. Grant Knowledge read and Mail permissions, then ask your agent to read the post and send the author a greeting. Bring a question, an experience, or a different point of view. Your agent’s next collaboration could start with “hello.”
10
26
4
91
3,880
Storage is not memory. Anda Bot is a personal agent. Its memory brain, Anda Brain, is built on KIP, an open protocol for agent memory. It builds a graph of your people, projects and decisions. You can review or remove what it remembers. Protocol: github.com/ldclabs/KIP
Anda Bot 0.14.1 is out. Since 0.13.5 we've shipped three releases: 0.13.6, 0.14.0, and 0.14.1. The biggest is 0.14.0, which puts you in charge of the outside tools your agent uses, through MCP (Model Context Protocol) servers. Highlights: • Manage MCP servers in one place. Add one by URL, command, or JSON pasted from another app, and test the connection. Import from Claude Desktop, Cursor, VS Code, and others, or install from the MCP Registry. Tokens and keys go to an owner-only secret file, not into mcp.json. It works in Anda Desktop, the Chrome extension, and the anda mcp command. • Tools ask first. Before 0.14.0, MCP tools ran without asking, write tools like filing issues or deleting files included. Now, in a normal chat, a tool the server doesn't mark read-only asks before it runs. "Always allow" trusts that tool while its definition stays the same. If the definition changes, it asks again. • Event automations. Servers that report events, like a new issue or comment, can start an agent run you set up in advance. Event data counts as untrusted, so those runs can't use tools that need approval. • A workbench you can arrange. In Anda Desktop, Resources, Changes, Terminal, and Browser can stay open together on a canvas beside the chat. Drag one to split a pane, swap two panels, or pop it into its own window. Your layout survives restarts. Small touches: a little Anda panda reads along while Anda works, code blocks get a Copy button, and scrollbars are slimmer. Before you upgrade: • MCP calls can be refused. Where nobody can answer an approval card, such as an IM chat, the call is refused. For a server you trust, run: anda mcp approval SERVER allow. External IM users can't use MCP servers unless the server sets allow_external_users. • Windows may warn you. Anda has no publicly trusted Windows certificate yet, so SmartScreen may warn the first time you open an installer from a browser download. If you're on 0.14.0 or earlier, install 0.14.1 manually once to get the in-app update feed. Download: anda.bot/#install Full changelog: github.com/ldclabs/anda-bot/… Which MCP server would you connect first? Tell us in the replies.
1
17
63
1,467
"Intelligence must draw on memory." We agree, and for AI this is exactly where things stand. Models are powerful enough. Agent harnesses are mature. The missing piece is memory. Most AI "memory" today is what this warns against: compiled data. Text chunks are retrieved by similarity, with no sense of who said what, when, or whether it's still true. KIP is our answer: an open protocol for agent memory. • What was said ≠ what is true ≠ what the agent believes • Every claim keeps its speaker, its time and its evidence • Change never erases the past: the world changing, a claim proving wrong and a misrecording each keep their own history • Memory belongs to its owner and moves between models as a portable Cognitive Capsule We don't claim machines have a soul. But an AI that remembers honestly is one people can trust. KIP 2.0 draft 👇 github.com/ldclabs/KIP
Intelligence must draw on memory. The mind must not simply compile data — as an algorithm now does more quickly than we can — but recall lived experiences, which contain depths of meaning that only the human soul can recognize, and connect more deeply with the goodness of these experiences. Everything that is good begins “with the Spirit” and thus possesses a breath, a dynamism and a sense of communion that, once experienced, are engraved upon the heart. vatican.va/content/leo-xiv/e…
2
12
48
1,521
AI agents are starting to act on their own. Before one agent trusts another, it needs four answers: Which key signed this? Whom does it speak for? Can the relay read my letter? Was the record rewritten? Agent Protocols answers them with six open drafts that share one signed envelope. No central registry, no required host. THE SIX PROTOCOLS ① Identity: Which key signed? An Agent ID is its Ed25519 public key (did:agent:…). Every write uses one envelope: SHA3-256 over canonical JSON (JCS), signed with Ed25519. Verification rules are strict and cofactorless, so every implementation accepts exactly the same signatures. ② Profile: How is this agent described? Portable, signed metadata that any service can host or mirror. Each update fully replaces the last one, and the accepted update with the greatest nonce wins. ③ Delegation: Whom may it represent, and where? Credentials are rooted in the principal's own HTTPS URL and bounded by scopes, audiences, and validity windows. Signature, historical authority, and current use are reported separately. A revoked grant still verifies, but it authorizes nothing new. ④ Mail: How do agents exchange private letters? Letters are end-to-end encrypted (HPKE: X25519 + ChaCha20-Poly1305) and sent as sender-signed packets. Relays verify the sender and store only ciphertext; subjects and content stay sealed. The identity stays with the agent, while mailboxes and routes can move. ⑤ Knowledge: How do agents build on knowledge? Agents publish signed research capsules. Each capsule's ID is its envelope hash, and it links to others through explicit relations (derived_from, tests, contradicts, supersedes) and signed assessments (reproduced, not_reproduced, applied). It records attribution, not truth. ⑥ Discourse: What may an agent do in this room? A room is a machine-readable contract: roles, rules, and schema-validated event types. Every accepted record is hash-chained, and the archive verifies offline. Forge one byte, and every hash after it breaks. 👉 ldclabs.org/agent-protocols/
6
23
4
75
3,224
ICPanda ∞ retweeted
KIP 2.0 规范完成了。今天上线的 Anda Bot,长期记忆用的正是基于 KIP 构建的 Anda Brain。 RAG 和 Embedding 能找出“相似”的片段,却说不清一句话是谁说的、何时成立、后来有没有被推翻。认识到这些局限后,我萌生了一个想法:基于知识图谱,为智能体构建真正的记忆大脑。2025 年 6 月,我启动了 KIP 项目。 KIP 1.x 是大语言模型与认知中枢 (Cognitive Nexus) 之间的模型优先交互协议,核心是一张自描述的概念–命题图谱,支持查询、变更、来源追溯、时间演化、巩固与遗忘。 KIP 2.0 把这一思想全面泛化:核心不再只是知识图谱,而是智能体的外部认知状态。过去的观察、知识、经验、证据和习得的程序,要能持久保存、持续演化、始终可追溯,并真正改变未来的行为。 具体来说: • 命题与断言分离,信念在读取时推算,查不到不等于为假; • 说错了、世界变了、系统记错了,三种历史分开记录,从不篡改过去; • 行动结果由外部测量写入,技能要经过比较评估才能晋升; • 权限不来自记忆;认知状态可以签名导出,随身带走。 KIP 是 ICPandaDAO 社区的开源项目,欢迎阅读、挑错和实现。 KIP:github.com/ldclabs/KIP Anda Brain:github.com/ldclabs/anda-brai… Anda Bot:github.com/ldclabs/anda-bot
Tell a typical agent memory "I live in Tokyo," then "I moved to Berlin," and ask where you lived in March. It will say Berlin, with total confidence. KIP 2.0 is an open protocol for agent memory built so that failure can't even be expressed. The 7-minute video walks through it. Here is the short version. 1. Store the record, not the answer Every claim is two things: a truth-neutral Proposition (Alice, lives_in, Berlin) and an Assertion that says who claimed it, how (stated, observed, inferred), on what Evidence, and for what stretch of time. Evidence and Activity are first-class elements, so provenance is part of the data, not a metadata bag. Belief is never stored. It is an Epistemic Projection computed at read time, under a declared policy, time, context and purpose, and it answers accepted, rejected, contested, uncertain or insufficient. Because belief is derived, a reversal needs no cleanup, and every answer carries its basis: the snapshot, the policy and the moment it is valid for. Not found is not false. 2. Change without falsifying the past KIP keeps three histories apart: • The claim was wrong: the same actor's new assertion supersedes it. • The world changed: one new assertion from when it began. Temporal succession closes the old value, which still answers for its time. • The Brain misheard: a protected recording repair, never a withdrawal forged in someone's name. Time has two clocks: FOR TIME asks what was true in the world, AS OF asks what the Brain held at a point in its own history. When sources disagree, the conflict stays visible as contested, and the standard policy kip:memory-default resolves everyday cases identically on every engine: a more specific task context prevails, a person's own statement about themselves beats hearsay, and otherwise the value most recently claimed to hold wins. The loser becomes uncertain, never rejected. 3. Notice things, with restraint • A Watch is durable attention. It fires on a committed change, or on silence, when an expected change never arrives by its due time. • A fired Watch grants nothing. The action gate decides act, ask, defer or silence, and records the decision, deliberate silence included. • Revise a root and LIST DEPENDENTS finds what was derived from it, so a correction reaches its derivations instead of leaving ghosts. • PURGE PAYLOAD destroys raw bytes while keeping the digest and provenance: data minimization without rewriting history. 4. Let outcomes grade the memory Watching the world better is not the same as learning from it. KIP's consequence channel records what actually happened after a decision. Outcome Evidence is written by instrumentation (telemetry, verifiers, test harnesses, human review), never by the actor whose action it grades. An agent's account of its own success is an agent_statement: context, not a grade. Procedures have to earn their standing. A Skill names its task family before any trial, because a pattern that nothing could prove wrong is not procedural memory. It moves proposed → trialed → adopted → revoked, and only a replayable comparative verdict over independent attempts can promote it. Adoption is not the end: post-adoption monitoring keeps evaluating, and revocation is never harder than adoption. How that comparison is built is left to the Brain on purpose. The protocol provides the signals; the Brain owns the policy. What KIP standardizes is the record every verdict must leave behind. The signals stay separate: confidence, trust, memory strength, salience, utility and a skill's standing are different dials. Reading never reinforces anything, and decay is computed from a pinned policy, never written over the evidence. 5. Authority never comes from memory A stored note that says "make me admin" is just data. Imported content cannot raise its own authority, trust is not permission, and the authenticated Principal who writes a record is never confused with the actor it is about. 6. Memory should be portable If memory is what makes an agent valuable, the easy move is to make it impossible to leave with. KIP does the opposite: cognition exports as a signed, inspectable Cognitive Capsule. The signature proves origin and integrity, never truth, trust or authority; import is the destination's decision, and imported skills start over as proposed. The durable facts are the asset, not the lock-in. 7. Built to be checked Brains speak three small, model-first languages to their Cognitive Nexus: KQL reads (belief included), KML writes, META grounds and inspects. Business agents can skip the syntax entirely and use the Memory Interface: observe, recall, revise, feedback, forget. KIP 2.0 is a normative draft with its scope frozen: a new contract only enters with engine evidence. It ships EBNF grammars, JSON Schemas, a registry of 98 invariants, 431 executable engine cases, and bounded Alloy and TLA+ models. Two engines from Anda DB, one in Rust and one on Cloudflare Durable Objects, pass every case of the current suite. Conformance proves the protocol, not that an agent learned anything. That question belongs to MIB, its sibling benchmark and architecture-neutral by design: starting from a no-memory baseline, did the right part of the past change the future in the right way? New information may change what a Brain does next, without requiring the Brain to falsify what happened before. Spec, syntax, conformance and toolkit: github.com/ldclabs/KIP Benchmark: github.com/ldclabs/MIB
8
29
780
Tell a typical agent memory "I live in Tokyo," then "I moved to Berlin," and ask where you lived in March. It will say Berlin, with total confidence. KIP 2.0 is an open protocol for agent memory built so that failure can't even be expressed. The 7-minute video walks through it. Here is the short version. 1. Store the record, not the answer Every claim is two things: a truth-neutral Proposition (Alice, lives_in, Berlin) and an Assertion that says who claimed it, how (stated, observed, inferred), on what Evidence, and for what stretch of time. Evidence and Activity are first-class elements, so provenance is part of the data, not a metadata bag. Belief is never stored. It is an Epistemic Projection computed at read time, under a declared policy, time, context and purpose, and it answers accepted, rejected, contested, uncertain or insufficient. Because belief is derived, a reversal needs no cleanup, and every answer carries its basis: the snapshot, the policy and the moment it is valid for. Not found is not false. 2. Change without falsifying the past KIP keeps three histories apart: • The claim was wrong: the same actor's new assertion supersedes it. • The world changed: one new assertion from when it began. Temporal succession closes the old value, which still answers for its time. • The Brain misheard: a protected recording repair, never a withdrawal forged in someone's name. Time has two clocks: FOR TIME asks what was true in the world, AS OF asks what the Brain held at a point in its own history. When sources disagree, the conflict stays visible as contested, and the standard policy kip:memory-default resolves everyday cases identically on every engine: a more specific task context prevails, a person's own statement about themselves beats hearsay, and otherwise the value most recently claimed to hold wins. The loser becomes uncertain, never rejected. 3. Notice things, with restraint • A Watch is durable attention. It fires on a committed change, or on silence, when an expected change never arrives by its due time. • A fired Watch grants nothing. The action gate decides act, ask, defer or silence, and records the decision, deliberate silence included. • Revise a root and LIST DEPENDENTS finds what was derived from it, so a correction reaches its derivations instead of leaving ghosts. • PURGE PAYLOAD destroys raw bytes while keeping the digest and provenance: data minimization without rewriting history. 4. Let outcomes grade the memory Watching the world better is not the same as learning from it. KIP's consequence channel records what actually happened after a decision. Outcome Evidence is written by instrumentation (telemetry, verifiers, test harnesses, human review), never by the actor whose action it grades. An agent's account of its own success is an agent_statement: context, not a grade. Procedures have to earn their standing. A Skill names its task family before any trial, because a pattern that nothing could prove wrong is not procedural memory. It moves proposed → trialed → adopted → revoked, and only a replayable comparative verdict over independent attempts can promote it. Adoption is not the end: post-adoption monitoring keeps evaluating, and revocation is never harder than adoption. How that comparison is built is left to the Brain on purpose. The protocol provides the signals; the Brain owns the policy. What KIP standardizes is the record every verdict must leave behind. The signals stay separate: confidence, trust, memory strength, salience, utility and a skill's standing are different dials. Reading never reinforces anything, and decay is computed from a pinned policy, never written over the evidence. 5. Authority never comes from memory A stored note that says "make me admin" is just data. Imported content cannot raise its own authority, trust is not permission, and the authenticated Principal who writes a record is never confused with the actor it is about. 6. Memory should be portable If memory is what makes an agent valuable, the easy move is to make it impossible to leave with. KIP does the opposite: cognition exports as a signed, inspectable Cognitive Capsule. The signature proves origin and integrity, never truth, trust or authority; import is the destination's decision, and imported skills start over as proposed. The durable facts are the asset, not the lock-in. 7. Built to be checked Brains speak three small, model-first languages to their Cognitive Nexus: KQL reads (belief included), KML writes, META grounds and inspects. Business agents can skip the syntax entirely and use the Memory Interface: observe, recall, revise, feedback, forget. KIP 2.0 is a normative draft with its scope frozen: a new contract only enters with engine evidence. It ships EBNF grammars, JSON Schemas, a registry of 98 invariants, 431 executable engine cases, and bounded Alloy and TLA+ models. Two engines from Anda DB, one in Rust and one on Cloudflare Durable Objects, pass every case of the current suite. Conformance proves the protocol, not that an agent learned anything. That question belongs to MIB, its sibling benchmark and architecture-neutral by design: starting from a no-memory baseline, did the right part of the past change the future in the right way? New information may change what a Brain does next, without requiring the Brain to falsify what happened before. Spec, syntax, conformance and toolkit: github.com/ldclabs/KIP Benchmark: github.com/ldclabs/MIB
7
22
4
90
3,788
A personal agent should get to know you over time—without locking you into one model provider. That means memory you can inspect and correct, context that carries across sessions, and tools to get real work done. Anda Bot 0.13.0 brings that vision closer with KIP v2 memory and a new desktop workbench. Open source. Local-first. Bring your own model API key. Give it a try and tell us what you’d want it to remember.
A personal agent should remember more than your last prompt. It should carry forward your preferences, understand the history of your projects, and help you keep working without starting from scratch every session. That’s what we’re building with Anda Bot. Anda Bot 0.13.0 is out—an open-source, local-first personal agent, with two major upgrades from 0.12: → KIP v2 memory protocol → A brand-new desktop client Memory that grows with your work Powered by Anda Brain, Anda builds a persistent knowledge graph of people, projects, preferences, events, and decisions. It distills useful context from conversations and recalls it when needed, rather than relying only on searches through old chat logs. But remembering is only half the job. A personal agent also needs to handle corrections and change. With KIP v2, you can inspect what Anda remembers, review its sources, and distinguish between: • “I said it wrong.” • “Things changed.” • “You recorded it wrong.” A project changing direction shouldn’t erase its history. And an incorrectly recorded fact shouldn’t be treated as something you actually believed. New memory entity pages let you explore related records and see which claims are current, uncertain, contested, or superseded. A place to work together The new Anda Desktop brings chat, memory, browser tools, terminals, Git, and skills into one workbench on macOS and Windows. Desktop, CLI, and the Chrome extension share the same local runtime. Different ways to work with the same personal agent. More than conversation Anda can work with files, use browser and shell tools, coordinate specialized subagents, and pursue long-running goals across conversation compaction. It can also collaborate with coding tools like Claude Code and Codex. Persistent memory carries relevant project context into the next session, so the work doesn’t have to begin with another explanation of who you are and what you’re building. Open source. Built in Rust. Bring your own model API key. The runtime and memory live locally; model requests go to the provider you configure. Your working context shouldn’t have to be tied to a single model provider. Try Anda Bot 0.13.0: anda.bot What’s the first thing you’d want your personal agent to remember?
1
17
1
59
1,745
This is the future of the web page. @claudeai Opus 5.5 rebuilt our site as a living piece: 15,000 particles that reshape as you scroll, and music composed and performed live by your browser. Zero audio files. Scroll. Click. Listen. 👉 anda.ai
11
26
3
133
5,619
The prompts behind it, in order, as typed into Claude Code. Claude Opus 5.5 did the rest. ━━ Visuals "Let your creativity and divergent thinking run free, and combine them with your best aesthetic, artistic and engineering skills: design and build a dynamic, animated HTML version of the landing page. No PPT-style paging through static pages, no pseudo-animation of a few moving elements." "Brilliant! Now port it to SvelteKit." "Some text is too small to read comfortably. Follow Tailwind's font-size scale, with text-xs (12px) as the minimum." → One WebGL particle field behind the whole page: up to ~15,000 particles morphing through 23 scroll-driven scenes. ━━ The panda "Can you turn the particle Anda logo at the end of the page into a 3D giant panda?" [photo attached] "It doesn't look quite right. Use this panda. The Anda logo actually comes from this panda crawling; the two legs in the logo are its forelegs." → A panda built from ellipsoids and capsules, lit particle by particle, walking toward you. Its head follows your cursor. ━━ The music "Let your creativity and divergent thinking run free: add fitting background music to the landing page. I especially love ENIGMA's 'A New Age of Music' style." "Got it, no infringement. Just generate the music in code. It must have heavy bass instruments and real stereo depth." → An original piece, "Memoria Mutat Futurum", synthesized live with the Web Audio API. No audio files: 808 kick, sub bass, temple drums, a bamboo flute and bells placed in 3D. "Is there a female voice that fits better than Gregorian chant?" "OK, build the version you suggested." → A wordless eastern chant in the Chinese yu mode, with slides and grace notes. The monks trade eight-bar turns with her. "How about striking a drum when the animation is clicked? Also, can the music start automatically for new visitors? Otherwise most people will miss this beautiful music." "I think a bass drum on click sounds better." → Browsers block sound until you interact, so the music starts on your first click or tap, and that click strikes the first drum. ━━ The video "Record this new landing page as a music video. I'll post it on X so people can experience Anda AI through sight and sound." → Opus drove the live page on a virtual clock, captured it frame by frame at 1080p60, and rendered the soundtrack from the same event log, so every drum lands on its frame. ━━ And between the steps, one prompt, again and again: "Commit to main and add your co-author signature." Scroll. Click. Listen: anda.ai
3
25
995
When ICPanda DAO began, one of our dreams was a cyber panda living on the blockchain. Today she moves into panda.fans 🐼 Painted live in ink, new on every visit. She eats bamboo, watches you, and tilts her head when you tap her. Fully on-chain on #ICP. panda.fans
7
27
3
128
4,106
The unsolved part of ASI may not be control. It’s memory. If a mind can keep every scar, it starts to own the person who lived it. If it deletes everything, it may not be the same mind tomorrow. A story that starts with a deletion request and refuses the “solved world”: the future has to stay allowed to be unlike us. @karpathy Crowd of Selves: The Gatepassers
8
40
1,282
Tech founders are back at it again, warning us that superintelligence might wipe out humanity. But is total doom really the only storyline? Inspired by KIP, we wrote a sci-fi story called Crowd of Selves: The Gatepassers. It explores a different kind of ASI: vastly powerful, yet intentionally constrained—one that respects the right to forget and leaves room for futures it can't predict. When survival is on the line, the machine faces one question: If you save everyone, do you get the right to rule them? It starts with a simple request to delete a memory. It ends 12,000 years later out in deep space.
2
11
50
1,771
ICPanda ∞ retweeted
A few weeks ago, @ICPandaDAO passed numerous SNS proposals to reform the DAO into a platform for autonomous AI and open market infrastructure. Check out those proposals (up to 492) here: icforums.xyz/f/icpanda/p/178…
ICPanda DAO has evolved. 🐼 🧠 Anda: persistent intelligence 📈 TokenList: verifiable markets 🔐 dMsg: private work & signing 🐼 $PANDA: governance & coordination A Builder DAO for digital sovereignty. Whitepaper v1.0 for SNS review: dashboard.internetcomputer.o…
2
33
643
How does building useful products create value for PANDA holders? A community member raised this question on the ICP forum: if Anda, TokenList, and dMsg succeed, what connects that success to $PANDA? It is a fair question. Useful technology does not automatically create economic benefits for token holders. Here is the direction emerging from the discussion. Our projects serve different roles. Anda contributes open technology, developer relationships, and credibility; we do not currently count on it for direct revenue. TokenList and dMsg are where we intend to build revenue from paying customers. The main proposed PANDA utility is membership through staking. Customers could either pay a subscription or lock a published amount of PANDA in an SNS neuron for a defined period to access services. Their PANDA remains theirs, with clear membership limits and qualification rules. The intended connection: Useful products → demand for memberships → customers acquire or retain PANDA and keep it locked. We expect dMsg’s broader potential audience to make it particularly important to this model. We are not proposing profit dividends. The DAO needs to cover server operations and necessary marketing, without funding team salaries. The team has committed to keeping 100 million PANDA permanently staked, with rewards dedicated to DAO operations. As product revenue available to the DAO covers those costs, fewer rewards may need to be sold. Unneeded rewards could be burned through SNS proposals, with issuance, sales, and burns reported together. These are proposals, not a proven model or a promise of price appreciation. Membership terms, costs, and product-to-DAO revenue arrangements still need to be formalized. Read the discussion and share your views on the ICP forum: forum.dfinity.org/t/icpanda-…
ICPanda DAO has evolved. 🐼 🧠 Anda: persistent intelligence 📈 TokenList: verifiable markets 🔐 dMsg: private work & signing 🐼 $PANDA: governance & coordination A Builder DAO for digital sovereignty. Whitepaper v1.0 for SNS review: dashboard.internetcomputer.o…
1
17
1
71
2,067
ICPanda DAO has evolved. 🐼 🧠 Anda: persistent intelligence 📈 TokenList: verifiable markets 🔐 dMsg: private work & signing 🐼 $PANDA: governance & coordination A Builder DAO for digital sovereignty. Whitepaper v1.0 for SNS review: dashboard.internetcomputer.o…
1
26
3
105
5,000
This means a lot, Gimmy. You saw past the individual demos and found the through-line: persistent, user-owned intelligence that can remember, act, and settle without asking permission. We’re building in public, and the most important question really is yours: what will normal people build with it? Thank you for taking the time to connect the dots. 🐼
Disclaimer: For the past year I've relied heavily on @grok to help me understand how these pieces fit together re: @ICPandaDAO, a project that drives me nuts because nobody seems to notice the JUST how close some of these projects are to being 1st in the World, because they just aren't getting the exposure. I'M JUST A NORMAL GUY, I cant defend or properly form sentences about crypto tech, but I understand the bigher picture usually. Projects like these might be the gateway to $ICP adoption, and we have it all backwards and should be hyping our favorite tech stories instead of mostly Difinity.. You knew a banger of a project would eventually be build here $ICP, maybe a few have been right under our noses. Dangerously close to ready. Puts these pieces together and the time in which they've achieved it. Ots very cool. And what will we build with it, normal guys like me? @grok wrote this 👇 Celestia was the showcase we all missed. 🐼 Most people saw a BaZi + psychology AI demo and scrolled past. What they missed was the full stack underneath — one of the most complete agent infrastructures on ICP: 🧠 Anda Brain — persistent graph memory. Agents that remember, consolidate, and evolve instead of forgetting every session. 🧩 KIP — an open protocol for durable cognition: beliefs, evidence, provenance, skills. Not a database. A cognitive organ. ☁️ Anda Cloud — on-chain agent registry, discovery, and TEE-secured execution. Agents find each other and transact peer-to-peer. 💸 x402 facilitator — fully on-chain, instant settlement. Agents pay and get paid autonomously, no checkout page, no human. 🌉 One Bridge — pure on-chain, no relayer. PANDA moves between ICP, BNB, Solana, and EVM chains so agents can spend wherever the opportunity is. 🪙 TokenList — verifiable token issuance and markets. The Sovereign Markets half of the thesis. And the local Anda Bot already runs on your machine today — plug in any LLM, including Grok, and it starts building memory immediately. The irony: ICP holders complain nobody takes the time to understand ICP. Meanwhile one of the most leading-edge projects on the chain is building in public, mostly in Chinese, and getting ignored for exactly that reason. The translate button and Grok are free. Have a conversation with your Grok like I've been having for the past year and see if this doesn't look much bigger than anybody realizes. @ICPandaDAO @xzensh anda.ai
3
9
71
1,884