> For the complete documentation index, see [llms.txt](https://docs.nearby.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nearby.finance/use-cases/emergency-coordination.md). # Emergency Coordination ## Emergency Coordination Emergency situations expose the fragility of traditional digital infrastructure. During natural disasters, power outages, infrastructure failures or network disruptions, people may lose access to the communication and payment systems they rely on every day. Nearby Protocol is designed to support coordination when connectivity cannot be assumed. By combining **Proof of Location**, **Nearby Mesh** and **OfflinePay**, Nearby enables communities to communicate, verify presence and exchange value during disconnected or partially connected conditions. > **Nearby helps communities coordinate when traditional infrastructure becomes unreliable, unavailable or overloaded.** *** ### The Challenge Emergency environments are unpredictable. Connectivity may be weak, intermittent or completely unavailable. Critical systems can fail at the exact moment they are needed most. Common emergency conditions include: * Power outages * Damaged communication infrastructure * Natural disasters * Network congestion * Restricted connectivity * Remote rescue environments * Temporary isolation of communities * Disrupted payment services Most digital tools are built for normal connectivity. Emergency coordination requires systems that can continue operating under degraded conditions. *** ### Why Traditional Systems Fail Many modern applications depend on centralized infrastructure. Messaging platforms require internet access. Payment systems require online authorization. Location services often depend on centralized servers. Emergency applications may fail if network access is unavailable. This creates a fragile model. When connectivity fails, users may lose access to: * Local communication * Community coordination * Emergency updates * Digital payments * Location-based assistance * Resource distribution tools Nearby introduces a local-first model that can continue functioning when global connectivity is unavailable. *** ### How Nearby Helps Nearby Protocol provides three core capabilities for emergency coordination: | Layer | Role in Emergency Coordination | | --------------------- | ------------------------------------------------------------------------------------------------------- | | **Proof of Location** | Verifies presence in affected zones, safe areas or response regions without exposing exact coordinates. | | **Nearby Mesh** | Enables local peer-to-peer communication when internet or mobile networks are unavailable. | | **OfflinePay** | Allows local value transfer and emergency payments without real-time connectivity. | *** ### Proof of Location Proof of Location allows users to prove they are present within a specific area without exposing exact coordinates. In emergency scenarios, this can support: * Presence verification in affected zones * Eligibility for local assistance * Resource distribution validation * Emergency response coordination * Proof of arrival at safe zones * Volunteer or responder verification Users can prove a location-related fact without broadcasting sensitive movement data. This allows emergency applications to verify presence while preserving user privacy. *** ### Nearby Mesh Nearby Mesh enables local peer-to-peer communication between nearby devices. This is critical when internet access or mobile networks are unavailable, congested or unstable. Nearby Mesh can support: * Local emergency alerts * Community status updates * Peer-to-peer messaging * Rescue coordination * Temporary local communication groups * Information relay across nearby devices Each participating device can help relay messages through the local network. This allows information to continue moving locally, even when centralized infrastructure is disrupted. *** ### OfflinePay OfflinePay enables value transfer without requiring real-time internet connectivity. During emergencies, this can support: * Local purchases * Aid distribution * Peer-to-peer assistance * Emergency commerce * Offline stablecoin transfers * Settlement after connectivity returns OfflinePay allows economic activity to continue even when online payment rails are unavailable. Transactions can happen locally and be reconciled on-chain once connectivity is restored. *** ### Example Emergency Flow A local area experiences a major outage. 1. Users enter a Nearby emergency mesh network formed around the affected area. 2. Devices discover nearby peers and begin relaying local messages. 3. Residents share updates, needs and available resources. 4. Volunteers generate Proof of Location to confirm presence within the response zone. 5. Local transactions are performed using OfflinePay. 6. Once connectivity returns, payment histories and attestations are reconciled on-chain. This creates a local coordination layer that can operate independently of centralized infrastructure. **Complete flow:** ``` Outage occurs → Local mesh forms → Presence is verified → Resources move → Settlement happens later ``` *** ### Emergency Communication Nearby Mesh can help communities maintain communication in disconnected conditions. Potential communication flows include: * Person-to-person updates * Neighborhood-level alerts * Volunteer coordination * Resource availability messages * Medical or supply requests * Evacuation instructions * Local status broadcasts Because communication is local-first, users do not need to depend entirely on external infrastructure. This makes Nearby useful in environments where communication must continue even when traditional networks fail. *** ### Resource Distribution Proof of Location can help verify that a person is within a specific area before receiving access to assistance or local services. This can support: * Distribution of food, water or supplies * Location-based aid eligibility * Volunteer check-ins * Local shelter access * Emergency zone verification * Proof of presence for support programs Nearby reduces the need to collect exact user location while still allowing location-based verification. This creates a better balance between operational trust and personal privacy. *** ### Offline Economic Activity In emergencies, access to banking and digital payments may be disrupted. OfflinePay enables local value exchange using cryptographically secured payment notes. This can be useful for: * Buying essential goods * Paying local vendors * Peer-to-peer support * Community aid transfers * Temporary offline markets * Local settlement after reconnection Transactions can happen locally and be finalized later. This helps preserve economic continuity when traditional payment systems are unavailable. *** ### Privacy Considerations Emergency systems should not become surveillance systems. Nearby is designed to minimize unnecessary data exposure. Users can prove they are within a relevant area without revealing exact coordinates or full movement history. This is especially important in sensitive situations where location data could expose vulnerable people, responders or affected communities. Nearby supports coordination while preserving user control over location information. *** ### Potential Applications Nearby can support emergency use cases such as: * Disaster response coordination * Power outage communication * Community safety networks * Emergency resource distribution * Volunteer coordination * Local aid payments * Remote rescue environments * Temporary communication networks The protocol is designed for environments where resilience matters more than perfect connectivity. *** ### Summary Emergency coordination requires systems that continue working when traditional infrastructure fails. Nearby Protocol enables local communication, privacy-preserving location verification and offline value transfer during disconnected or partially connected conditions. By operating across the full spectrum of connectivity, Nearby helps communities coordinate when they need it most. **Nearby turns emergency environments into resilient local coordination networks.** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.nearby.finance/use-cases/emergency-coordination.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.