---
# System prepended metadata

title: Week Five
tags: [Anuoluwapo AliWeekly, Blockfuselabs]

---


Update on week Five @ blockfuse Labs
The Article for this week will be spanning across different topics and events read closely as we dive into the main components that form used in token formation and all.
Let’s look into the Remote Procedure call known as the RPC. This procedure allows the user to communicate with the server using the RPC protocol ensuring calls to the API or services over the network.
Note that in blockchain the RPC is used to connect to a blockchain node. They are also used to integrate decentralized applications or services that rely on remote procedure calls.
Next up, I looked into an API Key: process.env.ETHERSCAN, this key is used to verify a smart contract. After that I went to through the process of looking at the hadhat documentation (hardhat.org) and how to integrate hardhat into my IDE (VS code) I also learnt that in  the blockchain space there are other field such as Smart contract security and auditing in blockchain. During the session we interacted with a smart contract on ether scan. We then had a glance at the layer two blockchain knowing that it is scalable but depends on the layer one blockchain for security.
Moving forward Ethereum Improvement proposal (EIP) was the next glance 
Ethereum Improvement Proposals (EIPs) are design documents providing information to the Ethereum community, or describing a new feature for Ethereum or its processes or environment. The EIP should provide a concise technical specification of the feature and a rationale for the feature. EIP authors are responsible for building consensus within the community and documenting dissenting opinions.
Ethereum Request Comment (ERC) it serves as a standard from which an EIP is generated, more like an improved version for token standards. Therefore an ERC is used to define standard interfaces for smart contracts on the Ethereum blockchain.
Lastly we went further to look into low level calls, and I learnt that these are low level functions used to interact with smart contracts. The most common low-level calls in Solidity are call, delegate call, static call, and call code.
