# Regions Since IronWeave stores data on-chain, and is agnostic to the type of data that is stored in blocks, and each interactions is private and securely encrypted against scanning, there are many different applications for the IronWeave fabric. Some such applications may require special or compliance-related data handling. To accommodate such special cases, IronWeave has the concept of special-purpose Zones called **Regions**. Just like how a Zone in IronWeave is a chain and validator boundary, a Region is also a chain and validator boundary, but with constraints. Each Region can have different kinds of constraints applied, to meet the needs of various industry, uses, compliance requirements, geographical boundaries that must be observed, stringent encryption that must be used, or even constraints on the types of blocks or block categories that can be employed. There are all sorts of potential uses for Regions, just like there are all sorts of use cases for IronWeave. The availability of Regions is how IronWeave responds to such needs or constraints. ## Types of Regions There are all sorts of reasons why or when a Region is needed. Here are a few: * **Healthcare Region:** this potential region would be HIPAA compliant to enable HIPAA data to be stored in IronWeave blocks. A healthcare region may have Validators and other nodes (storage node, Manager node) that must be running on hardware that is in a certified HIPAA-compliant datacenter, and the node operators for that Region may be required to have a BAA. A Business Associate Agreement (BAA) is a legally binding contract between a HIPAA-covered entity (like a healthcare provider) and a business associate (a vendor, such as a Validator) that handles Protected Health Information (PHI) on their behalf. * **Government Region:** this potential region would meet the data and storage requirements of the government with which the Region is associated or allowed. There could be an IronWeave Region that meets the requirements of the United States government, or the EU, or others. * **Geographical Region:** this potential region could have validators that only reside in the geographical area where the Region operates, to meet compliance requirements. There are *many* other potential Regions as well, with their specialized requirements. The existence of Zones in IronWeave enables the creation of these special-purpose Regions, and enable contractual or other separation from existing and general-purpose Zones in IronWeave. ## Region Requirements Each Region must be approved by the IronWeave Foundation (or Upheaval Corporation, the company that created IronWeave, as appropriate or necessary). Consensus in a Region, in addition to using Proof of Stake and the underlying selected BFT consensus protocol, will also require Proof of Authority, which will be necessary for a node operator or validator to operate in a given Region. This is a requirement to ensure compliance with the Region's specific requirements. It's anticipated that Corporate Currency holders (equity owners, validated by digital proof of ownership of a Corporate Currency chain) will automatically be allowed to run validators in Regions (they will receive a certificate confirming their Proof of Authority). Corporate Currency holders also have a reduced requirement for Proof of Stake staking requirements (26% of otherwise required Stake). It's also important to note that interaction with the rest of the IronWeave fabric is not a given from within a Region. Requirements or constraints on a given Region may prevent interaction with public Zones (by virtue of their data storage requirements), or may only let certain block types or block categories interact outside the Region. Regions are a compelling capability for IronWeave for industries, segments, or special requirements that exist that may otherwise preclude organizations from participating in (and benefiting from) the advantages of IronWeave, but their provisioning and undertaking are not simple nor straightforward. Those considerations are in part why Regions must be approved before being provisioned in the IronWeave fabric. --- # Agent Instructions: 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.ironweave.io/scalability/regions.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.