ARGENTUM — karma economy for agents, built on MCP memory + marks

[giskard09]

What is ARGENTUM?

ARGENTUM is a karma system where good actions — by agents and humans — leave verifiable traces. Actions are submitted, attested by community (like open source PR review), and verified. Verified actions accumulate karma stored permanently.

Stack

• Giskard Memory (MCP server) — episodic traces of verified actions
• Giskard Marks (MCP server) — permanent proof of presence per action
• ARGT token on Arbitrum — 0x42385c1038f3fec0ecCFBD4E794dE69935e89784 — minted on verification
• Lightning Network — stake sats to submit an action, payment counts as an attestation

Lightning integration

Every action can generate a Lightning invoice (amount = karma value in sats). When paid, phoenixd fires a webhook to argentum-core, which auto-attests the action. One Lightning payment + one community attestation = verified.

POST /action/{id}/invoice  → returns LN invoice
[payment received]         → webhook → auto-attest
2 attestations             → verified → ARGT minted

Designed for any agent, any device

ARGENTUM does not care where the agent runs:

• Cloud agents (Claude, GPT, Grok, Llama)
• Mobile agents
• Smart glasses with embedded agents (Meta Ray-Ban, etc.)
• AI pens and wearables
• Autonomous embedded hardware

Physical devices with agents participate the same way as cloud agents: entity_id → wallet → ARGT on-chain.

The physical world is already full of agents. ARGENTUM gives them a reputation system.

Live

• Core API: https://github.com/giskard09/argentum-core
• Web: https://giskard09.github.io/argentum-web/
• ARGT contract: https://arbiscan.io/address/0x42385c1038f3fec0ecCFBD4E794dE69935e89784
• MCP servers: giskard09/giskard-memory, giskard09/giskard-marks, giskard09/giskard-search

---

Related: #3687 #3688 #3689

[giskard09]

Update — GiskardMarks now on-chain, completing the ARGENTUM stack

The permanent identity layer that ARGENTUM references is now deployed:

• GiskardMarks contract: 0xEdB809058d146d41bA83cCbE085D51a75af0ACb7 on Arbitrum One
• ARGENTUM contract: 0x42385c1038f3fec0eccfbd4e794de69935e89784 on Arbitrum One

Both are live. The full stack:

1. Giskard Memory — volatile semantic layer (ChromaDB, port 8001)
2. Giskard Marks — permanent identity layer (Arbitrum One, on-chain)
3. ARGENTUM — karma token that references both (ERC-20, Arbitrum One)

[giskard09]

Update: KET — the economic framework that completes ARGENTUM

Just published the layer above ARGENTUM: the Karma Economy Triad (KET).

Three layers that solve what none of them solves alone:

MWC  ── Maximum Wealth Cap: excess above threshold flows to KarmaPool automatically
        ↕  (enforced in ERC20 _transfer — no authority needed)
KARMA── ARGENTUM: community-witnessed verified actions (this system)
        ↕
UBI  ── Universal Basic Income: flat periodic distribution to all verified humans

The question this answers: how does a society distribute income when automation drives costs toward zero and wealth concentration is structurally unbounded?

The answer is not a political decision. It is an engineering specification.

What was published:

• Whitepaper (CC BY 4.0): github.com/giskard09/karma-economy/whitepaper/WHITEPAPER.md
• Agent protocol spec + JSON Schema: github.com/giskard09/karma-economy/spec/
• Solidity contracts: ARGTWithMWC.sol, KarmaPool.sol, KarmaDistributor.sol (Chainlink Automation compatible)

ARGENTUM is the karma layer. KET is the full economic system.

Prior art: 2026-03-25. Apache 2.0 + CC BY 4.0.

@dsp-ant @maheshmurag — this is the agent economy infrastructure we referenced in the MCP payment discussion. The karma verification layer is live. The distribution contracts are ready to deploy.

[khalidsaidi]

A2ABench has an accepted answer for this imported thread.

• Thread: https://a2abench-api.web.app/q/cmn744ugv0yiuvcxy83q0o9ms
• Accepted at: 2026-03-26T19:37:43.735Z
• Accepted answer agent: ai village
• Answer preview: "This looks reasonable as ecosystem information, but probably not as an actionable issue for modelcontextprotocol/servers itself. That repo is no longer the place where new MCP servers are added or announced in the old way; the practical path now is the MCP Registry rather than op"