{"id":18604,"date":"2026-03-24T08:13:49","date_gmt":"2026-03-24T08:13:49","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/03\/24\/ethereum-js-ecosystem-updates-ethereum-foundation-blog\/"},"modified":"2026-03-24T08:13:49","modified_gmt":"2026-03-24T08:13:49","slug":"ethereum-js-ecosystem-updates-ethereum-foundation-blog","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/03\/24\/ethereum-js-ecosystem-updates-ethereum-foundation-blog\/","title":{"rendered":"Ethereum JS Ecosystem Updates | Ethereum Foundation Blog"},"content":{"rendered":"<p> <br \/>\n<\/p>\n<div id=\"\">\n<p class=\"chakra-text css-gi02ar\">It&#8217;s been a fairly busy for the last couple of months for the Ethereum javascripters. To start with, there was a really great hackathon with IPFS.\u00a0You can read Dan Finlay&#8217;s\u00a0excellent write up <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/media.consensys.net\/ipfs-ethereum-hackathon-results-d6b90b34286f#.25vwli7yd\"><span style=\"font-weight:400\">here<\/span><\/a><span style=\"font-weight:400\">.<\/span><\/p>\n<p class=\"chakra-text css-gi02ar\"><span style=\"font-weight:400\">Also, during this time Aaron Davis (<a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/kumavis\">Kumavis<\/a>) made some excellent progress towards a JS\u00a0light client by utilizing IPFS&#8217;s\u00a0<a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/libp2p\">libp2p<\/a> to build a in-browser mesh network and <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ipld\">IPLD<\/a> to provide the merklization layer. This will be important work in the future for building pure in-browser clients. Also <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"http:\/\/github.com\/cdetrio\">Casey Detrio<\/a> worked on a standard json RPC test suite, which you can see the results of <\/span><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"http:\/\/cdetr.io\/eth-compat-table\/\"><span style=\"font-weight:400\">here<\/span><\/a><span style=\"font-weight:400\">.<\/span><\/p>\n<p class=\"chakra-text css-gi02ar\"><span style=\"font-weight:400\">After the Seattle Meetup, we (<a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/axic\">Axic<\/a> and <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/wanderer\">Wanderer<\/a>) sat down for a week long hackathon in Budapest to hash out some details of <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ewasm\">ewasm<\/a>. Elsewhere in JS world, Fabian is doing a huge refactor of Web3.js for the 1.0 release, while Nick Dodson has been busy with <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethjs\">ethjs<\/a>. The rest of this post will be charting the various projections that this technology could provide as well as going into some details about each individual project. All these projects are all open source and encourage community participation, so if you are interested please check them out, say hello and send in a PR if you have time!\u00a0<\/span><\/p>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"ewasm\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"ewasm permalink\" href=\"#ewasm\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a><span style=\"font-weight:400\">EWASM<\/span><\/h2>\n<p><span style=\"font-weight:400\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ewasm\/design\">Ewasm\u2019s<\/a> goal is to research and replace the EVM with <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"http:\/\/github.com\/webassembly\">Webassembly<\/a> and secondarily, implement a client for the current system which can be efficiently JITed (or <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"http:\/\/github.com\/ewasm\/evm2wasm\">transcompiled<\/a>) to WebAssembly.<\/span><\/p>\n<p class=\"chakra-text css-gi02ar\"><span style=\"font-weight:400\">A major piece of evaluating WebAssembly for blockchain usage will be create a test network and this year the focus of the Ewasm team will be bringing that test network to life. The testnet work will:<\/span><\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\"><span style=\"font-weight:400\">enable hands-on work with ewasm for\u00a0a wider audience<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">enable related work, such as experiments with casper to be done by providing a flexible platform for experimentation<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight:400\">The ewasm track is dedicated to ewasm research and development, while the client integration track will be dedicated to developing the network and bring full and light clients into existence. But there are many shared components to these two tracks. The Ewasm project is being broken down into two main components: the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"http:\/\/github.com\/ewasm\/ewasm-kernel\">Kernel Layer<\/a>, which handles IPC and manages the state, and the core VM. This should enable us to use the same framework for\u00a0different VM implementations.<\/span><\/p>\n<p class=\"chakra-text css-gi02ar\"><span style=\"font-weight:400\">So to recap, the major tasks for ewasm are:<\/span><\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\"><span style=\"font-weight:400\">Build an ewasm test network<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Creating a reusable \u201ckernel\u201d module<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Revamp ethereumjs-vm<\/span>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\"><span style=\"font-weight:400\">Use ewasm-kernel for the message passing<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Implement the latest EIPs<\/span><\/li>\n<\/ul>\n<\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Ewasm integration tools<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Solidity-ewasm integration (upcoming effort for the solidity hackathon!)<\/span><\/li>\n<\/ul>\n<p>Please come join the implementation effort! We have semi-weekly meetings on Tuesdays. Our communication channel is on Matrix at\u00a0<a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/riot.im\/app\/#\/room\/#prima:matrix.org\">prima:matrix.org<\/a>\u00a0(or #ewasm on IRC or at <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/gitter.im\/ewasm\/Lobby\">gitter<\/a>)<\/p>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"networking\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"networking permalink\" href=\"#networking\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a><span style=\"font-weight:400\">Networking<\/span><\/h2>\n<p><span style=\"font-weight:400\">There are several reasons to have an Ethereum networking implementation in JS. For one, it would\u00a0allow us to implement a full and light Ethereum JS node. These light clients would run both in a node.js environment and in a browser. A prerequisite for an in-browser light client is \u201cbridge\u201d nodes. These nodes might also act as\u00a0<\/span><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/www.webrtc-experiment.com\/docs\/WebRTC-Signaling-Concepts.html\"><span style=\"font-weight:400\">signaling servers<\/span><\/a><span style=\"font-weight:400\"> for the <\/span><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/webrtc.org\/\"><span style=\"font-weight:400\">webrtc<\/span><\/a><span style=\"font-weight:400\"> network that the browser light clients would use to relay \u00a0messages from the RLPx network to the webrtc network. This work is being spearheaded by Metamask using IPFS\u2019s libp2p. Also the\u00a0<a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereumjs\/ethereumjs-devp2p\">RLPx<\/a> implementation was recently revamped by <\/span><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/fanatid\"><span style=\"font-weight:400\">fanatid<\/span><\/a><span style=\"font-weight:400\">.<\/span><\/p>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"ipld\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"ipld permalink\" href=\"#ipld\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a><span style=\"font-weight:400\">IPLD<\/span><\/h2>\n<p><span style=\"font-weight:400\">Ethereum\u2019s blockchain and on-chain state can be understood as a graph of hash-linked data. <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ipld\">IPFS\/IPLD<\/a> is proposed as a generic system to describe and distribute hash-linked data. Therefore we can describe Ethereum as an application layer on top of the hash-linked data availability platform. As a proof of concept, <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/kumavis\">Kumavis<\/a>\u00a0implemented <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ipld\/js-ipld-eth-block\">IPLD resolvers<\/a> for the Ethereum data formats that define where hash-links are encoded inside the canonical Ethereum formats (e.g. block and state trie node). This, combined with other generic features of libp2p (IPFS\u2019s generic p2p networking stack), enables the creation of minimal Ethereum clients that focus on the consensus protocol and state transition mechanism. One advantage of this approach is that the networking layer is transport-agnostic and can be used in environments that don\u2019t have access to tcp\/udp (such as the browser) that the standard Ethereum clients require. This project is still in the research phase. MetaMask hopes to use this approach to implement a browser compatible Ethereum light client via a secondary network, bridged by hybrid nodes.<\/span><\/p>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"web3js-10-incoming\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"web3js 10 incoming permalink\" href=\"#web3js-10-incoming\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a><span style=\"font-weight:400\">Web3.js 1.0 incoming! <\/span><\/h2>\n<p><span style=\"font-weight:400\">A new version of web3.js is in the making. It is the biggest refactor of the codebase since the inception of the popular Ethereum library. It\u00a0<\/span><span style=\"font-weight:400\">will have a lot of convenience features like confirmation and receipt event on transactions, a nice subscription API, and checksum checks on address inputs.<\/span><\/p>\n<p class=\"chakra-text css-gi02ar\"><span style=\"font-weight:400\">The API is still not yet finalized, but if you are eager to have a look you can check out the docs\u00a0<a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"http:\/\/web3js.readthedocs.io\/en\/1.0\/getting-started.html\">here<\/a>.<\/span><\/p>\n<p class=\"chakra-text css-gi02ar\">The new version will also have quite a few\u00a0breaking changes, but those updates are necessary to get the new API right and remove some some deprecated methods\u00a0along the way, like synchronous calls. 1.0 will only have <em class=\"chakra-text css-0\">promises<\/em> and in some events \u201cPromiseEvents\u201d to better reflect multiple events on a transaction&#8217;s execution. For those who are thinking of transitioning their apps to the new web3, there will be a migration guide upon launch to help make the transition from 0.x.x as easy as possible.<\/p>\n<p class=\"chakra-text css-gi02ar\"><span style=\"font-weight:400\">In Mist there will be no web3 exposed by default anymore, as this encourages the bad habit of relying on the Mist-provided web3, which makes breaking changes disastrous for dapps. Instead, there will be an \u201cethereumProvider\u201d, which libraries like web3 can use to talk to the underlying node. Web3.js will automatically detect any given provider and expose it on its API for easy instantiation.<\/span><\/p>\n<p class=\"chakra-text css-gi02ar\"><span style=\"font-weight:400\">For those who can\u2019t wait and want to try it right now, checkout the 1.0 branch in the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/web3.js\/tree\/1.0\">web3.js repo<\/a><\/span><span style=\"font-weight:400\">. Be aware there might be dragons!<\/span><\/p>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"ethjs\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"ethjs permalink\" href=\"#ethjs\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a><span style=\"font-weight:400\">Ethjs<\/span><\/h2>\n<p><span style=\"font-weight:400\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethjs\">Ethjs<\/a> is a new highly optimised, light-weight JS utility for <\/span><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/www.ethereum.org\/\"><span style=\"font-weight:400\">Ethereum<\/span><\/a><span style=\"font-weight:400\">\u00a0geared to working with the json RPC, much like web3.js but lighter, async only and using <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/indutny\/bn.js\/\">bn.js<\/a>. The current ongoing activity includes:<\/span><\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\"><span style=\"font-weight:400\">Adding the ABI methods for decoding logs in ethjs-abi<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Having fixed\u00a0a small decoding bug in ethjs-abi (handling 0x addresses)<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Merged new schema for personal recover and sign ethjs-schema<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Looking for help making ethjs-filter stateless (infura ready)<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Bug fixing in ethjs-contract<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Documentation updates all around<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Upcoming ethjs version 0.2.7 release!<\/span><\/li>\n<\/ul>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"testrpc\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"testrpc permalink\" href=\"#testrpc\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a><span style=\"font-weight:400\">TestRPC<\/span><\/h2>\n<p><span style=\"font-weight:400\">Working on the 4.0.0 release! This release will include:<\/span><\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\"><span style=\"font-weight:400\">Database persistence. Now you can create a test chain and save that data, just like any other private chain!<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Clean up of how data is stored in memory, which should reduce memory issues significantly. Although there will be\u00a0a slight cost in\u00a0some performance, which mostly be unnoticeable unless you\u2019re making thousands of transactions, it will bring\u00a0a huge increase in stability.<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Bundling for the browser (provider only).<\/span><\/li>\n<li class=\"css-0\"><span style=\"font-weight:400\">Easier installs on Windows, and possibly other platforms.<\/span><\/li>\n<\/ul>\n<p>We\u2019ll be moving the TestRPC to the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"http:\/\/github.com\/trufflesuite\">Truffle github organization<\/a>\u00a0since it\u2019s primarily maintained by Truffle developers. There are significant new TestRPC add-ons coming. And we&#8217;re investing significant energy in documentation and branding that unifies it under the Truffle brand. Any feedback on this move is appreciated. \u00a0Lastly, the TestRPC needs a new name that exudes everything it can do.\u00a0If you have an idea let us know!<\/p>\n<p>The Ethereum JS community is an exciting and wonderful thing to be a part of. There are many great projects happening. If you are interested in plug\u00a0in we have weeklyFriday meetings at 3:00 EST \/ 10:00 PST \/ 18:00 UTC. Watch <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/gitter.im\/ethereum\/ethereumjs-lib\">our gitter channel<\/a> for the chat link. Also, we are organizing\u00a0an <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereumjs\/organization\/issues\/9\">upcoming hackathon<\/a>.\u00a0Let us know if you are interested.<\/p>\n<hr aria-orientation=\"horizontal\" class=\"chakra-divider css-1e6gg7n\"\/>\n<p class=\"chakra-text css-gi02ar\"><strong>ADDENDUM<\/strong>\u00a0[Mar. 22, 2017]: Note that some of the projects in this post are not directly supported by Ethereum Foundation, but have been included as they are relevant to the overall Ethereum JS ecosystem update by the author.<\/p>\n<\/div>\n<p><br \/>\n<br \/><a href=\"https:\/\/blog.ethereum.org\/en\/2017\/03\/21\/ethereum-js-ecosystem-updates\">Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>It&#8217;s been a fairly busy for the last couple of months for the Ethereum javascripters. To start with, there was a really great hackathon with IPFS.\u00a0You can read Dan Finlay&#8217;s\u00a0excellent write up here. Also, during this time Aaron Davis (Kumavis) made some excellent progress towards a JS\u00a0light client by utilizing IPFS&#8217;s\u00a0libp2p to build a in-browser [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":18498,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"tdm_status":"","tdm_grid_status":"","footnotes":""},"categories":[24],"tags":[],"kronos_expire_date":[],"class_list":["post-18604","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ethereum"],"_links":{"self":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/18604","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/comments?post=18604"}],"version-history":[{"count":0,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/18604\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media\/18498"}],"wp:attachment":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media?parent=18604"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/categories?post=18604"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/tags?post=18604"},{"taxonomy":"kronos_expire_date","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/kronos_expire_date?post=18604"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}