Encode fee field more efficiently
Open
Nobody has claimed this yet.
Consensus
- Dominant language
- C++
- Stars
- 22
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
The fee field in kernels is currently 8 bytes, but a more compact encoding could bring that down to 2-4.
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.
Research direction
Start by locating the fee field in kernel encoding and inspect how its current 8-byte representation is serialized. Determine a compact encoding that supports the required fee values, then verify that kernels use 2–4 bytes without losing correctness.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100