On March 13, 2024, at 7:25:35 PM, Ethereum block number 19426587 was published. This block marked the first appearance of the blob_gas_used and excess_blob_gas keys in block headers, indicating that EIP-4844 was now in action. screenshot of first block with EIP-4844 showing header extension queried using ethRPCtoREST Impact Analysis What was going to be changed from then, can be answered best by those who were most excited about it, who were already waiting for it and literally jumped on making use of it. Daily Blob Transaction volume So Starknet and zkSync-era were the early adopters.

Contract // SPDX-License-Identifier: GPL-3.0 pragma solidity >=0.8.2 <0.9.0; contract test { function double(int a) public pure returns(int) { return 2*a; }

Compile Contract First let's compile contract using solidity compiler. echo 'contract Storage { uint pos0; mapping(address => uint) pos1; function Storage_func() public {  pos0 = 1234;  pos1[msg.sender] = 5678;

This is final dev update concluding developments of ethRPCtoREST occurred during Fellowship period. Goal was to create a simplified REST API interface for interacting with Execution layer APIs of Ethereum. Or simply, a REST Wrapper around JSON-RPC APIs. It started with deciding a rough structure through project proposal. There were mainly two sub-missions under this proposal. One was specing out all APIs in REST format and another was implementing them. I started with OPENAPI specifications on a .yaml file and after specing out 10 of the methods I moved on with implementation. After some time, there were multiple methods and OPENAPI specs got lagged. Jordan had also shown intent for working on REST wrappers and he took the responsibility of docs generation. Till now, in total there are 17 REST endpoints with around 18 execution layer methods wrapped. Their relation isn't one-to-one. In some cases, one REST endpoint acts as an umbrella over multiple methods, automatically figuring out appropriate methods depending upon input. In other cases, multiple endpoints are wrapped around single method with default values as input parameters.

Week 17 - Finally implementing them I did some mistakes in documenting the process mainly in counting zeros and setting length of key and position which result in inconsitency in implementation results and documented results. Finally spotted them and applied the changes in week 14. /eth/storage/:address/:position/:identifier Allowing to get storage using eth_getStorageAt. Doing some cleaning up and redoing some design decisions. Week 14 - APIs that need the simplification most eth_getStorageAt