City to City

City Chains can coordinate and transact with each other through Locale Network, which serves as the coordination layer for all L3 chains. This enables commerce, data sharing, and governance coordination while preserving the local autonomy that makes each City Chain unique.

Locale Network as Coordination Layer

Architecture Overview

City-to-City Coordination

City A

Kansas City

Cross-chain
messaging

City B

St. Louis

Asset Transfers

Bridge stablecoins

Data Sharing

Aggregate insights

Commerce

Cross-city trade

Coordination Services

Service	Function	Benefit
Messaging Protocol	Routes messages between City Chains	Reliable cross-city communication
Routing Layer	Optimizes transaction paths	Efficient multi-hop transfers
Settlement Layer	Finalizes cross-city transactions	Dispute resolution
Registry Services	City Chain discovery and metadata	Easy integration
Standards Library	Shared protocols and interfaces	Interoperability

Economic Benefits

Commerce That Preserves Localism

City-to-city coordination enables regional commerce while keeping economic value local:

Benefit	How It Works
Local First	Transactions settle in local stablecoins
Regional Trade	Cross-city commerce with fair exchange
Value Retention	Treasury fees stay with originating city
Fair Pricing	Transparent exchange rates

Cross-City Commerce

Cross-City Commerce Flow

Buyer (City A)

Pays with local coin

Bridge Protocol

Atomic swap

Seller (City B)

Receives local coin

Both parties stay in their local currency

Economic Flows

Transaction Type	Flow	Settlement
Direct Purchase	Buyer → Seller	Stablecoin swap on L2
Service Payment	Consumer → Provider	Routed via Locale Network
Data Licensing	Consumer → Producer	Micropayment channels
Treasury Transfer	City A → City B	Governance-approved

Data Sharing

Cross-City Data Exchange

City Chains can share verified data through L{CORE} attestations:

Data Type	Use Case	Privacy Model
Environmental	Regional air quality monitoring	Aggregated, anonymized
Traffic	Cross-city transit optimization	Real-time, anonymized
Economic	Regional economic indicators	Aggregated statistics
Public Health	Disease surveillance	Privacy-preserving

Data Marketplace

Cross-City Data Marketplace

DATA MARKETPLACE

Data Providers

• IoT sensors
• Business data
• User data (permissioned)

Data Consumers

• Analytics platforms
• Research institutions
• Other cities

Privacy-Preserving Exchange

Aggregate data, zero-knowledge proofs, consent management

Governance Coordination

Multi-City Decisions

Some decisions benefit from cross-city coordination:

Decision Type	Coordination Level	Example
Standards	Network-wide	Data format specifications
Protocols	Multi-city	Shared messaging protocols
Economic	Regional	Trade agreement terms
Technical	Network-wide	Infrastructure upgrades

Coordination Mechanisms

Mechanism	Description
Signaling	Cities express preferences without binding commitment
Soft Consensus	Majority agreement on non-critical changes
Hard Consensus	Supermajority required for protocol changes
Opt-In	Cities choose whether to adopt standards

Use Cases

Regional Tourism

Tourists can use their home city's stablecoin across the region:

1. Visitor arrives with home city stablecoin (e.g., KCD)
2. Pays locally — merchants accept any regional stablecoin
3. Automatic swap — Locale Network handles conversion
4. Merchant receives local currency (e.g., AUSD)

Supply Chain Coordination

Businesses operating across cities benefit from:

• Single identity — L{CORE} credentials work across cities
• Unified payments — Pay suppliers in their preferred currency
• Transparent tracking — Cross-city shipment verification
• Automated settlement — Smart contract escrow

Emergency Response

During regional emergencies:

• Resource sharing — Cities can request and offer resources
• Credential portability — Emergency workers verified across cities
• Data sharing — Real-time situational awareness
• Coordinated response — Multi-city action plans

Academic and Research

Universities and research institutions can:

• Share datasets — Cross-city research collaboration
• Pool resources — Shared compute and infrastructure
• Credential recognition — Student/researcher verification
• Grant coordination — Multi-city funding applications

Technical Implementation

Message Routing

Step	Action	Layer
1	Origin City Chain sends message	L3
2	Message arrives at Locale Network	L2
3	Router identifies destination	L2
4	Message queued for destination	L2
5	Destination City Chain receives	L3

Settlement Process

Step	Action	Finality
1	Transaction initiated on source L3	Local
2	Funds locked/burned on source	L3 confirmed
3	Proof submitted to L2	L2 confirmed
4	Funds minted on destination L3	L3 confirmed
5	Final settlement on L1	Full finality

Integration Guide

For City Chain Operators

1. Register — Add your City Chain to the Locale Network registry
2. Configure — Set up routing and settlement preferences
3. Test — Validate cross-city transactions on testnet
4. Launch — Enable production cross-city features

For Developers

1. SDK Integration — Use Locale SDK for cross-city calls
2. Message Formatting — Follow standard message schemas
3. Error Handling — Implement timeout and retry logic
4. Monitoring — Track cross-city transaction status

Learn More

• Cross-Chain Messaging — Technical messaging details
• Bridging Assets — Asset transfer mechanics
• Local Currency — Stablecoin economics
• Data Sovereignty — Data sharing principles