<\/p>\n
The past few months have been quite eventful for the Ethereum javascripters. To begin with, an outstanding hackathon was held in collaboration with IPFS. You can read Dan Finlay’s wonderful summary here<\/span><\/a>.<\/span><\/p>\n <\/p>\n Additionally, during this period, Aaron Davis (Kumavis<\/a>) made significant advancements towards a JS light client by leveraging IPFS’s libp2p<\/a> to forge an in-browser mesh network and IPLD<\/a> to establish the merklization foundation. This endeavor will be crucial for developing pure in-browser clients. Furthermore, Casey Detrio<\/a> worked on a standard JSON RPC testing suite, which you can view the outcomes of <\/span>here<\/span><\/a>.<\/span><\/p>\n <\/p>\n Following the Seattle Meetup, we (Axic<\/a> and Wanderer<\/a>) gathered for a week-long hackathon in Budapest to iron out details of ewasm<\/a>. Meanwhile, in the JS realm, Fabian is conducting an extensive overhaul of Web3.js in preparation for the 1.0 release, while Nick Dodson has been occupied with ethjs<\/a>. The remainder of this article will explore the diverse prospects that this technology could offer, along with delving into specific details regarding each unique project. All these projects are open source and welcome community engagement, so if you’re interested, feel free to check them out, introduce yourself, and submit a PR when you can!\u00a0<\/span><\/p>\n <\/p>\n Ewasm\u2019s<\/a> objective is to investigate and replace the EVM with WebAssembly<\/a> and, as a secondary aim, to create a client for the existing system that can be efficiently JITed (or transcompiled<\/a>) to WebAssembly.<\/span> A crucial part of assessing WebAssembly for blockchain applications will be to establish a test network, and this year, the Ewasm team will concentrate on bringing that test network into existence. The testnet initiative will:<\/span><\/p>\n <\/p>\n The ewasm track is dedicated to ewasm exploration and progress, while the client integration track will focus on developing the network and bringing robust and light clients into being. There are numerous shared components in these two tracks. The Ewasm project is divided into two primary aspects: the Kernel Layer<\/a>, which manages IPC and controls the state, and the core VM. This structure should allow us to use the same framework for distinct VM implementations.<\/span> To summarize, the key tasks for ewasm include:<\/span><\/p>\n <\/p>\n <\/li>\n We invite you to participate in the implementation initiative! We hold bi-weekly meetings on Tuesdays. Our communication platform is on Matrix at\u00a0prima:matrix.org<\/a>\u00a0(or #ewasm on IRC or at gitter<\/a>) There are various justifications for developing an Ethereum networking implementation in JS. Firstly, it would enable us to create a complete and lightweight Ethereum JS node. These light clients would operate both in a Node.js environment and within a browser. A necessity for an in-browser light client involves \u201cbridge\u201d nodes. These nodes might also serve as\u00a0<\/span>signaling servers<\/span><\/a> for the <\/span>webrtc<\/span><\/a> network which the browser light clients would utilize to relay messages from the RLPx network to the WebRTC framework. This initiative is being led by Metamask employing IPFS\u2019s libp2p. Moreover, the\u00a0RLPx<\/a> implementation was recently updated by <\/span>fanatid<\/span><\/a>.<\/span> Ethereum\u2019s blockchain and on-chain statecan be interpreted as a diagram of hash-linked information. IPFS\/IPLD<\/a> is suggested as a universal framework to articulate and disseminate hash-linked information. Thus, we can view Ethereum as an application layer built on the hash-linked data availability platform. As a demonstration, Kumavis<\/a> executed IPLD resolvers<\/a> for the Ethereum data formats that indicate where hash-links are incorporated within the standard Ethereum formats (e.g., block and state trie node). This, combined with additional universal characteristics of libp2p (IPFS\u2019s generalized p2p networking framework), allows for the development of lightweight Ethereum clients centered around the consensus protocol and the state transition mechanism. A key benefit of this strategy is that the networking layer is transport-neutral and can be utilized in environments lacking access to tcp\/udp (such as web browsers) which standard Ethereum clients rely on. Currently, this initiative is still being researched. MetaMask aims to leverage this strategy to create a browser-compatible Ethereum light client through a secondary network, facilitated by hybrid nodes.<\/span> A new iteration of web3.js is under development. It represents the most significant refactor of the codebase since the establishment of the popular Ethereum library. It\u00a0<\/span>will introduce numerous convenient features like confirmation and receipt events on transactions, an appealing subscription API, and checksum validations on address entries.<\/span> The API remains in the early stages of completion, but if you’re keen to explore, you can view the documentation\u00a0here<\/a>.<\/span><\/p>\n <\/p>\n The new iteration will also encompass several\u00a0major changes, but such updates are essential to ensure the new API is correctly configured and to phase out certain deprecated methods, including synchronous calls. Version 1.0 will exclusively support promises<\/em> and in specific scenarios \u201cPromiseEvents\u201d to better represent multiple events during a transaction’s execution. For those contemplating transitioning their applications to the new web3, a migration guide will be available upon release to facilitate the shift from 0.x.x smoothly.<\/p>\n <\/p>\n In Mist, there will no longer be a default exposure of web3, as this promotes the undesirable habit of depending on the Mist-supplied web3, making breaking changes detrimental for dapps. Instead, there will be an \u201cethereumProvider\u201d, that libraries like web3 can utilize to communicate with the underlying node. Web3.js will automatically identify any provided provider and make it accessible in its API for seamless instantiation.<\/span><\/p>\n <\/p>\n For those keen to try it immediately, check out the 1.0 branch in the web3.js repository<\/a><\/span>. Just be cautious, there may be unforeseen issues!<\/span><\/p>\n <\/p>\n Ethjs<\/a> is a newly optimized, lightweight JavaScript utility for <\/span>Ethereum<\/span><\/a>\u00a0designed to work with the JSON RPC, much like web3.js but more streamlined, asynchronous only, and utilizing bn.js<\/a>. Presently, ongoing efforts include:<\/span> <\/p>\n Currently working on the 4.0.0 release! This version will feature:<\/span> We will transition the TestRPC to the Truffle GitHub organization<\/a>\u00a0since it is primarily managed by Truffle developers. There are substantial new additions to TestRPC on the horizon. Additionally, we are dedicating considerable effort to unify documentation and branding under the Truffle identity. Any thoughts regarding this transition would be valued. Finally, the TestRPC is in need of a new name that reflects its full capabilities. If you have suggestions, please share!EWASM<\/span><\/h2>\n
\n<\/p>\n\n
\n<\/p>\n\n
\n<\/p>\n\n
\n<\/p>\nNetworking<\/span><\/h2>\n
\n<\/p>\nIPLD<\/span><\/h2>\n
\n<\/p>\nWeb3.js 1.0 is on the way! <\/span><\/h2>\n
\n<\/p>\nEthjs<\/span><\/h2>\n
\n<\/p>\n\n
TestRPC<\/span><\/h2>\n
\n<\/p>\n\n
\n
\nThe Ethereum JS community is a thrilling and remarkable sphere to engage with. There are numerous impressive projects underway. If you’re interested in integrating, we have weekly Friday meetings at 3:00 EST \/ 10:00 PST \/ 18:00 UTC. Keep an eye on our Gitter channel<\/a> for the chat link. Furthermore, we are organizing an upcoming hackathon<\/a>.\u00a0Do let us know if you are interested.
\n<\/p>\n
\n<\/p>\n