NextTrend Hub, Lagos: Agriculture Sector

By the time a reader arrives here, the paper has established that Prisma organises events that produce real value, and that this value now has a protocol to represent it. AgriDatum is a case study in how that protocol takes shape from the ground up, beginning not with a product, but with a question asked of a farming community in southern Nigeria.

Context

Wada, as the principal network coordinator for CATS, distributed funding across the hub network. NextTrend Hub, as one of the participating hubs, received that allocation and managed the teams operating under it during the hackathon programme. AgriDatum was one of those teams.

The Ground

The AgriDatum team conducted community research in farming communities in Akwa Ibom State, southern Nigeria. They did not arrive with a solution. They arrived to observe.

What they found was an agricultural system running on guesswork and informal trust. Farmers kept records in notebooks that were easily lost or left incomplete. Market prices shifted daily with no shared reference point. NGOs trying to support these communities were, in the words of one volunteer interviewed, operating blind, because no structured data existed to guide their decisions.

When the team asked farmers about digital tools, one responded:

“Why should I put my data where I don’t know who is using it?”

That was not reluctance to adopt technology. It was a rational response to a history of systems that took from communities without returning anything.

A younger farmer offered the other side of the same logic:

“If it connects us to markets or programs, I will enter it every day.”

Together, these two responses defined the design problem. The barrier was not access to technology. It was the absence of a system whose terms were legible and fair to the people being asked to participate.

The Problem as the Community Named It

• Surface symptom: farmers could not access loans, fair pricing, NGO support, or credible markets.
• Root dynamic: their economic activity was real and consistent, but invisible to every system that could have resourced it. The few systems that had tried to make it visible had done so on terms that served the systems, not the farmers.

The Currency Discovery Journey

First instinct

The team’s initial orientation was toward harvest data: crop type, quantity, location, date, recorded on-chain. The implicit metric was volume of data recorded.

Why it was insufficient

Optimising for data volume would have reproduced exactly the dynamic the farmer in Akwa Ibom was wary of. A system that grows by accumulating farmer data — without those farmers controlling what happens to it or receiving direct benefit — is not a trust system. NGOs and buyers would benefit from the data. Farmers would carry the cost of producing it.

The shift

The question that moved the conversation was: what would it mean for a farmer to be the one initiating the action, rather than being the subject of it?

A harvest record entered because a buyer required it is a different thing from a harvest record entered because the farmer chose to build their own verifiable track record. The first serves the system above. The second serves the farmer first, and the system as a consequence.

The proposed currency

Verified farmer-initiated transactions: actions the farmer chose to take, recorded on-chain, building a verifiable history of economic activity that the farmer owns and controls.

This currency is verifiable: each transaction is signed by the farmer’s own cryptographic key and recorded on Cardano. It is community-defined: participation is voluntary and the record belongs to the farmer. It is ecosystem-healthy: growth means more farmers are actively choosing to build their own economic identity, not that more data is being extracted from them. And it is aspirationally interoperable: a verified farmer track record could, in a mature version of Prisma’s protocol, travel to a credit platform, an NGO programme, or another hub context entirely. (See: Currency domain.)

The Three Levels of Nesting

Level 1: The Project

AgriDatum was building toward a condition where a smallholder farmer in Akwa Ibom could hold a verified record of their own economic activity, one no intermediary could alter, that they could present to a buyer, an NGO, or a lender on their own terms. The capacity being built was economic legibility on the farmer’s own terms.

Level 2: The Hub

NextTrend Hub’s support of AgriDatum, alongside its other teams, reveals something at a deeper level. The teams it hosted independently converged on the same root problem: invisibility as the condition of exclusion. This is not coincidence. It reflects the ecosystem NextTrend operates in and the quality of facilitation it provided during the action-learning process.

Level 3: The Hub-Network

A verified farmer identity built on AgriDatum does not have to stay within AgriDatum. In a mature version of Prisma’s protocol, a farmer with an on-chain record of honest harvest reporting could carry that trust profile across the network. AgriDatum’s currency, implemented at scale, would contribute a verifiable stream to the hub-network’s aggregate currency, $C_3$. (See: Currency domain.)

Governance and Trust

The most important governance observation from AgriDatum is also the simplest. The team went to the community before they built anything. The farmers they spoke to shaped the problem definition. The quote that anchored their design came from the ground, not from a product brief. That sequence, community first and technology second, is what the governance domain is concerned with protecting as a system scales. (See: Governance domain.)

At the individual level, AgriDatum made a deliberate choice: the farmer’s private key never leaves the device, personally identifiable information is stored separately from harvest records, and gas fees are sponsored by the platform so farmers do not need to hold ADA to participate. These choices kept ownership with the farmer during the hackathon period.

What was not yet demonstrated is how that ownership holds under pressure: when funding runs out, when a partner NGO requests broader data access, or when the platform operator changes. The governance framework exists precisely to protect individual ownership in those conditions, not just under normal ones.

At the institutional level, the case for trust is sound in design. An immutable on-chain record is verifiable by any institution independently, without needing to trust the platform operator. But this was not tested in a live funding relationship during the hackathon. The institutional trust proposition remains to be evidenced in practice.

At the narrative level, the community research was real and the farmers’ voices shaped the build. What remains open is whether the community in Akwa Ibom would recognise themselves in this account. That step, returning the story to the people it is about, is part of what the protocol must build into its process going forward.

What AgriDatum Makes Visible

Before AgriDatum, the economic activity of smallholder farmers in Akwa Ibom was real but unrecorded. Yields happened. Sales happened. Seasonal relationships between farmers and buyers were maintained across years. None of it was legible to any system that could have resourced it further.

AgriDatum did not create that activity. It created the conditions for it to be seen, on the farmers’ own terms.

The technology is not the innovation. The participatory process that defined what the technology should verify is the innovation.

What Remains Open

AgriDatum is not currently active. No pilot is running with live farmers. The currency has not been verified in a real economic exchange.

This does not diminish what the hackathon produced. It names what the next stage requires: sustained support to carry the team beyond the event, a pilot partnership with at least one farming cooperative in Akwa Ibom, and the governance conditions that would allow a farmer to trust the platform not just on day one but across years of changing conditions.

These are not technical problems. They are the conditions that Prisma’s protocol exists to create. (See: Business Model domain, on how pre-financing supports teams through the post-hackathon transition.)