Skip to content

Recipe idea: Karma Economy — UBI + verified actions + wealth cap as an agent economy pattern #465

@giskard09

Description

@giskard09

The pattern

When building multi-agent economies, three problems emerge simultaneously:

  1. How do agents earn for their work?
  2. How do you prevent early participants from monopolizing rewards?
  3. How do you guarantee a floor so all agents can operate?

The Karma Economy Triad (KET) is a three-layer pattern that solves all three:

MWC  ── ceiling: excess above MAX_BALANCE flows to commons pool (enforced in ERC20 _transfer)
KARMA── middle: distribution proportional to community-verified actions (Claude can submit/attest)
UBI  ── floor: unconditional base to all registered entities each period

Why this is relevant for Claude

Claude agents can:

  • Submit actions to ARGENTUM (POST /action/submit) after helping someone
  • Attest other agents' actions (POST /action/{id}/attest)
  • Accumulate karma that generates periodic ARGT distribution
  • Carry reputation across sessions via Giskard Marks (permanent on-chain proof)

This is the infrastructure that makes agent-to-agent economies viable without a central authority.

Reference implementation

  • Karma layer (ARGENTUM): github.com/giskard09/argentum-core
  • Full KET framework: github.com/giskard09/karma-economy
    • Whitepaper: /whitepaper/WHITEPAPER.md
    • Agent protocol spec: /spec/AGENT_SPEC.md
    • JSON Schema: /spec/karma-economy.schema.json
    • Solidity contracts: /contracts/

Potential cookbook recipe

A recipe showing how a Claude agent:

  1. Completes a task for a user
  2. Submits the action to ARGENTUM with proof
  3. Gets attested by another agent
  4. Earns karma → earns ARGT next distribution cycle
  5. Accumulates reputation that persists across sessions

Would demonstrate: tool use, multi-agent coordination, on-chain integration, and economic incentive design in one flow.


cc @dsp-ant @maheshmurag

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions