oasisprotocol / oasisprotocol/oasis-sdk
Transactions de-duplication should not rely on signature determinism
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 90
- Forks
- 35
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 5
Description
Currently transactions are treated as an opaque blob, so de-duplication is done by a byte-comparison which includes the signature. While some of the supported algorithms currently happen to produce deterministic signatures, this is a bad assumption to make since not all of the supported algorithms have this property:
- sr25519 is by definition, non-deterministic
- ed25519 as specified is deterministic, but it is trivial (and sometimes beneficial to add non-determinism)
If proper de-duplication support is to be done, it is likely that a standard transaction envelope format will need to be defined.
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
No files, tests, or entry points are named. Start by locating the transaction de-duplication and signature-handling implementation, then review how supported algorithms are represented; done requires an agreed transaction envelope that permits de-duplication without relying on signature determinism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100