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

Account API #140

Closed
3 of 4 tasks
Tracked by #117
l1h3r opened this issue Mar 1, 2021 · 1 comment · Fixed by #544
Closed
3 of 4 tasks
Tracked by #117

Account API #140

l1h3r opened this issue Mar 1, 2021 · 1 comment · Fixed by #544
Assignees
Labels
Enhancement New feature or improvement to an existing feature
Milestone

Comments

@l1h3r
Copy link
Contributor

l1h3r commented Mar 1, 2021

Add an API for managing Identity-related data

TODO

  • Add an optional background-sync process
  • Add automatic auth-chain publishing
    • Ability to change publish threshold
    • Ability to publish with/without key change
@l1h3r l1h3r added Enhancement New feature or improvement to an existing feature account labels Mar 1, 2021
@l1h3r l1h3r self-assigned this Mar 1, 2021
@l1h3r l1h3r mentioned this issue Mar 1, 2021
3 tasks
@JelleMillenaar JelleMillenaar added this to the Account Module milestone Mar 11, 2021
@l1h3r l1h3r mentioned this issue May 7, 2021
@JelleMillenaar
Copy link
Collaborator

@HenriqueNogara Can you check the state of the above mentioned features and if they exist or not?

To further clarify them:

Add an optional background-sync process

If an identity is updated on another device / program, the account should be able to update its internal DID Document to the latest by querying the Tangle (Resolving the Identity) for the latest state and comparing it to its own state. If it is behind, update the internal state. @cycraig and I also recently discussed this, so perhaps he can also provide some thoughts on this topic.

Add automatic auth-chain publishing

Right now, we have integration chain (previously called auth chain) and diff chain messages that a developer could use, but they have too chose themselves. The account should start to make these decisions for the developer instead. Putting new updates in diff messages, unless the diff chain has become to long (variable that the developer can set, lets default to 100).

Ability to change publish threshold

Thats the variable I just mentioned ;D

Ability to publish with/without key change

It is illegal to change the signing key within a diff chain. If the developer tries to do this, the account should automatically make it a integration chain update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or improvement to an existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants