ElementsProject / ElementsProject/elements
reissuance tokens can not be exercised from unblinded outputs
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 416
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 15
Description
In the current logic, `CAssetIssuance`'s `assetBlindingNonce` being null implies that the issuance is an initial issuance. When re-issuing, this field is re-used to expose the asset blinder for the spent output.
Clearly this is in direct conflict when the output itself has a null blinder.
If the user attempts to make a reissuance with the null blinder output, it will be interpreted as an initial issuance, using the reissuance token purely as the entropy.
Contributor guide
Research direction
Start by tracing CAssetIssuance::assetBlindingNonce through the issuance and reissuance logic described in the issue, focusing on the null-blinder case. Identify the relevant validation tests and establish behavior that distinguishes a reissuance from an initial issuance when the spent output has a null blinder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100