Support OutputMessage versioning
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 25
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Support versioning for `OutputMessage`s:
https://github.com/ltc-mweb/litecoin/blob/4c42bd77af510b157fb62d7a07a318c855f2d610/src/libmw/include/mw/models/tx/Output.h#L21
to allow different encoding formats and the ability to softfork in additional features.
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
Start with src/libmw/include/mw/models/tx/Output.h, especially the OutputMessage definition referenced by the issue. Trace how OutputMessages are encoded and consumed, then clarify the required version formats and softfork behavior before implementation. Done means versioned OutputMessages support the agreed encoding formats and allow the specified additional features.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100