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/identity/proof-of-representation #2838

Open
wants to merge 3 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
15 changes: 0 additions & 15 deletions docs/identity.md

This file was deleted.

62 changes: 0 additions & 62 deletions docs/index.md

This file was deleted.

3 changes: 1 addition & 2 deletions docs/por.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@

An AEA can use several key pairs. In particular, it can use different keys for securing its communication and for engaging in exchange. In the ACN we make use of this fact. To be able to signal to other agents that the address derived from one key pair is allowed to represent the agent controlling the other key pair, the key pair which is being represented must sign a message to prove that the other key pair is allowed to represent it. The `aea issue-certificates` command allows to create this association.

The proof of representation feature is used in the context of the `fetchai/p2p_libp2p` and `fetchai/p2p_libp2p_client` connection.
Expand All @@ -18,4 +17,4 @@ cert_requests:

The `identifier` refers to the environment for which the signature is generated, here `acn`. The `ledger_id` refers to the key pair to be used from the `private_key_paths` specified in `aea-config.yaml` for signing. The `not_after` and `not_before` fields specify constraints on the validity of the signature. The `public_key` can specify either the identifier of the key pair in `connection_private_key_paths` of which the public key is signed or it can contain the to be signed public key in plain text. The `save_path` specifies the path where the certificate is to be saved at.

In the above example, the connection requests a certificate which is a signature of the `fetchai` public key in `connection_private_key_paths` with the `fetchai` key pair in `private_key_paths`. The validity of the signature will be constrained to the year `2021` for the environment `acn`.
In the above example, the connection requests a certificate which is a signature of the `fetchai` public key in `connection_private_key_paths` with the `fetchai` key pair in `private_key_paths`. The validity of the signature will be constrained to the year `2021` for the environment `acn`.
7 changes: 4 additions & 3 deletions mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,10 @@ theme:
strict: true

nav:
- Introduction: 'index.md'
- Introduction:
- AEA Framework core concepts:
- Identity:
- Proof of Representation: 'por.md'
- Version: 'version.md'
- Upgrading: 'upgrading.md'
- Concepts:
Expand All @@ -22,7 +25,6 @@ nav:
- Vision: 'vision.md'
- Application areas: 'app-areas.md'
- Relation to OEF and Ledger: 'oef-ledger.md'
- Identity: 'identity.md'
- Trust minimisation: 'trust.md'
- Demos:
- Demos: 'demos.md'
Expand Down Expand Up @@ -70,7 +72,6 @@ nav:
- Multi agent manager: 'multi-agent-manager.md'
- Debugging: 'debug.md'
- Profiling: 'runtime-cost.md'
- Proof of Representation: 'por.md'
- Security: 'security.md'
- Architecture & component deep-dives:
- Design principles: 'design-principles.md'
Expand Down