Ahmedabad is home to over 100,000 bovines — cows who share roads, markets, and neighbourhoods with 8 million human residents, grazing along roadways, sheltering beneath highway flyovers, and cycling through a network of gaushalas (cowsheds) that operate as informal welfare infrastructure across the city. Their presence is active, spatial and political.
This cohabitation is shaped by deep contradiction. The cow occupies a singular position in Indian politics: simultaneously sacred and abandoned, protected by law and neglected by policy. Gujarat's anti-slaughter legislation, among the strictest in the country, criminalises harm to bovines while providing no corresponding framework for their urban care. The result is a city where thousands of unregistered animals depend entirely on decentralised, community-led networks of feeding, sheltering and healing. This is labour that is largely invisible, uncompensated, and carried out disproportionately by women, as well as Dalits and Muslim communities.
CattleDAO is a speculative design project that asks what would it mean to build civic infrastructure around multispecies care. It proposes a decentralised autonomous organisation (DAO), a blockchain-governed commons, in which the everyday acts of tending to urban cattle (feeding, watering, sheltering, veterinary response) become the basis of civic participation. Care Credits, the system's non-transferable reputation tokens, are earned through verified acts of care and accumulate into governance rights. The cowsheds themselves are reimagined as solar micro-grids whose energy production funds the computational cost of maintaining the shared ledger.
The interface you are about to see is a working prototype of this proposal. The map, the ledger, and the care protocols presented here are drawn from real gaushala locations, real herd distributions, and real patterns of informal care across Ahmedabad, as a design fiction grounded in the real. This project is an invitation to imagine urban governance that begins not with property or citizenship, but with relation.
Each role reflects a real form of care labour already practised informally across Ahmedabad. Your role determines your starting position in the system — but all roles earn Care Credits equally, and governance rights are accumulated through action, not title.
| WITNESS | A general civilian entering the network. You observe, report, and claim care tasks as they arise. Most residents of Ahmedabad begin here — encountering cows daily without a formalised care role. |
| KINKEEPER | A verified, consistent caregiver — someone who feeds, waters, or shelters bovines as part of a daily routine. Kinkeepers represent the backbone of informal care: the woman who brings rotla to the same three cows each morning, the gaushala worker who knows every animal by name. |
| PROVISIONER | A local vendor or supplier who contributes material resources — fodder, water, medical supplies — to the care network. Vegetable sellers who set aside scraps, dairy operators who maintain feed stocks, or shopkeepers who leave water outside. |
| HEALER | A medical professional — veterinarian, paravet, or traditional practitioner — who can assess injuries, administer treatment, and escalate cases to emergency care. Their expertise is the rarest and most urgent resource in the network. |
| SENSOR | A field observer or telemetry node — someone who surveys herd locations, monitors gaushala conditions, or maintains RFID/solar infrastructure. Auto-rickshaw drivers, municipal workers, and delivery riders whose daily routes cross bovine territories are ideal sensors. |
All identities currently synced to the Ahmedabad Node, ordered by Care Credits earned.
CARE CREDITS (CC) are the native reputation token of the CattleDAO network. They are not a currency, and cannot be traded, transferred, or sold. They are a proof-of-relation record, minted immutably to your identity each time you complete a verified care act on behalf of a registered bovine in the Ahmedabad Node. They mark your entanglement with the multispecies fabric of this city. Your rank reflects your lifetime accumulation of care.
When you join CattleDAO you declare a Node Class — WITNESS, KINKEEPER, PROVISIONER, HEALER, or SENSOR. This is a functional role: it describes what kind of care infrastructure you are willing to provide and shapes the protocols you are most likely to claim. Node Classes are self-declared, mutable, and carry no intrinsic authority.
Care Credits, by contrast, are earned exclusively through action. They are the ledger's memory of what you have actually done. CC cannot be purchased, delegated, or inherited. The rank tiers that CC unlock (WITNESS → COMPANION → KINKEEPER → SANCTUARY_WEAVER) are orthogonal to Node Class: a SENSOR node who consistently logs water-trough data will ascend to governance standing regardless of title.
Every verified care act, from distributing fodder, relaying a healer assessment, to clearing a traffic blockage, generates a confirmed block on the local ledger. Each block awards between +8 and +32 CC depending on the urgency and complexity of the protocol. The system does not distinguish between role classes: a Witness and a Healer earn equal CC for the same act of care. Presence and relation are the only currencies that count.
At 500 CC, your identity is elevated to KINKEEPER status within the DAO, as a threshold that emerges from embodied, place-based care rather than abstracted ownership. This unlocks the right to submit formal proposals, vote on resource allocations, and ratify changes to care protocols. Once reached, this standing is permanent: rank is determined by the cumulative record of what you have done. Power here is not purchasable and accumulated by one act of tending at a time.
Kinkeepers may vote on: designation of new gaushala territories; reallocation of communal feeding station resources; onboarding of new field sensors; escalation of a bovine to emergency care status; and amendments to the care protocol taxonomy. Proposals require a minimum quorum of 12 Kinkeepers and pass by simple majority. All decisions are recorded on the shared ledger and remain permanently auditable by any Witness.
Thresholds are measured against lifetime earned CC. Once a tier is reached it is held permanently.
| LIFETIME CC | RANK | STANDING |
| 0 – 49 CC | WITNESS | Enters the network. Can view, propose, and claim care tasks. |
| 50 – 499 CC | COMPANION | Recognised presence within at least one gaushala territory. |
| 500 – 1999 CC | KINKEEPER | Full governance rights. DAO proposal and voting unlocked. |
| 2000 + CC | SANCTUARY_WEAVER | Proposal veto. Mentorship of incoming Witnesses. Herd stewardship rights. |
CattleDAO is designed for deployment on a proof-of-stake (PoS) chain. The computational cost of recording a care act should be commensurate with the act itself: negligible in energy, permanent in consequence. A single Ethereum L2 transaction on a rollup like Base, Arbitrum, or Optimism currently costs 0.001 kWh.
The core contracts are minimal by intent. A CareRegistry contract stores bovine identity hashes and gaushala node addresses. A CareLedger contract records each verified care act as an immutable event log (subject, protocol, contributor, timestamp) and mints a non-transferable Soulbound CC token to the contributor's wallet. A GovernanceGate contract reads a wallet's lifetime CC balance and gates proposal submission and voting behind the 500 CC threshold. This does not require token swap, a liquidity pool, nor a speculative surface.
Verification of care acts is the hardest layer — and the one most easily corrupted by the logic of policing. CattleDAO deliberately avoids a verifier-judge model. There is no inspector, no approval queue, no human gatekeeper who adjudicates whether your care was "real enough." Instead, the system composes lightweight, layered evidence that makes fabrication socially costly without making honest care bureaucratically burdensome.
The primary proof layer is a photo or short video, uploaded at the moment of care. This is a relational receipt: a photo of Tara eating rotla near Ellis Bridge; a six-second video of a filled water trough. This media is hashed and pinned to IPFS; the hash is recorded on-chain alongside the care event. They serve three purposes simultaneously: (1) they anchor the care act in space and time, (2) they build a communal visual archive of the herd — a living record that belongs to the network, not to any authority — and (3) they make the ledger legible to non-technical community members who can scroll through and see what care looks like.
The secondary layer is machine attestation. Where available, a nearby SENSOR node — an RFID gate at a gaushala entrance, or a GPS-fenced check-in — co-signs the care event automatically. On-chain, this maps to a two-of-three multisig: the steward's upload, the SENSOR attestation, and optionally a second steward's confirmation. If two of three sign, the block is finalized and CC are minted. Critically, a photo alone is sufficient where no SENSOR is present — the system trusts the community first and instruments second. If someone uploads a false proof, the community board is where that conversation happens: socially, not punitively. The incentive to fabricate is low (CC are non-transferable reputation, not currency), and the social cost in a place-based network is high.
What you are using now is a design simulation — a fully client-side interface that models the governance logic, ledger mechanics, and community interaction patterns of the proposed CattleDAO network. No blockchain is running beneath it. The data is procedural, the blocks are fictional, and your CC exist only in the browser's memory. This is intentional: the simulation is a legibility tool, allowing stewards, policymakers, and community members to experience the proposed system before any infrastructure cost is incurred.
The path from this simulation to a live on-chain deployment follows a sequence of concrete milestones:
| PHASE | DESCRIPTION |
| 01 // TESTNET | Deploy CareRegistry + CareLedger + Soulbound CC contracts to an L2 testnet (Base Sepolia or Arbitrum Goerli). Connect this interface to the contracts via ethers.js. Replace procedural data with live on-chain reads. Wallet login replaces the current role-selection modal. |
| 02 // SENSOR | Install RFID reader nodes at 2–3 pilot gaushalas. Each reader is a lightweight IoT device (ESP32 or Raspberry Pi) that signs a GPS-stamped attestation when a tagged bovine passes its gate. These attestations serve as one leg of the two-of-three multisig for care verification. |
| 03 // PILOT | Onboard 20–40 stewards across 3 gaushalas for a 90-day pilot. Stewards use this interface on mobile to propose, claim, and verify care tasks. CC are minted on-chain. Governance proposals are not yet active — this phase tests the care-act pipeline and attestation reliability. |
| 04 // GOVERN | Activate the GovernanceGate contract. Stewards who have crossed 500 CC during the pilot can now submit and vote on proposals. First governance cycle: vote on whether to expand the pilot to additional gaushalas, and whether to modify CC reward weightings. |
| 05 // MAINNET | Migrate contracts to L2 mainnet. Integrate with municipal cattle census data (Ahmedabad Municipal Corporation). Open federation protocol so other cities can deploy their own CattleDAO Node, sharing the contract standard but maintaining local governance autonomy. |
This system is a speculative civic prototype for the Ahmedabad Node, imagining infrastructure for multispecies urban cohabitation. Care Credits are simulated. All data is illustrative of a proposed framework for community-managed bovine welfare — a design fiction grounded in the real. The smart contract architecture described above is technically viable today; what remains is the social infrastructure to sustain it.