potentially conflicting text about binding credentials in a batch to different keys
Open
Nobody has claimed this yet.
certification
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
When doing batches of credentials, §8.3 says:
Each key provided by the Wallet is used to bind to, at most, one Credential
While §3.3.2 says the batch:
SHOULD contain different Cryptographic Data
The first sounds like a 'must', is there a situation where it becomes only a 'recommendation' (should) as per the second?
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 by reading §§8.3 and 3.3.2 together, including their surrounding definitions and normative language. Check whether the two statements address different batch conditions or conflict directly. Done means the relationship is resolved and the specification wording makes the requirement unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100