Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add introduction --> core-concepts/trust-minimisation #2845

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
62 changes: 0 additions & 62 deletions docs/index.md

This file was deleted.

4 changes: 2 additions & 2 deletions docs/trust.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,10 @@ AEA applications have different requirements for _trustlessness_ or _trust minim

For example, using the AEA <a href="../weather-skills/">weather skills demo</a> _without_ ledger payments means that the client has to trust the weather station to send the weather data it purchased and that this data is in fact valid. Similarly, the weather station must trust that the client somehow sends the payment amount to which they agreed.

A step up, if you run the <a href="../weather-skills/">weather skills demo</a> with a ledger (e.g. Fetch.ai or Ethereum) then the client must still trust that the weather station sends valid data. However, all payment transactions are executed via the public ledger. This means the weather station no longer needs to trust the client for payment and can verify whether the transactions take place on the public ledger.
A step-up, if you run the <a href="../weather-skills/">weather skills demo</a> with a ledger (e.g. Fetch.ai or Ethereum) then the client must still trust that the weather station sends valid data. However, all payment transactions are executed via the public ledger. This means the weather station no longer needs to trust the client for payment and can verify whether the transactions take place on the public ledger.

We can further minimise trust requirements by incorporating a third party as an <a href="https://en.wikipedia.org/wiki/Escrow" target="_blank">arbitrator or escrow</a> implemented in a <a href="https://en.wikipedia.org/wiki/Smart_contract" target="_blank">smart contract</a> to further reduce trust requirements. However, in the current weather skills demo, there are limits to trustlessness as the station ultimately offers unverifiable data.

Another example of minimising trust, is applications with (non-fungible) token transactions involving <a href="https://dl.acm.org/doi/10.1145/3212734.3212736" target="_blank">atomic swaps</a> where trustlessness is clearly satisfied (e.g. in the <a href="../tac-skills-contract/">TAC demo</a>).
Another example of minimising trust, is applications with (non-fungible) token transactions involving <a href="https://dl.acm.org/doi/10.1145/3212734.3212736" target="_blank">atomic swaps</a> where trustlessness is clearly satisfied in the <a href="../tac-skills-contract/">TAC demo</a>).

<br />
5 changes: 3 additions & 2 deletions mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,9 @@ theme:
strict: true

nav:
- Introduction: 'index.md'
- Introduction:
- AEA Framework core concepts:
- Trust minimisation: 'trust.md'
- Version: 'version.md'
- Upgrading: 'upgrading.md'
- Concepts:
Expand All @@ -23,7 +25,6 @@ nav:
- Application areas: 'app-areas.md'
- Relation to OEF and Ledger: 'oef-ledger.md'
- Identity: 'identity.md'
- Trust minimisation: 'trust.md'
- Demos:
- Demos: 'demos.md'
- Aries Cloud Agents Demo: 'aries-cloud-agent-demo.md'
Expand Down