Docs: encrypted-at-rest content can't be semantically searched server-side (relayer embeds what it receives)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation, search, security
Research direction
Start by locating the encryption and recall documentation mentioned in the issue and review how each currently describes server-side embeddings. Document that encrypted payloads cannot be semantically searched by the relayer, while preserving the longer-term client-side or local-embedding idea as future work. Done means the tradeoff is explicit and the surprise is addressed.
Written by the indexing model from the issue text.
Description
Problem
The relayer generates embeddings from the bytes it receives. If a client encrypts payloads before sending them (encryption at rest, so the relayer never sees plaintext), the relayer embeds ciphertext, and server-side semantic recall no longer works. In practice you pick one: encryption at rest, or server-side semantic search — not both. We fell back to lexical ranking over transiently-decrypted plaintext in our own layer.
This is a reasonable consequence of the trust model, but it is not stated anywhere, and it is a surprise if you assumed both were available together.
Ask
- Document the tradeoff explicitly in the encryption / recall docs.
- Longer term: a client-side or local-embedding path so integrators can keep payloads encrypted at rest and still rank semantically.
- Dominant language
- TypeScript
- Stars
- 107
- Forks
- 37
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 101
Contributor guide
No contributing guide indexed for this repository
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.
More from MystenLabs/MemWal
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
MystenLabs/MemWal#799 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MystenLabs/MemWal#708 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MystenLabs/MemWal#691 · 1 comment ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
MystenLabs/MemWal#686 · 2 comments ·
-
Difficulty 2/5 1-2 days Newbie friendliness 74/100
MystenLabs/MemWal#462 · 1 comment ·
All issues in MystenLabs/MemWal
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100