# The Excelsior Springs Citizen Network **A sovereign-identity civic infrastructure layer for small-city deployment** --- ## The Bet Every municipal "smart city" program in the last decade has been a top-down surveillance upgrade wrapped in civic branding. Citizens get new sensors. The city gets new data. The relationship doesn't change. The Citizen Network flips the direction. Residents get a sovereign identity wallet, own their credentials, and earn local currency for civic participation. The city gets a population that engages because the system pays them to — and a privacy-preserving data layer it can monetize ethically. The architecture was designed for a specific deployment target: Excelsior Springs, Missouri, population ~12,000, with municipal characteristics that make it tractable to pilot and compelling to generalize from. --- ## Architecture Five layers. Each maps to an existing problem in municipal operations. | Layer | Function | Primitive | |---|---|---| | **1. Identity** | Every resident holds a Decentralized Identifier (DID) and a wallet of Verifiable Credentials (VCs) issued by the city. | W3C DID/VC standards; self-custody wallet | | **2. Incentive** | Residents earn **Excelsior Springs Credit (ESC)** — a USD-pegged stablecoin — for verified civic actions. Redeemable for utility bills, local retail, permits. | Smart-contract issuance against verified actions | | **3. Integration** | DID + VC replace login, attestation, and payment surfaces across municipal and partner services — permitting, library, utilities, local commerce. | VC-gated access; wallet-native payments | | **4. IoT Trust** | Every sensor in the civic network has its own DID. Data is signed at source. Residents can host sensors and earn ESC. | Device identity; provenance-signed telemetry | | **5. Data Dividend** | Aggregated civic data is monetized through a Civic Data Trust using zero-knowledge proofs. Revenue returns to residents as a dividend. | ZKP aggregation; Civic Data Trust 501(c)(3) | The layers are designed to compose. The wallet from Layer 1 is the surface for every other layer. The token from Layer 2 is what the IoT trust layer pays out. The Data Trust from Layer 5 is what governs the token. Nothing in this stack is a bolt-on. --- ## Tokenomics ### Table 2: Excelsior Springs Credit (ESC) Framework | Parameter | Description | Rule | Governance | |---|---|---|---| | Ticker | ESC | N/A | Data Trust DAO | | Type | Stablecoin, pegged 1:1 to USD | $1.00 USD | Peg maintained by City Reserve Fund | | Supply | Elastic; minted against verified civic action | Smart-contract logic | Data Trust DAO | | Earn — IoT sensor hosting | Monthly rental | 5 ESC / month | DAO | | Earn — Verified recycling | Weekly | 1 ESC / week | DAO | | Earn — Voting in municipal election | Per election | 10 ESC | DAO | | Earn — Shop Local cashback | At partner merchants | 5% of purchase | DAO | | Redeem | Utility bills, local retail, property taxes, permits | Partners approved by Trust | DAO | --- ## Deployment ### Table 1: Phased Roadmap & Budget | Phase | Year | Activities | Budget | KPIs | |---|---|---|---|---| | **1. Foundation & Pilot** | 1 | Charter 501(c)(3) Data Trust. Launch wallet MVP. Onboard 20–30 businesses and 500–1,000 citizen testers. Run "Shop Local & Earn ESC" pilot. | $1.5M–$2.5M | Wallet adoption >60% of pilot group. NPS >50. Pilot evaluation completed. | | **2. Expansion & Integration** | 2–3 | Scale retail city-wide. Utility bill payments in ESC. Issue additional VCs (library, permits). IoT air-quality sensor pilot. Launch DAO governance portal. | $3M–$5M / yr | >25% residents active. >10% utility payments in ESC. 100+ IoT sensors deployed. | | **3. Maturity & Monetization** | 4–5 | Digital voting pilot. ZKP anonymization layer live. Data marketplace API. First data dividend distributed. | $2M–$4M / yr | >$500K annual data revenue. Dividend to >50% of residents. Operations break-even on program revenue. | --- ## Funding Capital comes from four sources in parallel: federal smart-city and digital-equity grants, state-level economic development funding, the municipal capital improvements budget (infrastructure-classified), and private-sector P3 partnerships for technology development. Modeling shows the program reaches operational break-even in Phase 3 on data dividend revenue, moving the Data Trust off municipal subsidy. Full cost-benefit analysis lives in working documents. --- ## Governance The Civic Data Trust is a 501(c)(3) non-profit that holds the data infrastructure, manages the token economy, and distributes revenue. Its board is composed to balance citizen, municipal, business, and expert interests — and designed to survive political turnover without losing institutional memory. ### Table 3: Civic Data Trust Governance Model | Stakeholder | Seats | Role | Selection | |---|---|---|---| | Citizen Representatives | 3 | Resident advocacy; transparency | Elected biennially via DID wallet | | Municipal Appointees | 2 | Policy alignment | City Manager's Office | | Local Business Representatives | 1 | Economic development input | Chamber of Commerce nomination | | Independent Experts | 2 | Data ethics, privacy law, cybersecurity audit | Board-appointed, non-affiliated | | Trust Management Team | Non-voting | Day-to-day operations | Hired by and reports to Board | --- ## Regulatory & Ethics The framework was designed against the real compliance surface a small US city actually faces: state and federal data protection law (including CCPA/CPRA-adjacent principles most states now track), 501(c)(3) fiduciary duties, and the patchwork of municipal procurement rules that gate public-private partnerships. The Data Trust structure is explicitly chosen to insulate the data infrastructure from political turnover while keeping the municipality accountable for what gets issued on its behalf. Transparency practices — public audit cadence, published smart-contract code, community town halls — aren't decorative; they're how the Trust retains social license to operate. --- ## Why This Is Build-Ready Architecture is locked. Economics are modeled. Governance is chosen. Pilot scope is sized and priced. Excelsior Springs was selected because its population and institutional density make the pilot tractable — not because the framework is Excelsior-specific. Everything in this document generalizes to the long tail of US towns in the 5,000–50,000 population band. The next step is a 12-month Phase 1 pilot against a signed memorandum with the city.