Wallet Test Framework – `94f9943cea81ccb8a3456ec031ad1bd00ee9a1f6</code> </a>https://github.com/wallet-test-framework/framework </a> </p>`
`Not a statement of a wallet's quality or correctness.</em> </p> </caption>`
Wallet</th>	Automated</th>	Version</th>	Passing Tests</th>	Pass %</th>	Platform</th>	Notes</th> </tr> </thead>
Brave Wallet</th>	❌</td>	</td>	61</td>	100%</td>	Brave v1.63.16</td>	</td> </tr>
Frame</th>	❌</td>	0.6.8</td>	60</td>	98%</td>	Chromium 120.0.6099.129</td>	signTransaction unsupported</td> </tr>
Taho</th>	✔️</td>	0.57+</a> </td>	60</td>	98%</td>	Chrome 122.0.6261.94</td>	Changed definition of sign test to exclude hex</td> </tr>
Enkrypt</th>	❌</td>	1.33.0</td>	59</td>	97%</td>	Chrome 122.0.6261.94</td>	signTransaction unsupported, doesn't show destination address</td> </tr>
Rainbow</th>	❌</td>	1.4.8</td>	56</td>	92%</td>	Chrome 122.0.6261.94</td>	signTransaction opened, but was blank</td> </tr>
Backpack</th>	❌</td>	0.10.37</td>	56</td>	92%</td>	Chrome 122.0.6261.94</td>	sendTransaction invalid length, sign just closed</td> </tr>
Opera Wallet</th>	❌</td>	</td>	56</td>	92%</td>	Opera 107.0.5045.36</td>	Doesn't update balance before sending</td> </tr>
Coin98</th>	❌</td>	9.1.6</td>	55</td>	90%</td>	Chrome 122.0.6261.94</td>	Doesn't display full addresses</td> </tr>
Aurox</th>	❌</td>	2.0.0</td>	53</td>	87%</td>	Chrome 122.0.6261.94</td>	</td> </tr>
Metamask</th>	❌</td>	11.10.1</td>	48</td>	79%</td>	Chromium 120.0.6099.129</td>	signTransaction unsupported, logging/storage seems to lag behind chain</td> </tr>
Coinbase</th>	✔️</td>	3.57.0</td>	47</td>	77%</td>	Chromium 120.0.6099.129</td>	Doesn't show full addresses, can't differentiate sign/send transaction</td> </tr>
TokenPocket</th>	❌</td>	1.2.4</td>	46</td>	75%</td>	Chrome 122.0.6261.94</td>	signTransaction unsupported</td> </tr>
xdefi</th>	❌</td>	<28.3.6</td>	45</td>	74%</td>	Chrome 122.0.6261.94</td>	Notably different signTransaction behaviour</td> </tr>
Trust</th>	❌</td>	2.7.2</td>	43</td>	70%</td>	Chrome 122.0.6261.94</td>	Doesn't support filters/subscriptions</td> </tr>
BlockWallet</th>	❌</td>	1.2.4</td>	40</td>	66%</td>	Chrome 122.0.6261.94</td>	</td> </tr>
OKX</th>	❌</td>	2.85.0</td>	22</td>	36%</td>	Chromium 120.0.6099.129</td>	As likely to be a bug in WTF as a wallet problem</td> </tr> </tbody> </table> </div> Disclaimer🔗</a></h3> Our intent is not to claim that certain wallets are better than others, and a low score here is as likely to indicate that our tests have problems as it is to indicate bugs in a wallet. We're very interested in improving scores across the board, so we're happy to accept contributions to fix tests and just as happy to help debug.</p> Wallet Selection 🔗</a></h3> Very little of this report is scientific/rigorous, and the wallet selection process was no exception. We chose a few wallets we're familiar with, and a small sampling of random wallets from the Find an Ethereum Wallet</a> list.</p> Because Wallet Test Framework only supports `window.ethereum</code> so far, we're limited to wallets that provide it; that pretty much excludes mobile wallets for the time being. Ourarchitecture</a> requires connecting to a custom chain, so wallets that don't support custom chains cannot be tested (omitted from this table.)</p>` `For future reports, get in touch if you're interested in having your results published (or if you'd prefer we didn't mention you.)</p>` Discussion🔗</a></h3> Automation🔗</a></h4> The most exciting part of this Test Report is the new "Automated" column. Wallets with a "✔️ " (currently Taho and Coinbase) use the newest feature of WTF, custom glue. Both of these wallets use [Selenium WebDriver]-based automation to interact with their user interface to respond to prompts, like connecting or signing transactions.</p> Automating wallets is the first step in our plan—removing humans from the process means the tests can run unattended and regularly. Next, we plan to build a reporting platform to track results over time and highlight regressions.</p> Here's what Taho looks like running the tests:</p> Demo video of Taho with automation.</p> </video> </a> Common Issues🔗</a></h4> There are several issues that are hurting scores that we see across wallets: incomplete information, unsupported features, minor deviations from the JSON-RPC specification, and out-of-date information.</p> Far too many wallets (like Enkrypt, Coin98, etc.) do not display the source or destination address when preparing a transaction. Commonly wallets will display an abbreviated address (0xabcd...1234</code>) and provide no way to view the full value. This is a security issue, since it is relatively easy to mine addresses that collide on only four bytes. Always provide a way to access the full value, like in a tooltip or a "copy" button.</p> Perhaps following MetaMask's lead, many wallets do not support the eth_signTransaction</code> endpoint. Some other wallets do not support subscriptions. While adding support for these features is nontrivial, it is important to provide the same base level of functionality.</p> In other cases, wallets do provide a feature but do not follow the specification. Coinbase, for example, omits the 0x</code> prefix on hexadecimal log results and xdefi implements a very different eth_signTransaction</code>. Having to work around these differences increases the burden on dapp developers.</p> Finally, there is a whole class of bugs related to out-of-date information being presented to the user. For example, Opera Wallet does not refresh balance information while authorizing a transaction, preventing the user from completing a transaction that would otherwise succeed.</p> Conclusion🔗</a></h3> That's pretty much it for this Test Report. In the meantime, join us on Discord</a>!</p> Year in Review (2023) Unknown — Fri, 08 Dec 2023 00:00:00 +0000 Guess we failed pretty spectacularly in keeping up with the biweekly updates. Oh well.</p> This post covers everything we've accomplished so far this year, and what we're planning for next year.</p> Year in Review🔗</a></h2> We began our year by rewriting our prototype for Wallet Test Framework in TypeScript, to be more accessible to wallet developers. The original implementation was half TypeScript and half Rust, and without a specific reason to use Rust, we felt it more consistent to use TypeScript for everything. Around this time, we also migrated to the Mocha testing framework.</p> Soon after, we set up our continuous integration pipeline to deploy the framework to Heroku, making it easier to play with without having to build it. We simplified the backend, and created scaffolding for glue implementations.</p> After some bug fixes and new tests, we migrated from ethers to viem, due to some caching issues. We also introduced support for remote controlling wallets over WebSockets.</p> After publishing our first Test Report</a>, we moved full steam into developing automation glue for Coinbase and Taho wallets. We've proven that our tests are portable between wallets, and we've reported a handful of issues upstream.</p> After a fairly successful first year, we're really looking forward to 2024!</p> Roadmap for 2024🔗</a></h2> Mobile Wallets🔗</a></h3> Our top priority for the upcoming year is to broaden our support for wallets, especially mobile. Wallet Test Framework currently depends on window.ethereum</code>, pretty much limiting us to browser extension wallets. To better support the Ethereum community, we need to integrate technologies like WalletConnect</a>, EIP-6963</a>, and vendor-specific SDKs.</p> Documentation & Collaboration🔗</a></h3> Wallet Test Framework is only useful if it is run, and can only find bugs for areas it tests. Our second goal for 2024 is to write documentation for wallets, EIP authors, and security experts so that they can all use and contribute easily to the project.</p> We plan to write integration guides and documentation for wallets to make it as easy as possible to run WTF as part of testing pipelines. This will cover topics like writing the automated glue and adding vendor-specific tests.</p> Our biggest strength is that once a test is written, it's available to every wallet using the framework. To take full advantage, we need to make it as easy as possible for anyone—be it wallets themselves, EIP authors, or complete outsiders—to write WTF tests. Documenting the test-writing process and having clear guidelines for contributions are necessary to accomplish that goal.</p> Transaction Decoding🔗</a></h3> This might be a bit of a stretch goal, but we'd like to start testing how wallets decode the transactions of some popular applications. This is a wide attack surface with plenty of room for quality assurance.</p> EIP-1193</a> Events🔗</a></h3> EIP-1193</a> defines several events (like connect</code> or accountsChanged</code>) that aren't covered by the current tests. Emitting these events is essential for responsive application development, so we'd like to expand our coverage in this area.</p> Account Abstraction Wallets🔗</a></h3> The world of account abstraction wallets has exploded since the introduction of ERC-4337</a>. We'd like to explore expanding our tests to cover them.</p> Statistics & Reporting🔗</a></h3> We'd like to develop a dashboard showing the scores of wallets over time, as well as automation implementation status, and enabled test suites. These statistics will allow us to gauge how much of an impact Wallet Test Framework has on the ecosystem.</p> Supporters🔗</a></h2> We want to give a huge thank you to the Ethereum Foundation's Ecosystem Support Program and to the donors on Gitcoin for helping to fund our work so far. We'd also like to thank Coinbase for being very supportive and responsive when reporting issues.</p> WTF News (Week 19) Unknown — Fri, 18 Aug 2023 00:00:00 +0000 Hello and welcome to issue number nine of WTF News, our biweekly status update.</p> Over the last two weeks, we ran a handful of wallets through their paces, and today we can reveal the results! Spoiler alert, but there were more issues in our tests than in the best scoring wallets.</p> First, the regular status update!</p> Call to Action🔗</a></h2> CI/Build Pipelines🔗</a></h3> What good is a testing framework if it isn't used? Get in touch if you want to integrate WTF into your wallet's testing pipeline. We'll even build the automation ourselves!</p> Testing the Tests🔗</a></h3> We want to expand our tests for WTF, to catch issues with the framework itself. To that end, if you work on a wallet that works offline (aside from the RPC provider) and want to try out WTF, get in touch with us!</p> Code Changes🔗</a></h2> Upgraded to viem 1.6</a>!</li> </ul> Bug Fixes🔗</a></h2> Use smaller integers to make ganache happy</a>.</li> Send WebSocket pings to keep the connection alive</a>.</li> Use from</code> instead of account</code> in eth_signTransaction</code></a>.</li> Use hex instead of decimal in eth_signTransaction</code></a>.</li> Convert BigInt</code> to hex in eth_getProof</code></a>.</li> Actually put jsonrpc</code> in responses to the wallet</a>.</li> Handle race condition when falling back to adding a chain manually</a>.</li> </ul> Upstream Issues🔗</a></h2> eth_call</code> unclear when Block</code> parameter is omitted</a>.</li> </ul> Test Report🔗</a></h2> Summary🔗</a></h3> Wallet Test Framework – f999503092a10f2b409b5cc733db065c124e56e5</code> </a> https://github.com/wallet-test-framework/framework </a> </p> Not a statement of a wallet’s quality or correctness.</em> </p> </caption> Wallet</th> Version</th> Connection</th> Passing Tests</th> Pass %</th> Platforms</th> Browser</th> Notes</th> </tr> </thead> Brave Wallet</th> </td> EIP-3085</td> 61</td> 100%</td> Browser</td> Brv 1.57.42</td> </td> </tr> Taho</th> 0.46.1</td> EIP-3085</td> 61</td> 100%</td> Extension</td> Chr 115.0.5790.170</td> Had to impersonate chainlist.org</td> </tr> Frame</th> 0.6.7</td> EIP-3085</td> 60</td> 98%</td> Desktop</td> Ff 102.14.0esr (64-bit)</td> Missing signTransaction</td> </tr> Enkrypt</th> 1.24.0</td> Manual</td> 59</td> 97%</td> Extension</td> Ff 102.14.0esr (64-bit)</td> Attempted EIP-3085, but popup doesn’t show RPC url</td> </tr> Coinbase</th> 3.30.2</td> EIP-3085</td> 48</td> 79%</td> Extension</td> Chr 115.0.5790.170</td> Missing hex prefix in logs</td> </tr> Metamask</th> 10.34.0</td> EIP-3085</td> 48</td> 79%</td> Extension</td> Ff 102.14.0esr (64-bit)</td> </td> </tr> OKX</th> 2.58.1</td> EIP-3085</td> 18</td> 30%</td> Extension</td> Chr 115.0.5790.170</td> Tests stopped running somewhere around getFilterChanges</td> </tr> TokenPocket</th> 1.1.19</td> EIP-3085</td> 15</td> 25%</td> Extension</td> Chr 115.0.5790.170</td> Tests stopped running somewhere around getFilterChanges</td> </tr> Argent X</th> 5.7.2</td> Can’t Connect</td> 0</td> 0%</td> Extension</td> Chr 115.0.5790.170</td> No window.ethereum</td> </tr> Bitkeep</th> 1.4.8</td> Can’t Connect</td> 0</td> 0%</td> Extension</td> Chr 115.0.5790.170</td> Attempted EIP-3085, and Manual, but got system error</td> </tr> Sequence</th> 2.0.4</td> Can’t Connect</td> 0</td> 0%</td> Extension</td> Chr 115.0.5790.170</td> Cannot add custom chains</td> </tr> Exodus</th> 23.8.14</td> Can’t Connect</td> 0</td> 0%</td> Extension</td> Chr 115.0.5790.170</td> Cannot add custom chains</td> </tr> </tbody> </table> </div> The astute reader may notice that there are in fact 62 tests in the repository at that commit. Our eth_getProof</code> test is broken, and we are excluding it from this report.</p> Disclaimer🔗</a></h3> Our intent is not to claim that certain wallets are better than others, and a low score here is as likely to indicate that our tests have problems as it is to indicate bugs in a wallet. We're very interested in improving scores across the board, so we're happy to accept contributions to fix tests and just as happy to help debug.</p> Wallet Selection🔗</a></h3> Very little of this report is scientific/rigorous, and the wallet selection process was no exception. We chose a few wallets we're familiar with, and a small sampling of random wallets from the Find an Ethereum Wallet</a> list.</p> Because Wallet Test Framework only supports window.ethereum</code> so far, we're limited to wallets that provide it; that pretty much excludes mobile wallets for the time being. Our architecture</a> requires connecting to a custom chain, so wallets that don't support custom chains cannot be tested (labelled with Can't Connect</code> in the table.)</p> For future reports, get in touch if you're interested in having your results published (or if you'd prefer we didn't mention you.)</p> Discussion🔗</a></h3> Congratulations to Brave</a> and Taho</a> for getting perfect scores! Considering this was our first time trying them out with the Framework (we've been using Frame</a> to develop), this was quite surprising.</p> eth_signTransaction</code>🔗</a></h4> This is a contentious endpoint that we've discussed previously</a>. Very few wallets support eth_signTransaction</code>, mostly by choice.</p> Interestingly, this was Frame's only failure: instead of signing in the wallet, Frame passes these requests through to the RPC provider.</p> Caching🔗</a></h4> There are only two hard things in Computer Science: cache invalidation and naming things. Phil Karlton</em></p> </blockquote> Caching is hard. We've been bitten by it</a>. In a space where you have to pay for every API request, but your users expect a free wallet experience, caching is a necessary evil.</p> We suspect, but haven't verified for all wallets, that many of the test failures are caused by stale values cached by wallets.</p> In the case of eth_call</code>, we have verified that MetaMask specifies an old block number, causing a call into a freshly deployed contract to fail. This is unlikely to cause major issues on a real network with many seconds between blocks, but the tests mine blocks much more frequently, triggering the issue. Regardless, we're following up with their team to see what we can do.</p> Post-merge Endpoints🔗</a></h4> Some of the newer endpoints like eth_maxPriorityFeePerGas</code> aren't yet supported in all wallets. Expect these tests to start passing as they are implemented.</p> Stalled Tests🔗</a></h4> OKX</a> and TokenPocket</a> both failed somewhere around the eth_getFilterChanges</code> suites, and didn't continue to the rest of the tests. It's likely that they would've passed more tests had they continued.</p> We haven't debugged why the tests stalled. It could be as simple as adding a timeout to WTF, or something more involved. We'll be looking into this before the next report.</p> Future Plans🔗</a></h3> We'll continue adding tests, and we'll try to run through this report somewhat regularly. That said, this is entirely a manual process. Once wallets start running WTF as part of their continuous integration processes, we can make some pretty graphs, include more wallets, and make reports more often.</p> In the meantime, join us on Discord</a>!</p> WTF News (Week 17) Unknown — Fri, 04 Aug 2023 00:00:00 +0000 Hello and welcome to issue number eight of WTF News, our biweekly status update.</p> We missed last update (sorry about that), but we're back with more tests than ever!</p> Demo video of an eth_sendTransaction</code> test.</p> </video> </a> Call to Action🔗</a></h2> CI/Build Pipelines🔗</a></h3> What good is a testing framework if it isn't used? Get in touch if you want to integrate WTF into your wallet's testing pipeline. We'll even build the automation ourselves!</p> Testing the Tests🔗</a></h3> We want to expand our tests for WTF, to catch issues with the framework itself. To that end, if you work on a wallet that works offline (aside from the RPC provider) and want to try out WTF, get in touch with us!</p> Code Changes🔗</a></h2> Upgraded to ganache 7.9</a>!</li> </ul> New Tests🔗</a></h2> eth_accounts</code> returns properly formatted hex strings</a>.</li> eth_createAccessList</code> passes through value from ganache</a> (skipped</a>.)</li> eth_getProof</code> works for EOAs and contract storage</a>.</li> eth_call</code> can invoke a function and return the result</a>.</li> eth_getLogs</code> respects block number and source address when returning blocks</a>.</li> eth_maxPriorityFeePerGas</code> passes through value from ganache</a>.</li> eth_sendRawTransaction</code> publishes transactions on-chain</a>.</li> eth_gasPrice</code> passes through value from ganache</a>.</li> eth_estimateGas</code> passes through value from ganache</a>.</li> eth_feeHistory</code> passes through value from ganache</a>.</li> eth_sendTransaction</code> encodes call data to contracts</a>.</li> </ul> WTF News (Week 12) Unknown — Sun, 09 Jul 2023 00:00:00 +0000 Hello and welcome to issue number seven of WTF News, our biweekly status update.</p> This release introduces the first interactive tests, and our first major inconsistencies between wallets: eth_sign</code> and eth_signTransaction</code>.</p> Some wallets have treated eth_sign</code> as a "sign raw data" operation, while others implement it as "sign prefixed text", while still others disable it entirely. Similarly, eth_signTransaction</code> is often not supported at all.</p> For these cases, we've chosen to test for the behaviour specified in the JSON-RPC</a> specification and treat anything different as a test failure.</p> Call to Action🔗</a></h2> We want to expand our tests for WTF, to catch issues like last update's connection issue. To that end, if you work on a wallet that works offline (aside from the RPC provider) and want to try out WTF, get in touch with us!</p> Code Changes🔗</a></h2> Support for signing messages</a> and sending transactions</a> in the glue.</li> </ul> New Tests🔗</a></h2> eth_sign</code> creates a valid signature with prefix</a>.</li> eth_sendTransaction</code> creates and publishes a transaction</a>.</li> </ul> WTF News (Week 11) Unknown — Mon, 26 Jun 2023 00:00:00 +0000 Hello and welcome to issue number six of WTF News, our biweekly status update.</p> Over the last two weeks, we've begun to focus on tests involving UI interaction, like eth_sendTransaction</code> and on the initial steps toward automating wallets.</p> Code Changes🔗</a></h2> Implement connecting to glue over WebSockets</a>. If you navigate to URLs of the form https://127.0.0.1:3000/#glue=ws://127.0.0.1:3001/</code>, the tests will attempt to open a WebSocket connection to 127.0.0.1:3001</code> and issue commands to a glue instance there. The code is of prototype quality, and there is no documentation yet. For the adventurous, see the tests in wallet-test-framework/glue-ws</a> for the gory details.</li> </ul> Bug Fixes🔗</a></h2> During the transition to viem, we broke establishing the initial connection, so we fixed it</a>.</li> @wallet-test-framework/glue</code> didn't have any exports for Node</a>.</li> </ul> Upstream Issues🔗</a></h2> Incorrect type bounds for register</code> (elpheria/rpc-websockets#139</a>.)</li> </ul> WTF News (Week 9) Unknown — Fri, 09 Jun 2023 00:00:00 +0000 Hello and welcome to issue number five of WTF News, our biweekly status update.</p> Since our last post, we've settled on viem</a> for the time being. It fixed our caching issues, and has excellent TypeScript support!</p> Code Changes🔗</a></h2> Migrate from ethers to viem</a>.</li> Pass errors from Ganache over postMessage</code></a> then the WebSocket</a>.</li> Increase the slow test timeout</a>.</li> Disable minify by default</a>. Now test source code is understandable in Mocha's HTML output!</li> </ul> New Tests🔗</a></h2> eth_getTransactionCount</code> for contract accounts</a>.</li> eth_getCode</code> returns the contract's bytecode</a>.</li> eth_newBlockFilter</code> returns new blocks</a>.</li> eth_getStorageAt</code> can read contract storage</a>.</li> eth_getTransactionByBlockHashAndIndex</code></a> and eth_getTransactionByBlockNumberAndIndex</code></a> get transactions.</li> eth_getTransactionReceipt</code></a> can get receipts.</li> A whole</a> lot</a> of filter tests</a>.</li> </ul> Upstream Issues🔗</a></h2> Ganache returns null</code> from several endpoints, and it's unclear if that's allowed in the specification (ethereum/execution-apis#288</a>.)</li> Getting transactions by index beyond the end of the block throws an exception (trufflesuite/ganache#4435</a>.)</li> </ul> WTF News (Week 7) Unknown — Fri, 26 May 2023 00:00:00 +0000 Hello and welcome to issue number four of WTF News, our biweekly status update.</p> This time around we've mostly focused on trying out alternatives to ethers</a>. After wrestling with eth_blockNumber</code> not returning the latest block number, and other similar caching issues, we decided it would be best to try out a few other frameworks to see what they offer. @jakemoxey</a> suggested we try out viem</a>, and it's been promising so far!</p> Bug Fixes🔗</a></h2> Don't kill web worker on error</a>. Ganache throws exceptions in some cases instead of returning an error code (#34</a>.)</li> </ul> New Tests🔗</a></h2> eth_newFilter</code> doesn't return events from non-matching contracts</a>.</li> eth_newFilter</code> doesn't return events from non-matching topics</a>.</li> Getting balance of contract accounts</a>.</li> Getting nonce of externally owned accounts</a>.</li> </ul> WTF News (Week 5) Unknown — Fri, 12 May 2023 00:00:00 +0000 Hello and welcome to issue number three of WTF News, our biweekly status update.</p> Since the last update, we've mostly been working on bug fixes, stability, and UI updates.</p> Code Changes🔗</a></h2> Add two new glue events/actions: addEthereumChain</code> and switchEthereumChain</code></a>.</li> Split page into three columns on wide screens</a>.</li> Stricter lint rules</a>.</li> Auto-scroll test resuts</a>.</li> Added a utility for retrying assertions for a number of seconds.</li> </ul> Bug Fixes🔗</a></h2> Fixed "Order of mined blocks seems inconsistent"</a>. Likely related to how ethers.js fetches the block number. Fixed by calling eth_blockNumber</code> directly.</li> Fixed some</a> JSON-RPC related</a> bugs</a> (thanks to Adam Hodges</a> of coinbase</a> for reporting.)</li> </ul> New Tests🔗</a></h2> None this update.</p> WTF News (Week 3) Unknown — Fri, 28 Apr 2023 00:00:00 +0000 Hello and welcome to issue number two of WTF News, our biweekly status update. We've written more tests, new features, and broken more things than ever before!</p> Known Issues🔗</a></h2> Order of mined blocks seems inconsistent. This affects tests for: eth_getBlockByNumber</code>, eth_getBlockByHash</code>, eth_getBlockTransactionCountByHash</code>, eth_getBlockTransactionCountByNumber</code>, and eth_blockNumber</code>.</li> </ul> Code Changes🔗</a></h2> Added an introduction</a>.</li> Separate mocha output from introduction</a>.</li> Dropped support for queueing RPC requests before the WebSocket is established</a>.</li> Deployed a demo to Heroku</a>.</li> Create the @wallet-test-framework/glue</code></a> package, and use it to display instructions to the user</a>.</li> Automate compiling Solidity as part of the build</a>.</li> </ul> Bug Fixes🔗</a></h2> None. We only added bugs this update.</p> New Tests🔗</a></h2> eth_getBlockTransactionCountByHash</code></a></li> eth_getBlockTransactionCountByNumber</code></a></li> eth_newFilter</code></a></li> </ul> WTF News (Week 1) Unknown — Fri, 14 Apr 2023 00:00:00 +0000 Hello and welcome to the first of hopefully many biweekly status updates! We're going to try and write up a summary of the goings on in the Wallet Test Framework, any features/tests that land, and any issues we discover.</p> Code Changes🔗</a></h2> Rewrote the backend in TypeScript (instead of Rust.)</li> Updated ethers.js</a> and Ganache</a> to versions 6.3 and 7.7 respectively.</li> Switched from the zora</a> testing library to the more well-known Mocha</a> and assert</a> libraries.</li> Use esbuild</a> instead of webpack</a>.</li> Move Ganache into its own WebWorker</a>.</li> </ul> Bug Fixes🔗</a></h2> Handle wallets that return immediately from wallet_addEthereumChain</code></a>.</li> </ul> New Tests🔗</a></h2> eth_blockNumber</code> and eth_chainId</code></a></li> eth_getTransactionByHash</code> and eth_getBlockByHash</code></a></li> eth_getBlockByNumber</code> and eth_getBlockTransactionCountByHash</code></a></li> </ul> Kick Off Unknown — Wed, 05 Apr 2023 00:00:00 +0000 Introduction🔗</a></h2> Any denizen of the 2000s internet who dabbled in web development probably remembers the Acid3</a> browser testing website. The six squares jittering slightly as they change color, never quite reaching the rainbow from the reference image:</p> </p> If you've been following the AllWalletDevs</a> meetings—and if you haven't been, you should be—you might be aware that we've prototyped a framework for testing Ethereum wallets inspired by the Acid3 tests. Our goal is to foster quality and consistency by making it trivially easy to share tests across wallets.</p> This project is official now, with a one year grant from the Ethereum Foundation's Ecosystem Support Program</a>!</p> Project🔗</a></h2> The initial scope of the project is split into several milestones spaced out over one year. After completing these milestones, the testing framework should be in a reasonable place for outside contributors and be ready for wallets to integrate.</p> Milestones🔗</a></h3> Reassess the prototype</a>, and get it into reasonable shape to form the foundation of the framework.</li> Happy-path coverage of all of the endpoints available in the execution-apis</code></a> specification for a single wallet, where the website walks the user through the tests with specific human-readable instructions.</li> Expand the coverage to include multiple wallets, possibly including at least one browser extension and one hardware wallet.</li> Build automation glue (eg. WebDriver</a>) for at least one wallet.</li> </ol> Architecture🔗</a></h3> Overview🔗</a></h4> </p> Components🔗</a></h4> Proxy🔗</a></h5> A web server that forwards JSON-RPC requests between the wallet and the simulated chain. Necessary because browsers do not allow web pages to listen for HTTP or WebSocket connections.</p> Wallet🔗</a></h5> The software under test. Communicates with the tests using window.ethereum</code>, and with the simulated chain through the proxy with JSON-RPC.</p> Simulated Chain🔗</a></h5> An isolated Ethereum-compatible blockchain (like Ganache</a>.) The simulated chain presents a JSON-RPC interface to the wallet through the proxy.</p> Tests🔗</a></h5> Collection of functions that put the simulated chain into a known state, then perform some operation with or retrieve some information through the wallet.</p> Glue🔗</a></h5> Software specific to each wallet that translates conceptual actions (eg. approve transaction) into a format that the wallet understands. Initially this will be on-screen instructions for the user to follow, but later on the glue could be implemented with, for example, WebDriver for browser-based wallets.</p> What's Next?🔗</a></h3> You'll start to see some activity in the repository</a> in the next week or so, and perhaps some discussion in #testing</a>.</p> If you're developing a wallet and want to contribute, please reach out to @gaudren_</a>!</p>

WTF News (Week 19)

Unknown — Fri, 18 Aug 2023 00:00:00 +0000

Hello and welcome to issue number nine of WTF News, our biweekly status update.</p>

Over the last two weeks, we ran a handful of wallets through their paces, and today we can reveal the results! Spoiler alert, but there were more issues in our tests than in the best scoring wallets.</p>

First, the regular status update!</p>

Call to Action 🔗</a></h2>
CI/Build Pipelines 🔗</a></h3>
What good is a testing framework if it isn't used? Get in touch if you want to integrate WTF into your wallet's testing pipeline. We'll even build the automation ourselves!</p>
Testing the Tests 🔗</a></h3>
We want to expand our tests for WTF, to catch issues with the framework itself. To that end, if you work on a wallet that works offline (aside from the RPC provider) and want to try out WTF, get in touch with us!</p>
Code Changes 🔗</a></h2>

Upgraded to viem 1.6</a>!</li> </ul>
Bug Fixes 🔗</a></h2>

Use smaller integers to make ganache happy</a>.</li>
Send WebSocket pings to keep the connection alive</a>.</li>
Use `from</code> instead of account</code> in eth_signTransaction</code></a>.</li>`
`Use hex instead of decimal in eth_signTransaction</code></a>.</li>`
`Convert BigInt</code> to hex in eth_getProof</code></a>.</li>`
`Actually put jsonrpc</code> in responses to the wallet</a>.</li>`
Handle race condition when falling back to adding a chain manually</a>.</li> </ul> Upstream Issues🔗</a></h2> eth_call</code> unclear when Block</code> parameter is omitted</a>.</li> </ul> Test Report🔗</a></h2> Summary🔗</a></h3> Wallet Test Framework – f999503092a10f2b409b5cc733db065c124e56e5</code> </a> https://github.com/wallet-test-framework/framework </a> </p> Not a statement of a wallet’s quality or correctness.</em> </p> </caption> Wallet</th> Version</th> Connection</th> Passing Tests</th> Pass %</th> Platforms</th> Browser</th> Notes</th> </tr> </thead> Brave Wallet</th> </td> EIP-3085</td> 61</td> 100%</td> Browser</td> Brv 1.57.42</td> </td> </tr> Taho</th> 0.46.1</td> EIP-3085</td> 61</td> 100%</td> Extension</td> Chr 115.0.5790.170</td> Had to impersonate chainlist.org</td> </tr> Frame</th> 0.6.7</td> EIP-3085</td> 60</td> 98%</td> Desktop</td> Ff 102.14.0esr (64-bit)</td> Missing signTransaction</td> </tr> Enkrypt</th> 1.24.0</td> Manual</td> 59</td> 97%</td> Extension</td> Ff 102.14.0esr (64-bit)</td> Attempted EIP-3085, but popup doesn’t show RPC url</td> </tr> Coinbase</th> 3.30.2</td> EIP-3085</td> 48</td> 79%</td> Extension</td> Chr 115.0.5790.170</td> Missing hex prefix in logs</td> </tr> Metamask</th> 10.34.0</td> EIP-3085</td> 48</td> 79%</td> Extension</td> Ff 102.14.0esr (64-bit)</td> </td> </tr> OKX</th> 2.58.1</td> EIP-3085</td> 18</td> 30%</td> Extension</td> Chr 115.0.5790.170</td> Tests stopped running somewhere around getFilterChanges</td> </tr> TokenPocket</th> 1.1.19</td> EIP-3085</td> 15</td> 25%</td> Extension</td> Chr 115.0.5790.170</td> Tests stopped running somewhere around getFilterChanges</td> </tr> Argent X</th> 5.7.2</td> Can’t Connect</td> 0</td> 0%</td> Extension</td> Chr 115.0.5790.170</td> No window.ethereum</td> </tr> Bitkeep</th> 1.4.8</td> Can’t Connect</td> 0</td> 0%</td> Extension</td> Chr 115.0.5790.170</td> Attempted EIP-3085, and Manual, but got system error</td> </tr> Sequence</th> 2.0.4</td> Can’t Connect</td> 0</td> 0%</td> Extension</td> Chr 115.0.5790.170</td> Cannot add custom chains</td> </tr> Exodus</th> 23.8.14</td> Can’t Connect</td> 0</td> 0%</td> Extension</td> Chr 115.0.5790.170</td> Cannot add custom chains</td> </tr> </tbody> </table> </div> The astute reader may notice that there are in fact 62 tests in the repository at that commit. Our eth_getProof</code> test is broken, and we are excluding it from this report.</p> Disclaimer🔗</a></h3> Our intent is not to claim that certain wallets are better than others, and a low score here is as likely to indicate that our tests have problems as it is to indicate bugs in a wallet. We're very interested in improving scores across the board, so we're happy to accept contributions to fix tests and just as happy to help debug.</p> Wallet Selection🔗</a></h3> Very little of this report is scientific/rigorous, and the wallet selection process was no exception. We chose a few wallets we're familiar with, and a small sampling of random wallets from the Find an Ethereum Wallet</a> list.</p> Because Wallet Test Framework only supports window.ethereum</code> so far, we're limited to wallets that provide it; that pretty much excludes mobile wallets for the time being. Our architecture</a> requires connecting to a custom chain, so wallets that don't support custom chains cannot be tested (labelled with Can't Connect</code> in the table.)</p> For future reports, get in touch if you're interested in having your results published (or if you'd prefer we didn't mention you.)</p> Discussion🔗</a></h3> Congratulations to Brave</a> and Taho</a> for getting perfect scores! Considering this was our first time trying them out with the Framework (we've been using Frame</a> to develop), this was quite surprising.</p> eth_signTransaction</code>🔗</a></h4> This is a contentious endpoint that we've discussed previously</a>. Very few wallets support eth_signTransaction</code>, mostly by choice.</p> Interestingly, this was Frame's only failure: instead of signing in the wallet, Frame passes these requests through to the RPC provider.</p> Caching🔗</a></h4> There are only two hard things in Computer Science: cache invalidation and naming things. Phil Karlton</em></p> </blockquote> Caching is hard. We've been bitten by it</a>. In a space where you have to pay for every API request, but your users expect a free wallet experience, caching is a necessary evil.</p> We suspect, but haven't verified for all wallets, that many of the test failures are caused by stale values cached by wallets.</p> In the case of eth_call</code>, we have verified that MetaMask specifies an old block number, causing a call into a freshly deployed contract to fail. This is unlikely to cause major issues on a real network with many seconds between blocks, but the tests mine blocks much more frequently, triggering the issue. Regardless, we're following up with their team to see what we can do.</p> Post-merge Endpoints🔗</a></h4> Some of the newer endpoints like eth_maxPriorityFeePerGas</code> aren't yet supported in all wallets. Expect these tests to start passing as they are implemented.</p> Stalled Tests🔗</a></h4> OKX</a> and TokenPocket</a> both failed somewhere around the eth_getFilterChanges</code> suites, and didn't continue to the rest of the tests. It's likely that they would've passed more tests had they continued.</p> We haven't debugged why the tests stalled. It could be as simple as adding a timeout to WTF, or something more involved. We'll be looking into this before the next report.</p> Future Plans🔗</a></h3> We'll continue adding tests, and we'll try to run through this report somewhat regularly. That said, this is entirely a manual process. Once wallets start running WTF as part of their continuous integration processes, we can make some pretty graphs, include more wallets, and make reports more often.</p> In the meantime, join us on Discord</a>!</p> WTF News (Week 17) Unknown — Fri, 04 Aug 2023 00:00:00 +0000 Hello and welcome to issue number eight of WTF News, our biweekly status update.</p> We missed last update (sorry about that), but we're back with more tests than ever!</p> Demo video of an eth_sendTransaction</code> test.</p> </video> </a> Call to Action🔗</a></h2> CI/Build Pipelines🔗</a></h3> What good is a testing framework if it isn't used? Get in touch if you want to integrate WTF into your wallet's testing pipeline. We'll even build the automation ourselves!</p> Testing the Tests🔗</a></h3> We want to expand our tests for WTF, to catch issues with the framework itself. To that end, if you work on a wallet that works offline (aside from the RPC provider) and want to try out WTF, get in touch with us!</p> Code Changes🔗</a></h2> Upgraded to ganache 7.9</a>!</li> </ul> New Tests🔗</a></h2> eth_accounts</code> returns properly formatted hex strings</a>.</li> eth_createAccessList</code> passes through value from ganache</a> (skipped</a>.)</li> eth_getProof</code> works for EOAs and contract storage</a>.</li> eth_call</code> can invoke a function and return the result</a>.</li> eth_getLogs</code> respects block number and source address when returning blocks</a>.</li> eth_maxPriorityFeePerGas</code> passes through value from ganache</a>.</li> eth_sendRawTransaction</code> publishes transactions on-chain</a>.</li> eth_gasPrice</code> passes through value from ganache</a>.</li> eth_estimateGas</code> passes through value from ganache</a>.</li> eth_feeHistory</code> passes through value from ganache</a>.</li> eth_sendTransaction</code> encodes call data to contracts</a>.</li> </ul> WTF News (Week 12) Unknown — Sun, 09 Jul 2023 00:00:00 +0000 Hello and welcome to issue number seven of WTF News, our biweekly status update.</p> This release introduces the first interactive tests, and our first major inconsistencies between wallets: eth_sign</code> and eth_signTransaction</code>.</p> Some wallets have treated eth_sign</code> as a "sign raw data" operation, while others implement it as "sign prefixed text", while still others disable it entirely. Similarly, eth_signTransaction</code> is often not supported at all.</p> For these cases, we've chosen to test for the behaviour specified in the JSON-RPC</a> specification and treat anything different as a test failure.</p> Call to Action🔗</a></h2> We want to expand our tests for WTF, to catch issues like last update's connection issue. To that end, if you work on a wallet that works offline (aside from the RPC provider) and want to try out WTF, get in touch with us!</p> Code Changes🔗</a></h2> Support for signing messages</a> and sending transactions</a> in the glue.</li> </ul> New Tests🔗</a></h2> eth_sign</code> creates a valid signature with prefix</a>.</li> eth_sendTransaction</code> creates and publishes a transaction</a>.</li> </ul> WTF News (Week 11) Unknown — Mon, 26 Jun 2023 00:00:00 +0000 Hello and welcome to issue number six of WTF News, our biweekly status update.</p> Over the last two weeks, we've begun to focus on tests involving UI interaction, like eth_sendTransaction</code> and on the initial steps toward automating wallets.</p> Code Changes🔗</a></h2> Implement connecting to glue over WebSockets</a>. If you navigate to URLs of the form https://127.0.0.1:3000/#glue=ws://127.0.0.1:3001/</code>, the tests will attempt to open a WebSocket connection to 127.0.0.1:3001</code> and issue commands to a glue instance there. The code is of prototype quality, and there is no documentation yet. For the adventurous, see the tests in wallet-test-framework/glue-ws</a> for the gory details.</li> </ul> Bug Fixes🔗</a></h2> During the transition to viem, we broke establishing the initial connection, so we fixed it</a>.</li> @wallet-test-framework/glue</code> didn't have any exports for Node</a>.</li> </ul> Upstream Issues🔗</a></h2> Incorrect type bounds for register</code> (elpheria/rpc-websockets#139</a>.)</li> </ul> WTF News (Week 9) Unknown — Fri, 09 Jun 2023 00:00:00 +0000 Hello and welcome to issue number five of WTF News, our biweekly status update.</p> Since our last post, we've settled on viem</a> for the time being. It fixed our caching issues, and has excellent TypeScript support!</p> Code Changes🔗</a></h2> Migrate from ethers to viem</a>.</li> Pass errors from Ganache over postMessage</code></a> then the WebSocket</a>.</li> Increase the slow test timeout</a>.</li> Disable minify by default</a>. Now test source code is understandable in Mocha's HTML output!</li> </ul> New Tests🔗</a></h2> eth_getTransactionCount</code> for contract accounts</a>.</li> eth_getCode</code> returns the contract's bytecode</a>.</li> eth_newBlockFilter</code> returns new blocks</a>.</li> eth_getStorageAt</code> can read contract storage</a>.</li> eth_getTransactionByBlockHashAndIndex</code></a> and eth_getTransactionByBlockNumberAndIndex</code></a> get transactions.</li> eth_getTransactionReceipt</code></a> can get receipts.</li> A whole</a> lot</a> of filter tests</a>.</li> </ul> Upstream Issues🔗</a></h2> Ganache returns null</code> from several endpoints, and it's unclear if that's allowed in the specification (ethereum/execution-apis#288</a>.)</li> Getting transactions by index beyond the end of the block throws an exception (trufflesuite/ganache#4435</a>.)</li> </ul> WTF News (Week 7) Unknown — Fri, 26 May 2023 00:00:00 +0000 Hello and welcome to issue number four of WTF News, our biweekly status update.</p> This time around we've mostly focused on trying out alternatives to ethers</a>. After wrestling with eth_blockNumber</code> not returning the latest block number, and other similar caching issues, we decided it would be best to try out a few other frameworks to see what they offer. @jakemoxey</a> suggested we try out viem</a>, and it's been promising so far!</p> Bug Fixes🔗</a></h2> Don't kill web worker on error</a>. Ganache throws exceptions in some cases instead of returning an error code (#34</a>.)</li> </ul> New Tests🔗</a></h2> eth_newFilter</code> doesn't return events from non-matching contracts</a>.</li> eth_newFilter</code> doesn't return events from non-matching topics</a>.</li> Getting balance of contract accounts</a>.</li> Getting nonce of externally owned accounts</a>.</li> </ul> WTF News (Week 5) Unknown — Fri, 12 May 2023 00:00:00 +0000 Hello and welcome to issue number three of WTF News, our biweekly status update.</p> Since the last update, we've mostly been working on bug fixes, stability, and UI updates.</p> Code Changes🔗</a></h2> Add two new glue events/actions: addEthereumChain</code> and switchEthereumChain</code></a>.</li> Split page into three columns on wide screens</a>.</li> Stricter lint rules</a>.</li> Auto-scroll test resuts</a>.</li> Added a utility for retrying assertions for a number of seconds.</li> </ul> Bug Fixes🔗</a></h2> Fixed "Order of mined blocks seems inconsistent"</a>. Likely related to how ethers.js fetches the block number. Fixed by calling eth_blockNumber</code> directly.</li> Fixed some</a> JSON-RPC related</a> bugs</a> (thanks to Adam Hodges</a> of coinbase</a> for reporting.)</li> </ul> New Tests🔗</a></h2> None this update.</p> WTF News (Week 3) Unknown — Fri, 28 Apr 2023 00:00:00 +0000 Hello and welcome to issue number two of WTF News, our biweekly status update. We've written more tests, new features, and broken more things than ever before!</p> Known Issues🔗</a></h2> Order of mined blocks seems inconsistent. This affects tests for: eth_getBlockByNumber</code>, eth_getBlockByHash</code>, eth_getBlockTransactionCountByHash</code>, eth_getBlockTransactionCountByNumber</code>, and eth_blockNumber</code>.</li> </ul> Code Changes🔗</a></h2> Added an introduction</a>.</li> Separate mocha output from introduction</a>.</li> Dropped support for queueing RPC requests before the WebSocket is established</a>.</li> Deployed a demo to Heroku</a>.</li> Create the @wallet-test-framework/glue</code></a> package, and use it to display instructions to the user</a>.</li> Automate compiling Solidity as part of the build</a>.</li> </ul> Bug Fixes🔗</a></h2> None. We only added bugs this update.</p> New Tests🔗</a></h2> eth_getBlockTransactionCountByHash</code></a></li> eth_getBlockTransactionCountByNumber</code></a></li> eth_newFilter</code></a></li> </ul> WTF News (Week 1) Unknown — Fri, 14 Apr 2023 00:00:00 +0000 Hello and welcome to the first of hopefully many biweekly status updates! We're going to try and write up a summary of the goings on in the Wallet Test Framework, any features/tests that land, and any issues we discover.</p> Code Changes🔗</a></h2> Rewrote the backend in TypeScript (instead of Rust.)</li> Updated ethers.js</a> and Ganache</a> to versions 6.3 and 7.7 respectively.</li> Switched from the zora</a> testing library to the more well-known Mocha</a> and assert</a> libraries.</li> Use esbuild</a> instead of webpack</a>.</li> Move Ganache into its own WebWorker</a>.</li> </ul> Bug Fixes🔗</a></h2> Handle wallets that return immediately from wallet_addEthereumChain</code></a>.</li> </ul> New Tests🔗</a></h2> eth_blockNumber</code> and eth_chainId</code></a></li> eth_getTransactionByHash</code> and eth_getBlockByHash</code></a></li> eth_getBlockByNumber</code> and eth_getBlockTransactionCountByHash</code></a></li> </ul> Kick Off Unknown — Wed, 05 Apr 2023 00:00:00 +0000 Introduction🔗</a></h2> Any denizen of the 2000s internet who dabbled in web development probably remembers the Acid3</a> browser testing website. The six squares jittering slightly as they change color, never quite reaching the rainbow from the reference image:</p> </p> If you've been following the AllWalletDevs</a> meetings—and if you haven't been, you should be—you might be aware that we've prototyped a framework for testing Ethereum wallets inspired by the Acid3 tests. Our goal is to foster quality and consistency by making it trivially easy to share tests across wallets.</p> This project is official now, with a one year grant from the Ethereum Foundation's Ecosystem Support Program</a>!</p> Project🔗</a></h2> The initial scope of the project is split into several milestones spaced out over one year. After completing these milestones, the testing framework should be in a reasonable place for outside contributors and be ready for wallets to integrate.</p> Milestones🔗</a></h3> Reassess the prototype</a>, and get it into reasonable shape to form the foundation of the framework.</li> Happy-path coverage of all of the endpoints available in the execution-apis</code></a> specification for a single wallet, where the website walks the user through the tests with specific human-readable instructions.</li> Expand the coverage to include multiple wallets, possibly including at least one browser extension and one hardware wallet.</li> Build automation glue (eg. WebDriver</a>) for at least one wallet.</li> </ol> Architecture🔗</a></h3> Overview🔗</a></h4> </p> Components🔗</a></h4> Proxy🔗</a></h5> A web server that forwards JSON-RPC requests between the wallet and the simulated chain. Necessary because browsers do not allow web pages to listen for HTTP or WebSocket connections.</p> Wallet🔗</a></h5> The software under test. Communicates with the tests using window.ethereum</code>, and with the simulated chain through the proxy with JSON-RPC.</p> Simulated Chain🔗</a></h5> An isolated Ethereum-compatible blockchain (like Ganache</a>.) The simulated chain presents a JSON-RPC interface to the wallet through the proxy.</p> Tests🔗</a></h5> Collection of functions that put the simulated chain into a known state, then perform some operation with or retrieve some information through the wallet.</p> Glue🔗</a></h5> Software specific to each wallet that translates conceptual actions (eg. approve transaction) into a format that the wallet understands. Initially this will be on-screen instructions for the user to follow, but later on the glue could be implemented with, for example, WebDriver for browser-based wallets.</p> What's Next?🔗</a></h3> You'll start to see some activity in the repository</a> in the next week or so, and perhaps some discussion in #testing</a>.</p> If you're developing a wallet and want to contribute, please reach out to @gaudren_</a>!</p>

WTF News (Week 17)

WTF News (Week 12)

Code Changes 🔗</a></h2>

Support for signing messages</a> and sending transactions</a> in the glue.</li> </ul>
New Tests 🔗</a></h2>

`eth_sign</code> creates a valid signature with prefix</a>.</li>`
`eth_sendTransaction</code> creates and publishes a transaction</a>.</li> </ul>`

New Tests 🔗</a></h2>

`eth_sign</code> creates a valid signature with prefix</a>.</li>`
`eth_sendTransaction</code> creates and publishes a transaction</a>.</li> </ul>`

WTF News (Week 11)

Upstream Issues 🔗</a></h2>

Incorrect type bounds for `register</code> (elpheria/rpc-websockets#139</a>.)</li> </ul>`

WTF News (Week 9)

WTF News (Week 7)

New Tests 🔗</a></h2>

`eth_newFilter</code> doesn't return events from non-matching contracts</a>.</li>`
`eth_newFilter</code> doesn't return events from non-matching topics</a>.</li>`
`Getting balance of contract accounts</a>.</li>`
`Getting nonce of externally owned accounts</a>.</li> </ul>`

WTF News (Week 5)

New Tests 🔗</a></h2>
None this update.</p>

WTF News (Week 3)

Bug Fixes 🔗</a></h2>
None. We only added bugs this update.</p>
New Tests 🔗</a></h2>

`eth_getBlockTransactionCountByHash</code></a></li>`
`eth_getBlockTransactionCountByNumber</code></a></li>`
`eth_newFilter</code></a></li> </ul>`

New Tests 🔗</a></h2>

`eth_getBlockTransactionCountByHash</code></a></li>`
`eth_getBlockTransactionCountByNumber</code></a></li>`
`eth_newFilter</code></a></li> </ul>`

WTF News (Week 1)

New Tests 🔗</a></h2>

`eth_blockNumber</code> and eth_chainId</code></a></li>`
`eth_getTransactionByHash</code> and eth_getBlockByHash</code></a></li>`
`eth_getBlockByNumber</code> and eth_getBlockTransactionCountByHash</code></a></li> </ul>`

Kick Off

What's Next?🔗</a></h3>
You'll start to see some activity in the repository</a> in the next week or so, and perhaps some discussion in #testing</a>.</p>
If you're developing a wallet and want to contribute, please reach out to @gaudren_</a>!</p>

Wallet Test Framework

Test Report #2

Year in Review (2023)

EIP-1193</a> Events 🔗</a></h3>
EIP-1193</a> defines several events (like `connect</code> or accountsChanged</code>) that aren't covered by the current tests. Emitting these events is essential for responsive application development, so we'd like to expand our coverage in this area.</p>`

Supporters 🔗</a></h2>
We want to give a huge thank you to the Ethereum Foundation's Ecosystem Support Program and to the donors on Gitcoin for helping to fund our work so far. We'd also like to thank Coinbase for being very supportive and responsive when reporting issues.</p>

WTF News (Week 19)