Content
@
0 reply
0 recast
0 reaction
Joe Hoffend
@joehoffend
Common Standards in Blockchain are vital to improving usability for users (such as EIPs). They’re also challenging to understand! The work we do at @walletconnect helps support and drive many of these standards. Let’s dive into the different types:
1 reply
0 recast
1 reaction
Joe Hoffend
@joehoffend
At a high level, there’s 4 standard types we’ll focus on: EIP, ERC, RIP, CAIP. We’ll define each one and provide a basic overview.
1 reply
0 recast
0 reaction
Joe Hoffend
@joehoffend
1. Ethereum Improvement Proposals (EIP) - these changes are foundational to the Ethereum protocol, and may affect the consensus mechanism. You can bucket EIPs into two categories - “RPC / Client Software” changes & “Protocol or Consensus” changes.
1 reply
0 recast
0 reaction
Joe Hoffend
@joehoffend
“RPC / Client Software” changes do not require hard forks, as they simply update the client software that interacts with the Ethereum network. “Protocol or Consensus” changes alter the Ethereum protocol itself and require a hard fork, where all nodes must upgrade to stay compatible with the network.
1 reply
0 recast
0 reaction
Joe Hoffend
@joehoffend
2. Ethereum Request for Comment (ERC) - these are more about coordination between Applications. Think ERC-20 as a token standard, and ERC-721 as an NFT standard. They’re applicable at the application level and thus do not require a hard fork.
1 reply
0 recast
0 reaction
Joe Hoffend
@joehoffend
3. Rollup Improvement Proposal (RIP) - RIPs just started a few months ago. Basically all the rollups (L2’s) came up with their own standards process. They need to continue to innovate and move fast, and EIPs/ERCs take much longer and have much more back and forth around them.
1 reply
0 recast
0 reaction
Joe Hoffend
@joehoffend
RIPs won’t require any kind of hard-fork like scenario unless changes to sequencers or validators are proposed, which has yet to be seen.
1 reply
0 recast
0 reaction
