Add a section on Phone Home mitigations
Open
Nobody has claimed this yet.
ready for pr
- Dominant language
- HTML
- Stars
- 9
- Forks
- 8
- Avg merge
- 14d 42m
- Merged PRs (30d)
- 2
Description
For a given renderMethod template, a publisher has to make the usual engineering trade-off: link to it, or embed it?
Linking to a template -- space efficient, BUT phone-home possibility.
Embedding a template -- secure, but dramatically increased VC size (depending on size, may have parsing issues on mobile platforms).
Discuss possible mitigation methods:
- Does compression (gzip + text-encode) help any?
- Common template URLs (especially with digest hashes) can be cached by wallets
- Trusted cached directories of templates
- etc
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 target file, test, or documentation entry point is named. Start by reviewing the renderMethod linking-versus-embedding trade-off and the listed mitigation questions, then document the relevant options and their effects on VC size, parsing, caching, and phone-home risk.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100