interfacerproject / interfacerproject/zenflows
Query and mutation to read/write agent public keys
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 18
- Forks
- 4
- Avg merge
- 7m
- Merged PRs (30d)
- 2
Description
A CRUD graphql set to read (verify that public key belongs), write (add public key) and delete (remove public key) cryptographic public keys on an agent, granted only to the agent itself (signed mutation), read-only query on public keys can be publicly available.
This can be used also at user registration to add more keys after the first one is registered (eddsa)
Client side the keys are always created in a sorted chain descending from seed.root (eddsa master key first)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; start by locating the GraphQL schema and the agent and user-registration entry points. Trace how EdDSA keys are represented and how signed mutations are authorized. Done means public-key reads work publicly, while add and delete operations are restricted to the owning agent and support the described key chain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, graphql
- Domain
- api, authentication, cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100