multiformats / multiformats/multicodec
Keyed hashes (SipHash)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 383
- Forks
- 221
- Avg merge
- 24d 6h
- Merged PRs (30d)
- 1
Description
Basically, a widely used hash function ( at least internally in software ) is SipHash, which needs a key to be verified is missing from the codec table.
I have a use case that would require a hash-function that produces small digests ( ideally max 32bits ) for IoT usecases.
The recommended parameters are SipHash-2-4 for best performance, and SipHash-4-8 for conservative security. A few languages use Siphash-1-3. (from Wikipedia )
Is there anything that prohibits this from being added in multicodec? In this case I suppose it will not, but for my intended usecase, I suspect that maybe it will be problematic in for example multihash
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 with the multicodec codec table and the multihash concerns named in the issue. Determine whether keyed SipHash variants, including SipHash-2-4 and SipHash-4-8, can be represented and what limitations apply to small digests; done means a documented decision on whether and how to add them.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100