oasisprotocol / oasisprotocol/oasis-core
RPC request/response size padding
Open
Nobody has claimed this yet.
c:runtime/compute
p:3
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Not a priority now, but we may want to consider some standard message size to avoid leaking information about the RPC calls.
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, tests, or entry points. Start by locating the RPC request and response encoding path, then clarify the target standard size and information-leakage criteria; done requires an agreed padding behavior and tests covering it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100