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

Adding and maintaining own Gestalt in Gestalt Graph #319

Closed
emmacasolin opened this issue Jan 21, 2022 · 2 comments · Fixed by #446
Closed

Adding and maintaining own Gestalt in Gestalt Graph #319

emmacasolin opened this issue Jan 21, 2022 · 2 comments · Fixed by #446
Assignees
Labels
development Standard development discussion Requires discussion r&d:polykey:core activity 3 Peer to Peer Federated Hierarchy

Comments

@emmacasolin
Copy link
Contributor

Specification

Currently, the gestalt graph does not contain your own gestalt, however, this incorrect. We need a proper review of the Gestalt Graph theory and implement the expected behaviour.

Additional context

Tasks

  1. Full review of Gestalt Graph theory and gestalt trust
  2. Add bootstrapped node to gestalt graph during bootstrapping
  3. Incorporate Gestalt Graph into Node and Identity claiming process (including revoked/expired/invalid claims)
@CMCDragonkai
Copy link
Member

This is now done by #446. The identities domain and nodes domain both manage the own gestalt graph. The discovery does not manage this.

The only thing missing is that the GG should have setNode called at the beginning of PolykeyAgent startup so that way the GG always has its own node there as a vertex. This should be done in #446 too.

@CMCDragonkai
Copy link
Member

At the same time, the Discovery should be starting off from the GG but to do this we will need to introduce push-based dataflow to get the Discovery to react to changes in GG.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Standard development discussion Requires discussion r&d:polykey:core activity 3 Peer to Peer Federated Hierarchy
Development

Successfully merging a pull request may close this issue.

4 participants