TD canonicalization and signing
Open
Nobody has claimed this yet.
Spec-improvement
use case
wait-for-td
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Among the objectives of the TD task force of this new charter are also the exploration of signing mechanisms and canonicalization, this is a tracking issue of that topic. If the TD task force ever formalizes these mechanisms we have to define user stories for Scripting API and extract requirements.
Generated from #352
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
No files, tests, or entry points are identified in the issue. Start by reviewing the TD task force work on signing mechanisms and canonicalization, then define the Scripting API user stories and extract requirements if those mechanisms are formalized.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100