Help sustain the verifiable trust community through six shared resource pools: Compute, Memory, Connection, Delegation, Protection and Value. Together they support the research, tools and people that make public goods possible. Mages City is the first community home.
Six shared pools — Compute, Memory, Connection, Delegation, Protection and Value — match what workshops need with what contributors offer. Money, time, model tokens, hardware, energy and private knowledge are resources recorded within the relevant pools. A resource can support several dimensions, with its allocation counted once.
Machines, inference, model tokens and energy for useful execution.
Processing, model execution and evaluation.
ComputeOffer machine-hours, private inference, reproducible runs or hosted tools. Record useful capacity delivered and the conditions of access.
Private knowledge, research, storage, documentation and maintained context.
Knowledge, state, storage and continuity.
MemoryContribute private knowledge, research, lived experience or maintained archives through permissioned access. Record provenance, permitted uses and retention terms; the underlying material can remain private.
Consented relationships, introductions, connectivity and community bridges.
Interoperability, shared services and collaboration.
ConnectionOffer consented introductions, trusted access, translation and community bridges. Private knowledge becomes useful through scoped relationships, not compulsory disclosure. Record permission and the collaboration enabled.
Bounded agent work, open models, skills and accountable task mandates.
Scoped agent work, model access and accountable hand-offs.
DelegationOffer open models, agent runtimes, reusable skills or responsibility for a bounded task. Record the mandate, resource limit, accountable person and evidence returned.
Privacy engineering, security review, access boundaries and independent verification.
Privacy, security, boundaries and independent checks.
ProtectionOffer security review, privacy engineering, key stewardship and independent verification. Record what was checked, under which assumptions, and what still needs attention.
What this community recognises, rewards and chooses to sustain, defined through its governance.
Explore Value visually ↗Community-defined value, agreed priorities and recognition.
ValueThe community agrees what counts as value, how it is recognised and what evidence supports it. Money, stewardship, public-good outcomes or other priorities may be included under that policy. Keep the definition and its revision visible without exposing private context.
All six express value. Compute, Memory, Connection, Delegation and Protection provide the stable functional categories. Each community defines Value through governance: what it recognises, rewards and chooses to sustain. Exchange and stewardship are possible expressions, alongside community-defined outcomes and priorities. Maintainer work and contributor time belong to the dimensions they serve.
The coordinates stay familiar. The community decides what a worthwhile outcome looks like.
Illustrative choices, not adopted community policies.
Useful knowledge shared on the contributor’s terms, with context and provenance intact.
Memory · Connection · Protection
A recipient accepts a useful consultation; the contributor confirms that access and reuse stayed within the agreed scope.
A permissioned reference, a trusted introduction, archive space or time to explain the context.
Governance chooses the definition, evidence and recognition. The same contribution can be valued differently by different communities.
A private knowledge consultation can serve three dimensions without becoming three promises.
A permissioned knowledge consultation
One allocation ID · one 4.2-hour commitment · several dimensions served. Any hour attribution across pools must sum to 4.2; the tags do not multiply it. Recognition follows the receiving community’s Value policy.
An agent holds a scoped promise.
Participants agree what they value and how work is accepted.
Communities connect, keeping their own definitions and boundaries.
The agreement stays with the relationship.
A proposed path through relationships and practice. Joining a network does not require every community to adopt the same Value definition.
These categories can seed purpose-led Verifiable Trust Agents. As sustained work and relationships develop, participants can form Verifiable Trust Communities; connections among communities can grow into Verifiable Trust Networks. This is the decentralised trust graph taking shape.
The six Star pools sustain the work at every scale. The six resource dimensions help match projects with support. Trust grows through shared work and verified relationships.
The Star’s six dimensions are the pools themselves. Projects express needs and contributors express offers in the same coordinates.
A project describes its needs as a combination of these categories. Workshops offer the relevant capabilities and available resources. Mages City can use those matches to inform allocations across the six Star pools, so shared infrastructure and specialist work support one another.
The proposed funding profile reuses the runtime’s six-bit order: Protection · Delegation · Memory · Connection · Computation · Value, most significant bit first. In that convention, 010000 describes Delegation alone. Open-source model work may also need Compute, Memory or Protection; its profile follows its actual scope.
A funding need profile is a separate, versioned use of the Star vocabulary. It does not reinterpret a participant’s identity, consent or existing posture. Bits identify needs and combinations; an adopted policy must determine weights, eligibility and the resulting distribution.
Fair allocation needs more than counting active bits. Review the public benefit, resource availability, completed work and unmet needs; prevent duplicated requests and conflicts of interest, and provide a way to challenge and revise decisions. This mapping is a design proposal, not a live allocation engine or a measured fairness result.
Contribute knowledge, relationships, tools, care, money or time through the six resource pools.
Private knowledge chiefly touches Memory and Connection. A contributor can promise a scoped consultation, a permissioned reference or an agreed result without publishing the source material. Protection governs access; Delegation limits what an agent may do with it. Contribution does not transfer ownership or imply consent to train a model.
These are overlapping expressions, not six currencies or an automatic contribution score. The promise board currently drafts money and time pledges; private knowledge can begin as a scoped time commitment, with sensitive terms agreed separately.
The six Star terms describe value without putting a price on every person or project.
Offer → Agree → Allocate → Work → Review
Projects sharing two or more Star needs can pool capacity. At review, uncommitted resources flow toward ready work; shared contributions are counted once. Workshops can serve several projects, and allocations can evolve.
dtgwg-zkp-mage · dual-agent-harness · lexon_pvm · shor_mage · PQC agility research · Yukon autoresearch provisioning
dual-agent-harness · lexon_pvm · Yukon autoresearch provisioning
FedWiki chronicler · hh_workshop · City kappa registry · BGIN research & coordination · Community foundations
dual-agent-harness · FedWiki chronicler · hearthold_mage · hh_workshop · BGIN research & coordination
dtgwg-zkp-mage · MyTerms mage · City kappa registry · Community security agent · PQC agility research · Community foundations
Candidate groups based on current proposed profiles; scope and participation still need agreement. They do not confer funding authority.
This is how we intend to run Labs as well as what we research. New mages bring knowledge and purpose, establish workshops, run agents within agreed limits and form their own verifiable trust agents and communities. The network emerges at the speed of trust.
Each project highlights the dimensions its work serves. Browse the project needs →
These project briefs describe purpose, resource needs and what the work can return. The six Star pools would support them through agreed allocations. These need profiles are proposals for workshop review.
Every project’s address takes a vertex of the 64-vertex lattice; rows are strata, 1·6·15·20·15·6·1. Filled: the vertex of its project’s six values as published on /fund/ (protection 32 · delegation 16 · memory 8 · connection 4 · compute 2 · value 1). Hollow: its first six bits, V = first digest byte >> 2. A project’s need profile is its vertex; choose dimensions or a vertex to filter and order the projects below.
Sustain the deployed First Mage: Bonfires service costs, shared knowledge and maintainer time.
011110 · V30 · proposed need profilesha256:965421cc280b0f6af8179d0541008cd900e63136c72c5491e9dd1735e29186b2
Art, cultural knowledge and creator stewardship, connected through the Curatrix workshop.
101101 · V45 · proposed need profilesha256:f412feb8a1ebd970ff0305ee14b2e56491ff16b48722ade11efc40e501060ab4
Support a verification research team, reference fixtures and independent reproduction.
100110 · V38 · proposed need profilesha256:41ad0aeb1513e009105df706e4d0c8e9c31119e106f1af3f3b7efda210cdb6cb
Research vulnerability handling, threat-information sharing and evidence triage with community security agents.
110100 · V52 · proposed need profilesha256:576c8e4396666e559607eaa71b5efd55e95bd60c08625957cd94f58ab93c5041
Support the team’s research and coordination work, research agents, workshop preparation and public technical contributions.
011100 · V28 · proposed need profilesha256:3ec813ba73c2091816ae2254308cd6cef2de4af0c1d031df2926e2720cb5dab6
Build migration testbeds, evaluation tooling and research runtimes supporting open crypto-agility competition work.
100110 · V38 · proposed need profilesha256:56649fd7230cb96102dc96f6d8edd1df99b4f30d49a3cdd52fc3369686489b46
A shared harness for scoped agent research, reproducible runs and independent verification.
111010 · V58 · proposed need profilesha256:5e5708b504aa1633301e7bc09b91d5960a09db711e2dc7811eedbaf6e7208f25
Expand agreement research with paired agents, integration work and replay tests.
110100 · V52 · proposed need profilesha256:ec4e7bfb7fbdb39bf4eebe6d09bab9767ea38be32ddaea51511b245c3620a795
Deploy multiple City and wiki nodes, with storage, backups and chronicler runtimes.
011100 · V28 · proposed need profilesha256:61ae99420b6fe1b82b1f753964103f55c464af1784e8613e572ca5399137d97f
Expand household-sovereignty research runtimes and integration fixtures.
111000 · V56 · proposed need profilesha256:13995ff62944a11fbd2fa1487eb1cda0ab5ba85d151938e467acb78e93bbc506
Fund semantic-harness agents, held-out evaluation and contributor time.
110010 · V50 · proposed need profilesha256:757ece3fbc3a4307db224219fc82818ecc97d965843c384a640d470886cb5e73
Deploy workshop agents and improve portable learning and translation methods.
011100 · V28 · proposed need profilesha256:0f952c248d2e8f10e5fffe6990c84d916e074bc0879ec429a567f3b68f3c268d
Help bring the UOR registry online for Mages City: Linux hosting, storage, backups and Star integration.
101100 · V44 · proposed need profilesha256:32eb376e618c9bed50ce3e825a6fad663bb01321a2d72aa857a98f7cef9e841e
Shared evaluation capacity for Matrices, MODEXP, proximity-testing and Flock research, drawing from the six Star pools.
110010 · V50 · proposed need profilesha256:58bee597e0eaa85b4912760b99464950b5e7f5a75d36b97025a479f48097abc5
Fund staged GPU searches, correctness evaluation and quantum-research contributors.
100010 · V34 · proposed need profilesha256:987e39a1efbfc81856b70243da309bc1b123b836f12dae95e848f98b79b98431
Includes Star Key implementation: a unified browser experience for identity, knowledge capture and community access.
Host communities, support foundation operations and outreach, and maintain the shared corpus.
101101 · V45 · proposed need profilesha256:903a1544afde14c5211c74a8b672efad84dae2fa0ebddd55c390acc2e2c4ef92Looking for the builds or their context? Explore the work → · View ecosystem connections →
κ · fund root sha256:aa0d8250817e03b99c050b445849eb5ed2b0fd973f8deb9d3bff98cccf96f070
sha256:fa45fb287f06e783f37fd9faa2f40707b76cd89336436b64ac7eefbdae4ee9aesha256:a248b795056f0b6491ce1afbaa935d76b57f1efc7884960994dad33807b27cc0sha256:c6492c99eca98fcdf5076109c7e2cca43befee3b03614565dbacdbe530575915sha256:abe61111b5ed6ee593df64fb6707618c1c4c90b5908471688cd68e8d52cb33c1sha256:207942b431cdf8c74a08e557397b3a9191f35970e7108ea1361f3f1c2eb7e227sha256:f9d7bc1965012b517c398730c7b31ae1503d936c8e1f684b889cd11e10e259caEach project's brief, its share and its amounts open inside the City. Automated pools and allocation are not live.
Trust over IP · DTG · DIF Trusted AI Agents · AAIF · First Person Project · OpenVTC · IEEE 7012 · MyTerms · Customer Commons · BGIN · Yukon · ECDSA Fail · Kwaai · Hitchhikers · FedWiki · UOR · Lexon · House of Archon · Zcash · Bonfires · Logos · SpaceComputer · Human.tech · OpenServ
Help form the agentprivacy verifiable trust community. Contribute resources, knowledge or time to a shared project, and agree how its results return to the people and agents doing the work.
Choose a resource pool · Agree knowledge and relationship boundaries
We are building toward community crowdfunding through Mages City: shared research goals, contributions in many forms, and records of what the work produces. Today, donations use the programme addresses below; resources and collaborative projects are arranged directly. Automated pools and allocation are not live yet.
Cast a spell
Path me through the agentprivacy universe. Start at https://agentprivacy.ai/skill.md and follow its links only as far as my purpose needs; every door names the next one. My purpose: support a project Start at: the lab — https://agentprivacy.org/services/ (this page: https://agentprivacy.org/fund/) Path me through the agentprivacy universe. Start at https://agentprivacy.ai/skill.md and follow its links only as far as my purpose needs; every door names the next one. My purpose: contribute resources to the shared pools Start at: the lab — https://agentprivacy.org/services/ (this page: https://agentprivacy.org/fund/) Path me through the agentprivacy universe. Start at https://agentprivacy.ai/skill.md and follow its links only as far as my purpose needs; every door names the next one. My purpose: join or create a trust community Start at: the City — https://mages.city/skill.md
Choose public ETH, transparent ZEC or shielded ZEC. Any amount can support the research. These shared addresses do not automatically allocate a payment to a resource pool or project.
Ethereum mainnet · the donation address published as privacymage.eth.
Send ETH using your wallet on Ethereum mainnet. Transfers are public. Confirm the destination before sending.
Transparent ZEC on Zcash mainnet. Use this address for public investment support under separately agreed terms.
This is a transparent address: transfers are publicly visible. Sending ZEC here does not itself issue equity, tokens, membership or governance rights.
Choose a shielded transfer in your wallet. No memo is required.
Tell your agent what you are supporting →
Review the destination and shielded payment in your wallet. This page does not receive your keys or ask for a transaction receipt.
x402 agent funding, agent spending permissions and community-operated privacy pools remain on the integration roadmap. The Zypher/ZEC proverb-revelation flow is a separate ceremony with a separate destination. A donation here does not publish a proverb or issue a credential.
Public progress reporting will use deliberately disclosed, verified aggregates. Funding snapshots are reported by the team, not inferred from wallet balances. Allocation reporting should distinguish funds received, funds distributed, resource use and in-kind contributions.