[wbs] Response to 'Call for Review: WebExtensions Working Group Charter'

The following answers have been successfully submitted to 'Call for Review:
WebExtensions Working Group Charter' (Advisory Committee) for Ethereum
Foundation by Franziska Heintel.

Answers to this questionnaire can be set and changed until 2026-04-27 at:
  https://www.w3.org/wbs/33280/webextensions-charter-2026/

> 
> 
> 
> ---------------------------------
> Support for the proposal
> 
> ----
> In case of Formal Objection: Per section 5.5 of the W3C Process Document
> requiring that a record of each Formal Objection must be publicly
> available, we encourage your organization to make their response public.
> You may do so by setting the visibility of your response to this
> questionnaire to public. If it instead chooses to make it Member-visible,
> or Team-only, and does not provide an alternate public version, the Team
> may make the Formal Objection public without attribution, per section
> 7.3.
> My organization:
> 


 * (x) supports this Charter as is.
 * ( ) suggests changes to this Charter, but supports the proposal whether
or not the changes are adopted (your details below).
 * ( ) does not support this Charter for the reasons cited in comments but
is not raising a Formal Objection (your details below).
 * ( ) suggests changes to this Charter, and only supports the proposal if
the changes are adopted [Formal Objection] (your details below).
 * ( ) opposes this Charter and requests that this group not be created
[Formal Objection] (your details below).
 * ( ) abstains from this review.

Comments: 



> 
> 
> 
> 
> 
> ---------------------------------
> Participation
> 
> ----
> If this proposal is approved, my organization would be interested
> in
participating in the following groups. Note: This
> answer is non-binding;
after the review 
> a formal Call for Participation will be sent for each
approved charter.
> Charters include information about proposed staff
effort, which may
> be evaluated in the context of the 
> current staff
effort tables.
> 
> 


 * [ ] WebExtensions Working Group


> 
> 
> 
> 
> 
> ---------------------------------
> Support for Deliverables of the group
> 
> ----
> My organization:
> 


 * [x] intends to review drafts as they are published and send comments.
 * [ ] intends to develop experimental implementations and send experience
reports (your details below).
 * [ ] intends to develop products based on this work (your details below).
 * [ ] intends to apply this technology in our operations.

Comments: 



> 
> 
> 
> 
> 
> ---------------------------------
> Expected Implementation Schedules
> 
> ----
> If you expect to implement some deliverables of this activity, please
> indicate any known schedule for such implementations, without commitment.
> 
Comments: 



> 
> 
> 
> 
> 
> ---------------------------------
> Detailed Comments, Reasons, or Modifications
> 
> ----
> In addition to any comments you may have, please provide details about
> your answers. This may include, but is not restricted to, technical
> issues or issues associated with patent claims associated with the
> specification.
> 
Comments: 

Ethereum Foundation supports the proposed charter for the W3C WebExtensions
Working Group. The charter shows strong alignment with the Foundation’s
Trillion Dollar Security Initiative and supports essential components of
the Ethereum Access Layer. 

Browsers are a primary access layer for
decentralized applications built on
Ethereum. Browser extension wallets play a critical role in enabling users
to manage their assets, keys, and interactions with decentralized
applications. A common core of WebExtensions APIs is important to preserve
user choice across browsers while maintaining strong security and privacy
properties.


The scope of the charter is clear and relevant to the
continued development
and hardening of browser extension wallets. In particular, Extension/Web
interactions enable wallets to act as providers within web contexts,
communicating user capabilities and mediating consent. The permissions
model is therefore central to ensuring that access to sensitive
capabilities is explicit, well-scoped, and under user control.

Capabilities
such as network request modification are also important for
improving user safety, including mitigating certain classes of malicious or
unintended interactions that may otherwise result in loss of funds.
WebDriver integration supports improved testing and implementation quality
across user agents, while consistent extension capabilities simplify
deployment across browsers, enabling broader availability of wallets across
browsers and supporting user choice.

More broadly, the Working Group’s
scope is relevant to maintaining user
security and control in an evolving web environment where extensions
increasingly mediate access to identity and value.


> 
> 
> These answers were last modified on 27 April 2026 at 20:14:05 U.T.C.
> by Franziska Heintel
> 

--
The Automatic WBS Mailer

Received on Monday, 27 April 2026 20:14:06 UTC