Darryl Yeo

Reverting all proposed normative changes to avoid restarting the Last Call period.

> there are some left, but I consider these as breaking changes. @glitch-txs As I understand it, this spec is defining JavaScript functionality; the TypeScript syntax is used illustratively, so...

> Also, we shouldn't assume that just because a change is non normative that it doesn't matter. The implications of subtle interpretation differences can be profound. Especially when making changes...

Update: "EIP-1193 Provider Objects" are now front and center with a dedicated definition. Also reverted some prescriptive language related to browser extensions, as they are not the only way Wallet...

If it helps people read the code diff more easily — my revisions stem from using the **four terms under the "Definitions" section** as consistently as possible. If anyone strongly...

> I think we should keep the previous name for types. Imo it is a breaking change since most of us use typescript and have this EIP as reference/source of...

* [viem's wallet client](https://viem.sh/docs/clients/wallet) is the best out-of-the-box library for EIP-1193 interactions, and it also [supports EIP-5792](https://viem.sh/docs/actions/wallet/sendCalls). Might be worth diving into the source code for how it handles edge...

Would love to have this as well – was wondering why the existing `pnpm.overrides` syntax didn't work for me, until I realized I was trying to override a _peer_ dependency...

Just saw that last comment – pretty clever, but I still think having a well-defined list of string keys is better than coupling string templates to arbitrarily deeply nested object...

Will be updating `` to have a more intuitive column-level `Snippet` option shortly. Once that's in, `WalletTable.svelte` would be the place to make this change.