From caec83406e9dbea4580a67b1c1b3b8a84a452005 Mon Sep 17 00:00:00 2001 From: Marine DECHAMP-GUILLAUME <92780073+MdechampG@users.noreply.github.com> Date: Fri, 8 Mar 2024 14:50:48 +0100 Subject: [PATCH] fix: correct typo and center image tags --- docs/academy/overview.mdx | 4 ++-- docs/academy/part-2/decentralized-identity.mdx | 8 ++++---- docs/academy/part-2/describe-resource.mdx | 8 ++++---- docs/academy/part-2/describe-zone.mdx | 6 +++--- docs/academy/part-2/resource-governance.mdx | 16 ++++++++-------- docs/academy/part-2/verifiable-claims.mdx | 16 ++++++++-------- docs/academy/part-2/zone-governance.mdx | 14 +++++++------- docs/faq/faq.md | 6 +++--- .../governance/governance-extent.md | 2 +- .../governance/hierarchy-of-norms.md | 4 ++-- .../ontology/the-power-of-ontologies.md | 8 ++++---- .../ontology/what-are-ontologies.md | 8 ++++---- docs/tutorials/explorer-sc.md | 4 ++-- docs/tutorials/keplr-1.mdx | 10 +++++----- docs/tutorials/nonos-tuto-2.md | 2 +- docs/tutorials/nonos-tuto-3.md | 2 +- docs/tutorials/prolog-1.mdx | 4 ++-- docs/whitepaper/architecture.mdx | 4 ++-- docs/whitepaper/solution.md | 4 ++-- docs/whitepaper/token-model.tsx | 8 ++++---- 20 files changed, 69 insertions(+), 69 deletions(-) diff --git a/docs/academy/overview.mdx b/docs/academy/overview.mdx index 1e82cb6e9bf..5b2f17a25e0 100644 --- a/docs/academy/overview.mdx +++ b/docs/academy/overview.mdx @@ -9,9 +9,9 @@ Welcome to the Axone Academy, your gateway to the cutting-edge world of off-chai Throughout this concise journey, we will guide you through the core principles of the Axone protocol, providing you with a swift understanding of its functions. Prepare to immerse yourself in Axone, where the focus lies on optimizing resource sharing and creating new knowledge. Are you ready to explore the forefront of off-chain resource management? Follow us through this Academy to unravel the intricacies of Axone. -
+
![overview-1](/img/content/academy/overview-1.webp) -
+ ## Your learning journey diff --git a/docs/academy/part-2/decentralized-identity.mdx b/docs/academy/part-2/decentralized-identity.mdx index 0e046e1c76b..ff2d1c37e88 100644 --- a/docs/academy/part-2/decentralized-identity.mdx +++ b/docs/academy/part-2/decentralized-identity.mdx @@ -42,9 +42,9 @@ A Holder can be a person, organization, product, or object possessing a set of a A Verifier is an entity empowered to authenticate the legitimacy and veracity of a Verifiable Credential through a Verifiable Presentation submitted to it. The verifier can confirm that the information presented originates from the correct and authorized Issuer and that the Verifiable Credential has not been altered in any way. Generally, the verifier can also check that the Verifiable Credential has not expired or been revoked. -
+
Decentralized Identity tryptic -
+ **Zero-knowledge proof** (ZKP) technology can be used to share proof of identity or authorization without revealing the complete identity of the holder. @@ -205,9 +205,9 @@ Understanding and distinguishing key roles is essential when claiming a resource - **Holder**: This role is assigned to the DID of the resource itself. The holder embodies the digital identity of the resource in the dataverse, thus constituting a central point for any interaction or transaction concerning this resource. - **Issuer**: The issuer, whose DID is linked to creating the Verifiable Credential, plays a decisive role. It ensures the authenticity and legitimacy of the resource's claim, guaranteeing its official recognition in the protocol. -
+
Decentralized Identity and Axone -
+ In the case of the declaration of a digital resource in the Dataverse, the Provider has three roles at the same time: - Issuer as he declares the metadata of its resource diff --git a/docs/academy/part-2/describe-resource.mdx b/docs/academy/part-2/describe-resource.mdx index 931e4f944a7..9ce2d823c67 100644 --- a/docs/academy/part-2/describe-resource.mdx +++ b/docs/academy/part-2/describe-resource.mdx @@ -8,13 +8,13 @@ sidebar_position: 3 Now that you know what a DID and a Verifiable Credential are, and what they mean for the Axone protocol, let's put them into practice! -You're a digital resource provider and you want to share a dataset or a service. First, you need to describe your resource and register it in the Dataverse (i.e. in the Axoneprotocol). +You're a digital resource provider and you want to share a dataset or a service. First, you need to describe your resource and register it in the Dataverse (i.e. in the Axone protocol). Here are the 4 steps involved: -
+
Steps to describe a resource in the Dataverse -
+ We'll take 2 examples in this tutorial: @@ -249,7 +249,7 @@ You can see that there is a new field in the jsonld with the cryptographic proof The VC is now in the hands of the Holder. Note that it is possible that the Issuer is also the Holder. -The Axone blockchain can only register VCs in N-Quads format. Then, you must convert the jsonld files in N-Quads. You can use this tool: https://transform.tools/jsonld-to-nquads . +The Axone blockchain can only register VCs in N-Quads format. Then, you must convert the jsonld files in N-Quads. You can use this tool: https://transform.tools/jsonld-to-nquads. ## Step 4: Register the credentials in the blockchain diff --git a/docs/academy/part-2/describe-zone.mdx b/docs/academy/part-2/describe-zone.mdx index 813979815e1..7dada81d0b9 100644 --- a/docs/academy/part-2/describe-zone.mdx +++ b/docs/academy/part-2/describe-zone.mdx @@ -12,9 +12,9 @@ All the workflows initiated within the Axone protocol must be defined in the con Let's see how to describe and register a zone in the Axone Protocol. Here are the four steps involved: -
+
Steps to describe a resource in the Dataverse -
+ We'll take the example of the Collaborative AI Zone in this tutorial. @@ -178,7 +178,7 @@ You can see that there is a new field in the jsonld with the cryptographic proof The VC is now in the hands of the Holder. Note that it is possible that the Issuer is also the Holder. -The Axone blockchain can only register VCs in N-Quads format. Then, you must convert the jsonld files in N-Quads. You can use this tool: https://transform.tools/jsonld-to-nquads . +The Axone blockchain can only register VCs in N-Quads format. Then, you must convert the jsonld files in N-Quads. You can use this tool: https://transform.tools/jsonld-to-nquads. ## Step 4: Register the credentials in the blockchain diff --git a/docs/academy/part-2/resource-governance.mdx b/docs/academy/part-2/resource-governance.mdx index eaf21fa9274..f590b77ab79 100644 --- a/docs/academy/part-2/resource-governance.mdx +++ b/docs/academy/part-2/resource-governance.mdx @@ -10,7 +10,7 @@ sidebar_position: 4 We recommend you first read the [Technical documentation of Governance](https://docs.okp4.network/technical-documentation/governance/introduction) before delving into practice in the Academy. ::: -Resource Consent is an agreement associated with the use of Resources within Zones. By resources, we mean Digital Resources (e.g., datasets) or Digital Services. It goes beyond simple approval and encompasses the permissions and restrictions on resource owners' access, usage, sharing, management, and handling of their resources. It allows parties to define boundaries and establish terms for others to interact with their digital resources. This aspect is crucial aspect of governance, ensuring resources are used appropriately per the relevant parties' expressed will and intentions. +Resource Consent is an agreement associated with the use of Resources within Zones. By resources, we mean Digital Resources (e.g., datasets) or Digital Services. It goes beyond simple approval and encompasses the permissions and restrictions on resource owners' access, usage, sharing, management, and handling of their resources. It allows parties to define boundaries and establish terms for others to interact with their digital resources. This is crucial for governance, ensuring resources are used appropriately per the relevant parties' expressed will and intentions. The materialization of a resource in the dataverse requires the creation of a Governance VP. According to a principle of self-determination, the resource itself must generate this VP, i.e., the issuer and the resource have the same identity. @@ -23,15 +23,15 @@ In the protocol, governance structures are made up of two key elements: - A **VP** serves as proof of the existence of a governance by referencing the Codified Governance. This document plays a fundamental role in creating a resource within the dataverse. - **Governance as Code** is represented by a program written in Prolog. This program details and encodes the specific rules governing resource management. -
+
Governance elements for Resources in Axone Protocol -
+ Here are the five steps to create the governance of a resource in the Dataverse: -
+
Steps to create a resource's governance -
+ We'll take 2 simple examples in this tutorial: @@ -134,9 +134,9 @@ partOf(subSec1, sec1). partOf(sec1, chap1). ``` -
+
Governance elements for Resources in Axone Protocol -
+ #### Elements of description @@ -304,7 +304,7 @@ You can see that there is a new field in the jsonld with the cryptographic proof The VC is now in the hands of the Holder. Note that it is possible that the Issuer is also the Holder. -The Axone blockchain can only register VCs in N-Quads format. Then, you must convert the jsonld files in N-Quads. You can use this tool: https://transform.tools/jsonld-to-nquads . +The Axone blockchain can only register VCs in N-Quads format. Then, you must convert the jsonld files in N-Quads. You can use this tool: https://transform.tools/jsonld-to-nquads. The final step is to register the VCs in the Axone blockchain by submitting them to the Dataverse smart contract. It's the role of the Registrant (who can be the Holder or another entity). diff --git a/docs/academy/part-2/verifiable-claims.mdx b/docs/academy/part-2/verifiable-claims.mdx index c6ce4172e72..0f95fad3ac6 100644 --- a/docs/academy/part-2/verifiable-claims.mdx +++ b/docs/academy/part-2/verifiable-claims.mdx @@ -21,9 +21,9 @@ A credential may contain several claims. For example, a diploma contains the cla In the [W3C standard](https://www.w3.org/TR/vc-data-model/), a credential is a set of one or more **claims** made by the same entity. Credentials include an identifier and metadata describing the credential's properties, such as the issuer, the expiry date and time, a representative image, a public key to use for verification purposes, the revocation mechanism, and so on. The issuer might sign the metadata. A verifiable credential is a set of tamper-evident claims and metadata that cryptographically prove who issued it. -
+
Verifiable claims W3C -
+ :::info @@ -41,9 +41,9 @@ A **verifiable presentation** is a tamper-evident presentation encoded in such a A government authority issues a digital passport to a citizen. -
+
Verifiable claims passport example -
+ Use when traveling : @@ -64,9 +64,9 @@ This notion is analogous to that of crypto-currency wallets. Although all addres Verifiable Credentials obey schemas that describe a particular aspect of a resource. Certain VCs apply depending on the nature of the resource. A VC describing an entity or organization does not apply to the same resource as a VC describing a dataset. This is why VCs are organized in schemas. -
+
Verifiable claims attached to a resource -
+ ### Resource materiality @@ -90,8 +90,8 @@ Once the Issuer successfully issues the Verifiable Credentials (VCs) associated Recording VPs in the blockchain, rather than individual VCs, ensures the confidentiality of specific properties by only revealing a restricted set of properties on the public chain. -
+
Verifiable presentation W3C -
+ diff --git a/docs/academy/part-2/zone-governance.mdx b/docs/academy/part-2/zone-governance.mdx index 2edea0632bb..5358bc49285 100644 --- a/docs/academy/part-2/zone-governance.mdx +++ b/docs/academy/part-2/zone-governance.mdx @@ -23,15 +23,15 @@ In the protocol, governance structures are made up of two key elements: - A **VP** serves as proof of the existence of a governance by referencing the Codified Governance. This document plays a fundamental role in creating a zone within the dataverse. - **Governance as Code** is represented by a program written in Prolog. This program details and encodes the specific rules governing zone management. -
+
Governance elements for Zone in Axone Protocol -
+ Here are the five steps to create a zone governance in the Dataverse: -
+
Steps to create a zone's governance -
+ We'll take one simple example in this tutorial for the Collaborative AI zone. @@ -112,9 +112,9 @@ partOf(subSec1, sec1). partOf(sec1, chap1). ``` -
+
Governance elements for Resources in Axone Protocol -
+ #### Elements of description @@ -283,7 +283,7 @@ You can see that there is a new field in the jsonld with the cryptographic proof The VC is now in the hands of the Holder. Note that it is possible that the Issuer is also the Holder. -The Axone blockchain can only register VCs in N-Quads format. Then, you must convert the jsonld files in N-Quads. You can use this tool: https://transform.tools/jsonld-to-nquads . +The Axone blockchain can only register VCs in N-Quads format. Then, you must convert the jsonld files in N-Quads. You can use this tool: https://transform.tools/jsonld-to-nquads. The final step is to register the VCs in the Axone blockchain by submitting them to the Dataverse smart contract. It's the role of the Registrant (who can be the Holder or another entity). diff --git a/docs/faq/faq.md b/docs/faq/faq.md index 2c382ad644f..3f4b9c3dbbf 100644 --- a/docs/faq/faq.md +++ b/docs/faq/faq.md @@ -10,7 +10,7 @@ sidebar_position: 1 Axone is the first settlement layer for off-chain workflows using shared resources. In other words, it is an open-source and public protocol that enables the sharing and orchestration of digital off-chain resources (datasets, algorithms, storage, computation resources…) while enforcing their associated governance rules. -### How does Axone works in a few words ? +### How does Axone work in a few words ? Axone is a custom blockchain facilitating digital resource sharing with auditability and adherence to consent rules. It establishes trust through decentralization, offers a flexible incentive system, and reduces digital ecosystem fragmentation by enabling 'Anything as a Service'. The protocol introduces Zones for resource orchestration and utilizes an on-chain ontology for standardized interpretation of diverse elements. With smart contracts and modules, it is the orchestrator of workflows running on shared resources for any applications. @@ -84,7 +84,7 @@ In summary, the distinction between Zones and resources enables the Axone ecosys The Dataverse is an ever-expanding universe comprised of all the digital resources, such as datasets, and digital services such as infrastructure services, processing services or any other digital service referenced in the Axone Blockchain. All resources, services and Zones are found within the same universe, the Dataverse. The on-chain Ontology is the semantic representation of the Dataverse. -### How does Axone stores the resources and services? +### How does Axone store the resources and services? As a protocol, Axone doesn't store them. It only references the resource/services where it is (wherever it is) and make it available to the network according to the permissions granted by the provider. It can be stored anywhere, with any kind of storage solution, either centralized or decentralized. @@ -318,7 +318,7 @@ Axone functions as a decentralized coordinator where: - The workflow can be initiated in accordance with the consent rules of each resource. - The workflow is recorded on-chain and is subject to thorough auditing. -### How does Axone ensures the execution and validation of sharing rules? +### How does Axone ensure the execution and validation of sharing rules? The protocol itself is primarily an infrastructure that allows a resource "provider" to reference and define usage rules (in Prolog, which offers better expressiveness compared to other languages), and for a "consumer" to make usage requests based on these rules. What the protocol guarantees is the transparency of the rules and the correct assessment (validation or not) of these rules. However, there is indeed the question of verifying the actual "real" sharing action. The current approach is an open-source off chain "orchestrator" developed by the Axone Association team that provides access to resources (based on requests validated onchain) and then reports the successful execution back on chain. So, yes, there's an element of centralization! We aim to have multiple orchestrators, deployed by external entities, and even decentralize that process at some point. Both "providers" and "consumers" will be able to choose the one they "trust" or deploy their own. diff --git a/docs/technical-documentation/governance/governance-extent.md b/docs/technical-documentation/governance/governance-extent.md index c0e99304187..da85b90498f 100644 --- a/docs/technical-documentation/governance/governance-extent.md +++ b/docs/technical-documentation/governance/governance-extent.md @@ -48,7 +48,7 @@ The Zone Rules directly address matters that significantly impact business activ Here are some facets of business models in the zones: - **Retribution models**: Rules establish the economic terms resulting from the orchestration of resources within a zone. The retribution model describes the creation and redistribution of resulting value, benefitting all participating parties. The models can be diverse and significantly different from each other, and their design can either promote equity or impose constraints on it. For instance, in one specific Zone, it may be stated that Open Data does not receive remuneration, whereas other data sets receive remuneration. Conversely, each service provider may set the price associated with their service usage in another zone, with compensation arranged according to this price. -- **Economic Incentives**: The rules specify financial incentives to promote desirable behaviours and outcomes within the Zone. This can include mechanisms such as reward systems, token incentives, or revenue-sharing models that encourage active entities to contribute to the growth and development of the Zone actively. +- **Economic Incentives**: The rules specify financial incentives to promote desirable behaviors and outcomes within the Zone. This can include mechanisms such as reward systems, token incentives, or revenue-sharing models that encourage active entities to contribute to the growth and development of the Zone actively. ### Related to self diff --git a/docs/technical-documentation/governance/hierarchy-of-norms.md b/docs/technical-documentation/governance/hierarchy-of-norms.md index 7229d31e925..0a182de6dac 100644 --- a/docs/technical-documentation/governance/hierarchy-of-norms.md +++ b/docs/technical-documentation/governance/hierarchy-of-norms.md @@ -8,9 +8,9 @@ The hierarchy of norms refers to the hierarchical structure of rules within the In the Axone Governance framework, the hierarchy of norms establishes a clear order of precedence for rules and regulations. We thus end up with different levels of governance that allow fine-grained control of the use of the protocol. -
+
Governance - Hierarchy of Norms -
+
diff --git a/docs/technical-documentation/ontology/the-power-of-ontologies.md b/docs/technical-documentation/ontology/the-power-of-ontologies.md index ec506f4dec3..ae651fb22f0 100644 --- a/docs/technical-documentation/ontology/the-power-of-ontologies.md +++ b/docs/technical-documentation/ontology/the-power-of-ontologies.md @@ -6,9 +6,9 @@ sidebar_position: 1 In the Axone protocol, ontologies are indispensable. They facilitate a comprehensive depiction of the dataverse, capturing even its most intricate details. Ontologies provide detailed descriptions of both datasets and services, enhancing overall comprehension. Moreover, they bridge the connection between governance and orchestration within the dataverse. -
+
-
+ This ontology allows to achieve: @@ -28,9 +28,9 @@ Several languages are used to express the Axone ontologies: - RDFS (RDF Schema): an ontology representation language that defines classes and properties and relationships between them. RDFS is an extension of RDF. - [SKOS (Simple Knowledge Organization System)](https://en.wikipedia.org/wiki/Simple_Knowledge_Organization_System): a language for representing ontology that allows the description of classification systems and thesauri. SKOS allows the definition of concepts, relationships, and properties. -
+
-
+ ## Ontology at the heart of the blockchain diff --git a/docs/technical-documentation/ontology/what-are-ontologies.md b/docs/technical-documentation/ontology/what-are-ontologies.md index 14198312c3b..78871e81036 100644 --- a/docs/technical-documentation/ontology/what-are-ontologies.md +++ b/docs/technical-documentation/ontology/what-are-ontologies.md @@ -8,9 +8,9 @@ sidebar_position: 2 In computer science, ontology is a formal and structured representation of the concepts, relationships, and properties of a particular domain. An ontology generally comprises the following basic elements: concepts, relationships, properties, axioms, and instances. These can be graphically represented by the simplified equation shown below. -
+
Ontology equation -
+ Some definitions: @@ -110,9 +110,9 @@ The construction of this ontology follows a number of steps which are described - **Ontology implementation (5)**: Encoding the ontology according to the OWL grammar. - **Ontology evaluation (6)**: Association of key concepts and terms in the ontology with concepts and terms of other ontologies. -
+
Ontology construction process -
+ ## Underlying Assumptions diff --git a/docs/tutorials/explorer-sc.md b/docs/tutorials/explorer-sc.md index 4d94465d023..c331680ea84 100644 --- a/docs/tutorials/explorer-sc.md +++ b/docs/tutorials/explorer-sc.md @@ -52,7 +52,7 @@ You'll see your Axone wallet address if you click again on the wallet button. Cl - Send a few $AXON tokens to another Axone wallet, `okp41wuxc2mzy0wp27cdcfnde3vz07eurpd7grfmq6n` as the recipient for example. - Click on "Send" and "Approve" to confirm the transfer. -
+
Once completed, click on "View transaction". @@ -69,7 +69,7 @@ Once completed, click on "View transaction". You can also retrieve a transaction you executed by clicking the "Search" button upper on the right, providing your Axone address, and clicking "Confirm". Click on the hash in the "Transactions" section to get the details. -
+
If you have the transaction hash, you can also directly get transaction details by providing the hash in the Search modal. diff --git a/docs/tutorials/keplr-1.mdx b/docs/tutorials/keplr-1.mdx index 345c30b1d93..a828413df6e 100644 --- a/docs/tutorials/keplr-1.mdx +++ b/docs/tutorials/keplr-1.mdx @@ -61,7 +61,7 @@ The official Axone faucet provides a way to obtain test tokens for experimentati - Type "OKP4", - Click on `Axone drunemeton`, and then click on "Save". -
+
2. Let's check you received the **AXON** tokens: @@ -70,7 +70,7 @@ The official Axone faucet provides a way to obtain test tokens for experimentati Alright, there's **1 AXON** in the wallet. -
+
3. Your wallet is identified by an address derived from your recovery phrase. To receive $AXON tokens, you should provide your Axone address to the spender. Here's how you can have your Axone address: @@ -79,7 +79,7 @@ Here's how you can have your Axone address: - Look for `Axone drunemeton` in the list or type ‘okp4' in the "Search for a chain" field to see it easily. - Click on "Copy" to have the Axone address, which is in the following form: `okp41yxrseqc9weu6cm...9xdf3k5z8nwknf` -
+
## Send $AXON tokens to another wallet @@ -87,11 +87,11 @@ Now that you have $AXON tokens in your Keplr Wallet, you can send them to other 1. Click on the Keplr extension icon and on "Send". -
+
2. Select the asset you want to send: AXON. Provide the recipient wallet address, the amount and, optionally, a memo. Click on "Next" and "Approve". You will have to pay a small fee to execute the transaction. -
+
### Check your transaction with the explorer diff --git a/docs/tutorials/nonos-tuto-2.md b/docs/tutorials/nonos-tuto-2.md index c8541d0e263..d9fe8af3b60 100644 --- a/docs/tutorials/nonos-tuto-2.md +++ b/docs/tutorials/nonos-tuto-2.md @@ -6,6 +6,6 @@ sidebar_position: 102 🚀 Welcome to the second episode of Nono's Tuto! Your tutorial series to become an expert developer on the Axone protocol 🔥 -📚 In this second episode, we'll be focused on the governance architecture on Axone with some theory and some live examples ! +📚 In this second episode, we'll be focusing on the governance architecture on Axone with some theory and some live examples! diff --git a/docs/tutorials/nonos-tuto-3.md b/docs/tutorials/nonos-tuto-3.md index 79b5b1c0b54..edcc55ab20a 100644 --- a/docs/tutorials/nonos-tuto-3.md +++ b/docs/tutorials/nonos-tuto-3.md @@ -6,6 +6,6 @@ sidebar_position: 103 🚀 Welcome to the third episode of Nono's Tuto! Your tutorial series to become an expert developer on the Axone protocol 🔥 -📚 In this third episode, we'll dive in the Ontology and do some demonstration! +📚 In this third episode, we'll dive into the Ontology and do some demonstration! diff --git a/docs/tutorials/prolog-1.mdx b/docs/tutorials/prolog-1.mdx index a5f4d17e2e5..25c5e4598cd 100644 --- a/docs/tutorials/prolog-1.mdx +++ b/docs/tutorials/prolog-1.mdx @@ -6,7 +6,7 @@ sidebar_position: 5 ![Tutorials overview](/img/content/tutorials/prolog.webp) -Welcome, Axone builders to an exciting journey at the crossroads of Prolog and blockchain! +Welcome, Axone builders, to an exciting journey at the crossroads of Prolog and blockchain! This tutorial delves into the fascinating realm of logic programming and its profound impact on the "law" governing off-chain resources usages. Whether you're interested in developing using the protocol or are intrigued by one of the core Axone concepts, this tutorial will equip you with the knowledge of programming rules with Prolog and how to use it to set up and enforce rules without trusting a central authority. @@ -24,7 +24,7 @@ The rules define access conditions and the revenue-sharing model, for example. B The declarative nature of Prolog makes it an excellent choice for establishing governance rules in decentralized systems where rules can be explicitly stated and enforced. Unlike procedural languages, where the control flow is explicitly coded, Prolog uses a declarative approach where you declare the facts and rules. -### How the Axone protocol leverages Prolog language? +### How does the Axone protocol leverage Prolog language? The Axone blockchain has a Prolog interpreter built-in, the "logic module", which enables the definition of complex business logic and agreement conditions using a concise and human-readable syntax. diff --git a/docs/whitepaper/architecture.mdx b/docs/whitepaper/architecture.mdx index d7276c89577..e2085c7b057 100644 --- a/docs/whitepaper/architecture.mdx +++ b/docs/whitepaper/architecture.mdx @@ -76,9 +76,9 @@ Smart contracts handle all interactions with external parties, whether to provid - **Orchestration**: ensures the smooth coordination and execution of services. It enforces the rules and policies that govern resource (datasets and services) authorizations. -
+
-
+ ### Objectarium: unstructured data storage diff --git a/docs/whitepaper/solution.md b/docs/whitepaper/solution.md index 5cdf101cfb6..e8d6bbbbf62 100644 --- a/docs/whitepaper/solution.md +++ b/docs/whitepaper/solution.md @@ -79,7 +79,7 @@ Zones can be nested and overlapping, as one resource or service can participate **What's the purpose ?** **Creating a general purpose Ecosysteme that enables XaaS integration** Anything that is presented to the Protocol as a Service, whatever it does, wherever it is hosted or deployed (in the cloud or on premise), whoever provides it, it can be used by the Protocol. Therein lies **the integration power of the protocol**, which brings infinite scalability and extensibility to the entire Axone ecosystem. -The description of each resource referenced on the protocol ensures their proper processing by the different entities of the protocol. +The description of each resource referenced in the protocol ensures their proper processing by the different entities of the protocol. ![solution-3](/img/content/whitepaper/solution-3.webp) @@ -172,7 +172,7 @@ To tackle this, Axone aims at providing a **reliable and secure mechanism** to e ![solution-8](/img/content/whitepaper/solution-8.webp) 1. An Identity (human or bot) wants to interact with a Zone -2. The Zone asks to the dedicated smart contract if its possible given the context and all the involved rules +2. The Zone asks to the dedicated smart contract if it's possible given the context and all the involved rules 3. The protocol employs logical inference to resolve matters based on the state of the blockchain 4. The protocol yields a modality as a response, such as "prohibited", "permitted", "possible", and so on. Depending on the answer, the execution process could start. diff --git a/docs/whitepaper/token-model.tsx b/docs/whitepaper/token-model.tsx index 61cab30a855..8f996a11276 100644 --- a/docs/whitepaper/token-model.tsx +++ b/docs/whitepaper/token-model.tsx @@ -27,7 +27,7 @@ export const LinePlot = ({ caption, xLegend, yLegend, xFormat, yFormat, data }) return (
-
+
-
-
+ +
{caption}
-
+
) }