graphprotocol / graphprotocol/hypergraph
Updates must be connected to a space event
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
This is important to ensure that the client has all the latests keys before decrypting it.
In addition we want to ensure that the server can't inject an update from an already remove member as a new update. To do this new encrypted updates can only reference the current or newer space events. Using the clock and the references we can check for this rule.
The information should be stored in the AAD (additional authenticated data) of the AEAD ciphertext. This way also the server can verify it's correctness and reject old updates in case a newer space event already exist.
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
No files or tests are named; start by locating the TypeScript code that creates encrypted updates and handles space-event clocks and references. Confirm how AAD is constructed and define tests showing updates reference the current or newer space event, while older or removed-member updates are rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100