data centers don't have to eat the farm.

cassville, Wisconsin. population 951. a developer proposed a billion-dollar data center. 50 jobs. $5.5 million in annual property tax revenue. by any economic development formula, this should have been a slam dunk.

the vote was 44-0. against.

not 44-0 in a room full of environmentalists. 44-0 in a rural farming community that could have used the money. they looked at the proposal, looked at their fields, and said no.

that vote wasn't about water or noise or energy. it was about identity.

what the money can't buy

economic development departments run the numbers: tax revenue, construction spending, permanent jobs, multiplier effects. and the numbers for data centers often look good on paper — especially the property tax line.

but communities don't live on spreadsheets. they live in places. and when a 500-acre industrial facility replaces the farmland that defines who they are, no amount of tax revenue compensates for the loss.

the pattern repeats:

• kent county, michigan — Solon Township unanimously approved a six-month moratorium on data center proposals. residents cited loss of agricultural land and rural character.
• san marcos, texas — city council denied a map amendment to block data center development. hundreds of residents gathered to protest.
• montour county, pennsylvania — commissioners denied Talen Energy's rezoning after months of community opposition.
• across michigan — at least 19 communities have passed or proposed data center moratoria.

the common thread isn't anti-business sentiment. it's a community saying: "this changes who we are, and nobody asked us."

the ratio problem

data centers have a fundamental problem that no PR strategy solves: the footprint-to-employment ratio is terrible.

:::stat 100–500+ acres | large data center campuses 50-150 | permanent operational jobs 44-0 | cassville ban vote despite $5.5M/yr tax revenue | warning :::

a manufacturing plant on the same acreage might employ 500-2,000 people. a distribution center, 300-800. even a solar farm creates more construction jobs per acre.

communities look at the math:

• massive building, few jobs
• prime agricultural land consumed permanently
• tax incentives often reduce the revenue to a fraction of the headline number
• the jobs that exist require specialized skills most locals don't have

the economic argument doesn't pencil. so the question becomes: what else are you bringing?

the identity frame

rural communities have identity rooted in land. farming isn't just an economic activity — it's a way of life, a connection to place, a multi-generational story. when a data center proposal arrives, people don't just calculate tax revenue. they ask:

• will my grandkids grow up seeing fields or server halls?
• will this still feel like home?
• are we becoming a suburb of someone else's economy?
• who benefits — us, or a company that could put this anywhere?

these aren't irrational concerns. they're the concerns of people who understand something that spreadsheets don't capture: the value of a place is not reducible to its property tax yield.

this isn't a new insight. USDA's Agricultural Conservation Easement Program (ACEP), American Farmland Trust, state Purchase of Development Rights (PDR) programs, and thousands of local land trusts have been protecting working farmland for decades — often funded by developer impact fees or public bond measures. the infrastructure for farmland preservation exists and works.

what it lacks is composability. a conservation easement protects one parcel. it doesn't simultaneously fund the watershed that irrigates it, track soil health on the preserved land, or create transparent, enforceable commitments visible to the community before construction begins. ensurance adds a layer: the ability to bundle farmland protection with watershed health, soil programs, and food system resilience into a single, onchain commitment — permanent, auditable, and composable with existing land trust infrastructure.

what if the project protected more than it consumed?

instead of "this project takes 500 acres of farmland," what if the pitch were:

"this project permanently protects 5,000 acres of working farmland."

a 10:1 protection ratio. for every acre developed, ten acres of surrounding farmland are placed under permanent conservation easement — funded by the data center developer through ensurance instruments.

the instruments are live on Base L2. the first end-to-end deployment — from certificate to funded conservation easement — is the next step. here's how it's designed to work:

how it works

1. data center developer holds ensurance certificates on rural-open-space.ensurance, healthy-soils.ensurance, and food.ensurance agents
2. certificate proceeds fund conservation easements on working farmland in the surrounding area — permanent, legally binding restrictions that prevent development while keeping the land in agricultural production
3. additional certificates on .basin agents fund watershed protection that benefits the preserved farmland — irrigation water quality, soil health, flood management
4. the protection ratio is built into the community benefits agreement — enforceable, transparent, onchain

a qualified land trust holds each conservation easement; ensurance certificates fund the acquisition and track compliance onchain.

what the community gets

the community doesn't lose farmland on net. it gains permanent protection for land that was previously vulnerable to any future development pressure — not just data centers.

the instruments

what econ dev departments can require

economic development departments have more leverage than they think. data center developers need land, water, grid access, and permits — all controlled locally. instead of accepting or rejecting proposals, econ dev can set the terms:

a farmland protection framework

1. protection ratio — require a minimum ratio of permanently protected acres per developed acre (10:1 is a strong starting point)
2. conservation easement funding — developer deposits easement acquisition funds before construction begins, held in an ensurance syndicate
3. working lands requirement — protected farmland stays in active agricultural production (not just vacant open space)
4. soil health standards — preserved land includes funded soil health programs (cover crops, no-till, rotational grazing)
5. transparency — all protection commitments, fund flows, and easement status reported onchain through ensurance certificates
6. permanence — conservation easements are perpetual, not term-limited

this framework doesn't say "no" to data centers. it says "yes, and here's what comes with it." communities that adopt this framework get something more valuable than tax revenue — they get permanent protection for the land that defines them.

the deeper point

the cassville vote wasn't a failure of economic development. it was a success of community values. 44 people looked at a billion-dollar proposal and decided their farmland was worth more.

they were right. farmland IS worth more — not just sentimentally, but in ecosystem service terms. working agricultural land provides food production, soil carbon sequestration, water filtration, pollinator habitat, flood storage, and cultural continuity. these services have real economic value that conventional appraisals don't capture.

ensurance is built to recognize that value and fund its protection. the next proposal doesn't have to repeat cassville. it can arrive with a protection ratio, funded easements, and a transparent commitment the community can verify before a single acre is graded. the question is which developer uses them first.

see how ensurance works for data centers →