Repository navigation
Conversation
Collaborator
File
|
Added ndavd as a co-author to the draft document.
abcoathup
reviewed
Apr 30, 2026
abcoathup
reviewed
Apr 30, 2026
Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
Added Zefram Lou as an author to the document.
feat: add registry interface to contract hosted app
hilljessica8787-dot
approved these changes
Jul 2, 2026
|
the file |
Incorporates review feedback from wighawag on the ethereum-magicians thread: Subresource Integrity for external resources, EIP-6963 provider discovery, and isolation stated as a property rather than prescribing an iframe.
Keeps the relaxations from PR #2 (SRI, EIP-6963 discovery, isolation as a property rather than a prescribed iframe) while retaining as normative the requirements that carry the proposal's trust guarantees: - renderer MUST treat the document as untrusted code - client MUST provide isolation equivalent to a sandboxed iframe - client MUST gate every signing request through wallet confirmation - document MUST be able to identify its origin contract - restore a network constraint, framed around integrity rather than a blanket prohibition, so SRI-pinned and content-addressed fetches remain possible Also links EIP-6963 on first mention, as required by the markdown-link-first lint.
ndavd
approved these changes
Jul 19, 2026
The Abstract claimed no off-chain hosting is involved, which no longer held once integrity-checked external resources were permitted. It now states that off-chain hosting is not required and that any external resource is integrity-checked, preserving the single-trust-domain claim. Also documents coexistence with ERC-5219 in Backwards Compatibility, answering an open question from the discussion thread.
Contributor
Author
|
requesting review ~~ |
This was referenced Aug 3, 2026
4 tasks done
lightclient
approved these changes
Nov 14, 2026
lightclient
left a comment
lightclient
left a comment
Member
There was a problem hiding this comment.
This is a cool idea! LGTM
lightclient
enabled auto-merge (squash)
November 14, 2026 10:25
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This proposal introduces a view-only interface (
html()) for a contract to serve its own self-contained HTML dapp. Thus the dapp lives in the same trust domain as its bytecode.