Loading...
Loading...
Loading...
Loading...
Loading...
Software infrastructure for the Internet of Impact.
The ixo blockchain is open-source software to provide computational and data storage infrastructure for the Internet of Impact. This implements open standards to form an inter-operable network of networks. Anyone can set up an ixo blockchain based network, which will provide users with a common set of functionalities.
A network running the core ixo blockchain software can fulfil the following functional requirements:
The ixo Blockchain software is modular. Application-specific networks can configure these modules for their purpose, add new modules, or swap-out some of the non-core modules. These modules are written in Go.
The purpose of each module is briefly outlined in the table and described in technical detail on the linked pages.
The ixo blockchain SDK shares a set of core blockchain modules with the Cosmos-SDK and is built using the same standards. The Cosmos-SDK is a software development kit for building application-specific blockchains.
This enables functional interoperability between blockchains that implement the same modules.
For example:
The MsgSend
function transfers fungible tokens of designated denominations between counter-parties, using the bank module
.
The account
querier function, which is part of the Auth Module
, returns information about an account, regardless of which chain this account is created on.
The IBC module
enables messages to be sent between blockchain networks implementing the Inter-Blockchain Communication Protocol.
ixo Blockchain SDK Module | Purpose |
---|---|
Functional Requirement
ixo Blockchain mechanism
Identify agents
Digital Identifiers (DID) & Verifiable Credentials
Identify cell nodes
Digital Identifiers (DID)
Identify projects
Digital Identifiers (DID)
Identify claims
Content Identifiers (CID)
Revoke identifiers
Distributed revocation list
Open knowledge graph
Distributed Hash Table (DHT)
Locate cell nodes
DNSLink
Program state-changes
Virtual Machines
Authenticate identifiers
Public Key Infrastructure (PKI)
Sign messages
Cryptographic keys
Validate messages
Validator nodes
Verify claims
Oracles
Record proofs of state
Merkle DAGs
Transfer value
Digital wallets
Issue digital assets
Token minting
Incentivise network hosts
Gas fees
Prevent Byzantine faults
Tendermint consensus
Protect against censorship
Distributed validator nodes
Protect against tampering
Hashes
Protect against spam
Message Validation
And more ... not an exhaustive list
Alpha Module
Calculates project risk scores (Alpha) which provide signals to the Bonds module to adjust the pricing of Alpha-Bonds and trigger bond state changes.
Bonds Module
Calculates the buy/sell price and supply of tokens, using configurable bonding curve algorithms and other automated market-maker mechanisms.
Manages the life-cycle of Alpha Bonds.
Cells Module
Maintains a registry of Cell Node identifiers, with associated cryptographic public key material and DNSLink record of the cell's hosting location.
Claims Module
Maintains a registry of Impact Claim digests and claim status, with verification proofs.
Data Assets Module
Maintains a registry of data assets, automates usage rights management and IP ownership/control. Data assets include templates, algorithms, evaluation methods, datasets, etc.
Fees Module
Automates billing, accounting, distribution and settlement of fees for all digital services delivered through the network.
Identity Module
Maintains a registry of trusted root identifiers and revocation lists, based on Web of Trust principles and complying with W3C specifications for digital identifiers and verifiable credentials.
Oracles Module
Maintains a registry of oracles, with staking and insurance mechanisms.
Defines rights for oracles to perform specific functions, such as mint or burn digital assets (using Object Capabilities).
Treasury Module
Issues standard digital assets through mint and burn functions. Maintains a ledger of assets.
The digital dynamo for processing, storing, protecting and sharing impact claims data. Deployed as fully decentralised virtual containers that are identified and secured on the ixo blockchain. A marvel built for Web 3 data sovereignty and interoperability! ixo-pods provide the open-source software infrastructure for all types of data-intensive sustainable development applications.
Automatically deploys when a project is initiated. Configures to the requirements of the project. Validates claim submissions in real-time (eliminating duplicates). Built for high-definition data, based on the new web standards for verifiable claims. Stores data in a cryptographically secured private ledger. Identified and secured by the ixo public blockchain. Includes a powerful event sourcing module and web APIs. Access is controlled by decentralised authentication. Enables secure communications and messaging. Project Founders own and control their project data and decide where this should be hosted. This is free open-source software that is fast, inexpensive and highly scalable.
ixo Data Stores are fast, cost-effective, highly scalable and fully interoperable with a wide range of services.
You hold the keys to your data and decide who gets access. Processes project data automatically, as each claim is checked and validated on submission. No more double-counting. Record claims in a high-definition data format that is machine-readable and verifiable. Each project Publishes claims metadata to the ixo public blockchain, for transparency, accountability and trust. Built for Web 3.
Collect, validate, store and share your project data with private, secure, decentralised data containers, your data is always Built for Web 3, ixo Project Data Stores automatically process and store claims in a new high-definition data format. Each claim is validated and published to the public ixo blockchain.
How the Internet of Impact is built
ixo Protocol networks are formed by connecting distributed blockchain nodes in a way that is designed to create a global Internet of Impact. This builds on core Internet protocols and standards, but uses additional and repurposed standards, in the same way as Web 2.0 has been adapted to form the Internets of Commerce, Finance, Social Media, Internet of Things, etc.
The ixo Protocols provide additional common operating protocols and standards that build on foundational new World-wide Web Consortium (W3C) standards for Linked-data, Decentralised Identifiers and Verifiable Claims. ixo also builds on emerging Web3 standards for tokenisation, cryptographic message-signing and validation.
Together, the ixo Protocols provide new ways of:
Identifying impact with decentralised identifiers and high-definition data
**Verifying impact **with crypto-economic proofs
**Valuing impact **through tokenisation of impact data assets
The Internet of Impact will become interconnected by the Inter-blockchain Communication (IBC) Protocol. In the future this will also connect across protocols, to a universe of other Web3 networks, including for instance, the Ethereum Network.
ixo Protocol Networks may be independently configured into zones that have their own security, governance and economic mechanisms. These networks may be public or private, closed or open. The building-blocks are modular, open-source software components that anyone can reuse, build on and repurpose for their own diverse applications and use-cases.
These network zones provide the backbone that supports a reticular mesh of project Nodals. Nodals can be thought of as the cells that are responsible for coordinating, resourcing and incentivising the sense and respond activities of the network. Each Nodal is a containerised, sovereign message processing and project data storage component.
Validator Node operators of the Sustainability Hub are referred to as Relayers. These organisations join a consortium which is responsible for securely operating blockchain nodes and to host the software clients that deliver applications to end-users. Relayers also provide channels to the markets in which they operate, providing support to their customers and end-users with value-adding products and services.
Applications built on ixo protocol networks are delivered as web, mobile, IoT and Precision Oracle services. A collection of open-source ixo client applications is available for developers to build on or adapt to their own business requirements.
The** ixo protocols** are based on core new standards for the decentralised internet from the World-wide Web Consortium (W3C).
The software clients that provide the communications, data processing and storage capabilities of ixo protocol networks are modules that build on the generic Cosmos SDK, written in Golang.
In addition to the generic Cosmos modules, which have been purposed for the Internet of Impact, the ixo SDK includes application-specific modules, which include:
Projects Module
Bonds Module
Data Assets Module
Identity Module
Fiat Banking Oracle Module
Alpha Oracle Module
The ixo blockchain contains the records of every claim that is issued against a project and the subsequent evaluation of those claims. Each record is validated by a quorum of validator nodes before it is written to the chain and thereafter the record cannot be removed or updated. This data is then aggregated to build out the final states of the projects.
All the information on the ixo blockchain is publicly available through the ixo Explorer. This data includes the project information, stats regarding the project, the stakeholders of the project and the structure of data being captured against the project. All actual claim data is stored in the Project Datastore.
Much of the data that is captured within a claim is highly sensitive in nature. This data might have specific regulator requirements such as GDPR or maybe the data may not reside outside certain geographical boundaries. In order to comply with this and to also put the data into the hands of the owners of the project we have created the concept of independent data stores for each project.
The ixo Blockchain keeps a link to the location of these project data stores and provides services to the project data that are governed by cryptographic access controls.
All requests that create data or access sensitive data require cryptographic signatures and a capabilities model supports this to provide finer grained access control.
In general update requests are created and signed on the front end using our keysafe which holds the private keys for the user. The request with its signature portion is then passed to the Project Datastore (PDS) when it is processed and the results are then ledgered onto the ixo blockchain with hash references back to the original transaction on the PDS. The block containing the request is then processed on the ixo blockchain and the ixo Explorer syncs this block to the current system state.
When reading publicly availably data a REST call is made to the ixo Explorer which contains the current state of the blockchain. If private information needs to be accessed then a signed request is submitted to the PDS which will respond with the data if the the signature and capabilities of the user adhere to the policies for that data.
The diagram below offers a view of what happens when an 'upload project' message is received from the UI, and which ixo components are involved at every stage, with focus on Cell Node.