Zoned Architecture
iov42's zoned architecture influences platform performance, security, and governance.
Last updated
Was this helpful?
iov42's zoned architecture influences platform performance, security, and governance.
Last updated
Was this helpful?
The iov42 global platform is based on the formation of local, permissioned DLT networks called zones
Each zone is formed by a limited number of locally connected nodes
iov42 zone: a single DLT network made up of a limited number of data center nodes.
Zone characteristics:
Every node in the zone participates in consensus and has a copy of the immutable history of all of the zone’s activity - the ledger
All data, including transactions, remain within the zone
Forming a zone:
An iov42 zone can be created based on factors such as geographical location, industry, or regulatory requirements. In most cases, geography will also be a determining factor.
→ Example(s):
A group of petroleum suppliers form a zone to allow their customers to trade fuel and carbon certificates within a certain region.
Telecommunications companies or internet service providers (ISPs) form a zone to offer the iov42 platform as a service for their customers to develop DLT solutions
Advantages of the zone model:
A rapid consensus process and a higher number of transactions per second
Little incentive for zone participants to undermine the zone’s integrity
Governance is built into each zone through legal agreements made between the node operators
The zones are designed to eventually be able to connect with one another and form a global network of networks that could truly meet demands of scalability, interoperability, and regulatory compliance.
