From d9818a33e164e46c468704753b6d7f79319d67f7 Mon Sep 17 00:00:00 2001 From: GAEAlimited <69316708+GAEAlimited@users.noreply.github.com> Date: Wed, 19 Jun 2024 07:05:09 -0400 Subject: [PATCH] Update index.html (GSCxEIPs) GAEA $uperChain --- index.html | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/index.html b/index.html index a09f9ad8ad6dbb..2333c445a95e07 100644 --- a/index.html +++ b/index.html @@ -1,9 +1,9 @@ --- layout: default -title: Home +title: GSC20 Edition --- -

EIPs +

EIPs for GSC20 Discord channel for ECH eip-editer Discord channel for Eth R&D eip-editing Discord server for discussions about proposals that impact Ethereum wallets @@ -12,12 +12,12 @@

EIPs RSS RSS

-

Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Network upgrades are discussed separately in the Ethereum Project Management repository.

+

GSCx Edition of Ethereum Improvement Proposals (GSCxEIPs) are standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. Network upgrades are discussed separately in the Ethereum Project Management repository.

Contributing

First review EIP-1. Then clone the repository and add your EIP to it. There is a template EIP here. Then submit a Pull Request to Ethereum's EIPs repository.

-

EIP status terms

+

GSCx Edition of EIP status terms for GAEA $uperChain

-

EIP Types

+

GSCx Edition for EIP Types

EIPs are separated into a number of types, and each has its own list of EIPs.

-

Standard Track ({{site.pages|where:"type","Standards Track"|size}})

+

Introducing GAEA $uperChain ({{site.pages|where:"type","GAEA $uperChain"|size}})

Describes any change that affects most or all Ethereum implementations, such as a change to the network protocol, a change in block or transaction validity rules, proposed application standards/conventions, or any change or addition that affects the interoperability of applications using Ethereum. Furthermore Standard EIPs can be broken down into the following categories.

-

Core ({{site.pages|where:"type","Standards Track"|where:"category","Core"|size}})

+

Core ({{site.pages|where:"type","GAEA $uperChain"|where:"category","Core"|size}})

Improvements requiring a consensus fork (e.g. EIP-5, EIP-211), as well as changes that are not necessarily consensus critical but may be relevant to “core dev” discussions (for example, the PoA algorithm for testnets described in EIP-225).

-

Networking ({{site.pages|where:"type","Standards Track"|where:"category","Networking"|size}})

+

Networking ({{site.pages|where:"type","GAEA $uperChain"|where:"category","Networking"|size}})

Includes improvements around devp2p (EIP-8) and Light Ethereum Subprotocol, as well as proposed improvements to network protocol specifications of whisper and swarm.

-

Interface ({{site.pages|where:"type","Standards Track"|where:"category","Interface"|size}})

+

Interface ({{site.pages|where:"type","GAEA $uperChain"|where:"category","Interface"|size}})

Includes improvements around client API/RPC specifications and standards, and also certain language-level standards like method names (EIP-6) and contract ABIs. The label “interface” aligns with the interfaces repo and discussion should primarily occur in that repository before an EIP is submitted to the EIPs repository.

-

ERC ({{site.pages|where:"type","Standards Track"|where:"category","ERC"|size}})

+

ERC ({{site.pages|where:"type","GAEA $uperChain"|where:"category","ERC"|size}})

Application-level standards and conventions, including contract standards such as token standards (EIP-20), name registries (EIP-137), URI schemes (EIP-681), library/package formats (EIP-190), and account abstraction (EIP-4337).

Meta ({{site.pages|where:"type","Meta"|size}})