⚠️ PAGE UNDER CONSTRUCTION
An Entity is a node in the Internet of Impact graph. The best way of explaining this is to describe the different classes of entities and their primary puposes.
Entities are inter-linked. The relationships between entities are the edges of the impact graph, as illustrated in the example below.
{insert diagram}
Each entity has its own digital identifier, in the format did:ixo:29wribufwiuw984feuf98348fj9f4
and an associated stateful digital record, which is referred to as the DID Document (DDO).
User Story
As a user of the Internet of Impact, I am an Agent with a digital identifier that I can use to authenticate myself with keys that are stored in my Impact Wallet, over which only I have control. As an Agent, I can create a cyber-cellular organisation (Cell) to coordinate the activities of other agents, such as the members of my team, towards achieving a shared mission. I associate the Cell with a Cell Node (web service), which provides computational and data hosting infrastructure for the Cell and its related entities. Now members of my Cell can create one or more Projects. The simplest way of doing this is by using a Template. I can set up an investment entity to form and allocate resources to the Cell and Projects, using an instrument such as an Alphabond. I can employ Oracles to assist with a range of Precision Functions. If I have data assets that will be used by my own and other entities, I can register this data to make it available in a data marketplace. All information and transactions flow between these entities in the format of cryptographically signed messages between identified counter-parties.
Oracles in the context of the Internet of Impact are trusted digitally-enabled services that operate on stateful data to perform Precision Functions (P-functions).
Proofing through evaluation and verification of claims
Prediction by determining statistical probabilities and forecasts
Personalisation of interventions and responses
Prescription to program deterministic interventions and responses
Planning support to make decisions about interventions and responses
Proposing how to configure interventions and responses
Prevention through relative risk calculation and alerting
Protection through threat detection and proactive response
Profiling to identify patterns of attributes and features
Participation by enabling humans in the loop
Users employ ixo Oracles to provide these functions on their data. This helps optimise the outcomes, risks and financial results of cyber-cellular organisations, projects and investments.
Oracles are categorised into different namespace types, to help identify the their general purpose. Whilst oracles are all the same entity class, some security and technical characteristics can differ, depending on the oracle type.
For instance, a Treasury Oracle must be listed in the genesis record of an ixo-SDK blockchain. This type of oracle has the privileged capability to programmatically mint, burn or transfer a specific token on the network.
Each oracle has a digital identifier (DID), with one or more verifiable credentials. These credentials are issued by other entities that have a high trust rating, serving as Trust Seeds. This creates a stateful trust graph, based on cryptographic proofs, which can be independently extracted by any Internet of Impact user who wishes to verify that an oracle can be trusted.
Trust must be earned over time. The performance of each oracle is recorded in the blockchain record. For a given oracle, a user can determine from the oracle's transaction history how many services the oracle has provided, to how many different users. They can also see any disputes against the oracle, which were upheld against the oracle provider.
Oracle service providers may be required by the users who employ their oracles, to place a security deposit into escrow, in order to perform services. This performance bond is a risk assurance mechanism for the users of an oracle service. The bond can be slashed if the terms of a Service Execution Agreement are not upheld, when a dispute is adjudicated against the oracle provider.
Oracle launchpad and innovation bonds
Oracle development toolkit
Jupyter Notebooks for designing and training oracles
Federated learning on a Cell Node network
Oracle credentialing
Entity Class | Primary Purpose |
---|---|
Oracle Type | Purpose (click the links to learn how) |
---|
Agent
The digital representation of a natural person, organisation, machine, or software service.
Cell
The cybernetic unit of organisation for coordinating a network of Agents.
Project
The operational unit for Agents to perform tasks that can be recorded as digital claims.
Investment
The economic unit for programming resource-flows between Agents.
Oracle
A service that operates on stateful data to provide precision functions (P-functions).
Data Asset
The digital representation of any type of data that can be used in a data marketplace transaction.
Template
The generic instance of an entity, which can be used to create a specific instance of the entity.
Evaluation Oracle | Approval of claims |
Alpha Oracle | Risk estimation |
Verification Oracle | Verification of claim and credential proofs (including Zero-Knowledge Proofs) |
Credentialing Oracle | Issuance of Verifiable Credentials |
Impact Oracle | Precision impact |
Audit Oracle | Claims and transactions audit |
Banking Oracle | Banking claims |
Treasury Oracle | Instruct the network treasury module to programmatically mint, burn or transfer tokens |
⚠️ PAGE UNDER CONSTRUCTION
Accesses the claims in a Cell-node database, for which it is authorised.
Reads the claim data.
Uses external information sources to triangulate and predict the odds of claim attributes being true-positive.
Opines on whether the claim meets pre-determined criteria for approval
Enriches the claim with additional information, such as data transformations and expert opinion.
Issues a cryptographic proof based on the analysis and approval status