> 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/the-connectivity-problem.md). # The Connectivity Problem ### A Connected World That Isn't Always Connected Modern digital services are built on a simple assumption: users are always online. Messaging applications, payment systems, location services and cloud-based platforms generally require continuous internet connectivity to function. While this assumption works in many environments, real-world conditions are often far more complex. Network access can be disrupted by technical failures, physical infrastructure damage, geographic limitations or temporary congestion. When connectivity becomes unavailable, critical services can become inaccessible within seconds. As society becomes increasingly dependent on digital infrastructure, resilience becomes just as important as connectivity itself. *** ### When Infrastructure Fails Internet access relies on a large network of interconnected systems. These systems include: * Mobile network operators * Internet service providers * Data centers * Fiber infrastructure * Satellite systems * Cloud platforms * Regional networking equipment Failures within any part of this chain can impact access to communication and financial services. Common causes include: #### Natural Disasters Earthquakes, floods, wildfires, hurricanes and severe weather events can damage communication infrastructure and disrupt network availability across entire regions. #### Power Outages Large-scale power failures can disable communication equipment and prevent access to internet services even when devices remain operational. #### Infrastructure Damage Physical damage to network infrastructure can interrupt connectivity for extended periods of time. #### Network Congestion In highly populated environments, communication networks may become overloaded due to excessive demand. *** ### Connectivity Challenges at Large Events Connectivity problems are not limited to emergencies. Large gatherings often create temporary communication bottlenecks. Examples include: * Music festivals * Conferences * Sporting events * Public celebrations * Exhibitions * University campuses Thousands of people attempting to access the same mobile infrastructure simultaneously can significantly reduce network performance. Messages may be delayed, applications may become unreliable and payment systems can experience interruptions. Ironically, these are often situations where communication and coordination are most important. *** ### The Challenges of Remote Regions Many communities around the world continue to experience limited or inconsistent internet access. Remote environments may face challenges such as: * Sparse network coverage * Limited infrastructure investment * Geographic barriers * High connectivity costs For these communities, continuous internet access cannot always be assumed. Digital services designed exclusively for always-online environments may fail to serve users in these regions effectively. *** ### The Cost of Dependence When communication and payment systems depend entirely on centralized infrastructure, disruptions can have immediate consequences. Users may lose access to: * Communication channels * Community coordination tools * Digital payments * Location-based services * Emergency information This creates a fragile model in which a temporary loss of connectivity can interrupt essential activities. Resilient systems should continue operating even when connectivity conditions are less than ideal. *** ### A Different Approach Nearby Protocol is designed around the principle that connectivity should enhance functionality, not define it. Instead of assuming continuous internet access, Nearby introduces infrastructure capable of supporting local coordination in both connected and disconnected environments. Through Proof of Location, Nearby Mesh and OfflinePay, users can: * Verify location without centralized intermediaries * Communicate through local mesh networks * Exchange value without immediate internet access * Coordinate with nearby communities during connectivity disruptions This approach creates a more resilient foundation for real-world interaction. *** ### Connectivity as a Spectrum Connectivity should not be viewed as a binary state. In practice, users may experience: * Full connectivity * Intermittent connectivity * Local connectivity only * Delayed connectivity * No connectivity Systems designed to operate across this entire spectrum are inherently more robust than systems that rely exclusively on constant internet access. Nearby Protocol embraces this reality by enabling communication, verification and payments to function across a wide range of network conditions. The goal is not to replace the internet. The goal is to ensure that essential coordination remains possible when internet access is unavailable, unreliable or insufficient. --- # 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/the-connectivity-problem.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.