Skip to content

Commit

Permalink
Merge branch 'dev' into network-layer
Browse files Browse the repository at this point in the history
  • Loading branch information
minimalsm authored May 16, 2022
2 parents ac610be + 5c78c10 commit b7cb0a8
Show file tree
Hide file tree
Showing 1,164 changed files with 153,519 additions and 40,320 deletions.
572 changes: 566 additions & 6 deletions .all-contributorsrc

Large diffs are not rendered by default.

1 change: 0 additions & 1 deletion .env.example
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,6 @@
# warning: variables prefixed with GATSBY_ will be made available to client-side code
# be careful not to expose sensitive data (e.g. your Algolia admin key)
ALGOLIA_ADMIN_KEY=insertValue
DEFI_PULSE_API_KEY=insertValue
ETHERSCAN_API_KEY=insertValue
GATSBY_ALGOLIA_APP_ID=insertValue
GATSBY_ALGOLIA_SEARCH_KEY=insertValue
Expand Down
4 changes: 4 additions & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
@@ -1,2 +1,6 @@
deploy.sh linguist-documentation
README.md linguist-documentation
*.md linguist-vendored=false
*.md linguist-generated=false
*.md linguist-documentation=false
*.md linguist-detectable=true
97 changes: 97 additions & 0 deletions .github/ISSUE_TEMPLATE/suggest_layer2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,97 @@
---
name: Suggest a Layer 2
about: Suggest a Layer 2 to list on ethereum.org
title: ""
labels: "feature :sparkles:, content :fountain_pen:"
assignees: ""
---

Before suggesting a layer 2, make sure you've read [our listing policy](/contributing/adding-layer-2/).

Only continue with the issue if your layer 2 meets the criteria listed there.

If it does, complete the following information which we need to accurately list the layer 2.

**Name**

<!-- Please provide the official name of the layer 2-->

**Logo**

<!-- Please provide an SVG or hi-res transparent PNG -->

**Description**

<!-- Please provide a 1-2 sentence (240 character max) of the layer 2. -->

**Website**

<!-- Please provide a URL to the website for the layer 2 -->

**Developer documentation**

<!-- Please provide a URL to developer docs for the layer 2 -->

**L2Beat page**

<!-- Please provide the link to the layer 2s page on L2BEAT-->

**Is the project open source?**

<!-- If yes, please provide a link to the repository -->

**What category of layer 2 is it? (Optimistic, ZK)**

<!-- Please provide some information on what kind of layer 2 this is -->

**Does the layer 2 use Ethereum Mainnet for data availability?**

<!-- Please provide proof thats the layer 2 uses Ethereum for data availability -->

**Which bridges are used to onboard?**

<!-- Please provide some information on how to bridge assets onto this layer 2 -->

**Which exchanges offer support for the project?**

<!-- If there is exchange support for deposits/withdrawals, please provide information for this -->

**Link to dapp ecosystem (if applicable)**

<!-- Please provide a link to the dapp ecosystem. (ex: https://portal.arbitrum.one/, https://www.optimism.io/apps/all) -->

**Token contract list (if applicable)**

<!-- Since assets will have a new address on layer 2, if there is a token list resource available please share -->

**What date did this project go live?**

<!-- Please provide proof to substantiate this date -->

**Is this project a fork? If yes, which project was forked?**

<!-- Please provide information about if this project is a fork -->

**What wallets support this layer 2?**

<!-- Please list wallets that support this network -->

**How can users and/or developers connect to this layer 2?**

<!-- What is the public RPC information for the network? (RPC URL, Chain ID, Currency Symbol) -->

**Has this project undergone an external security audit and/or bug bounty?**

<!-- Please provide a link to a report or repo for any audits or bug bounties. If you haven't been audited but think your layer 2 should be listed anyway, explain here. -->

**Has the project sustained its users over time?**

<!-- Please provide supporting information such as TVL history, transaction statistics, and whether it is used by known companies or projects. -->

**Is the project being actively maintained?**

<!-- Is there an active team developing the project? -->

**Is there a block explorer?**

<!-- Are there block explorers for the network? Please share URLs. -->
126 changes: 126 additions & 0 deletions .github/ISSUE_TEMPLATE/suggest_staking_product.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,126 @@
---
name: Suggest a staking product or service
about: Suggest a staking product or service to list on ethereum.org
title: ""
labels: "feature :sparkles:, content :fountain_pen:"
assignees: ""
---

Before suggesting a staking product or service, make sure you've read [our listing policy](/contributing/adding-staking-product/).

Only continue with the issue if the staking product meets the criteria listed there.

If it does, complete the following information which we need to accurately list the product/service.

**Product type**

<!-- Which category best fits the product or service? -->

- [ ] Node/client tooling
- [ ] Key management
- [ ] Staking as a service
- [ ] Staking pool
- [ ] Other: (describe)

<!-- Keep in mind, not all questions apply to every product type. -->

**Name**

<!-- Provide the official name of product or service. -->

**Logo**

<!-- Provide an SVG or hi-res transparent PNG. -->

**Description**

<!-- Provide a 1-2 sentence (240 character max) of the products or service. -->

**Website**

<!-- Provide a URL to the website for the product or service. -->

**If software is involved, is everything open source?**

<!-- Select one option, providing any available links to repositories. -->

- [ ] Yes, everything is open source: _provide link(s) to project repo(s)_
- [ ] Portions of code are open source: _provide link(s) to project repo(s)_
- [ ] No, code is closed source
- [ ] N/A, no custom software is involved

**Is the project a fork? If yes, which project was forked?**

<!-- Provide information about if the project is a fork. -->

**Is the product out of _beta_ development?**

<!-- Provide information as to where the product is in the development lifecycle -->

**What wallets support the product or service?**

<!-- List wallets that directly support the product or service. -->

**If the product or service enables staking with <32 ETH, what is the minimum ETH required to stake?**

<!-- Provide any details related to ETH requirements, any other staking requirements, and any fees related to the service -->

**If a service, what are the fees associated with using the service?**

<!-- Is there a monthly fee for the service? Or a percentage of earnings? Any additional staking requirements? -->

**If the product or service involved a liquidity token, what are the tokens involved?**

<!-- Include token abbreviation and contract address for any tokens involved -->

**What date did the project or service go live?**

<!-- Provide proof to substantiate the date of when the product or service became available to the public -->

**Has the project undergone an external security audit?**

<!-- Provide a link to a report or repo. If none, are there plans to be audited? -->

**Has the project undergone any security bug bounties?**

<!-- Provide a link to a report or repo. If none, are there plans to hold a bug bounty? -->

**Is the project being actively maintained?**

<!-- Is there an active team developing the project? -->

**Is the product or service free of trusted/human intermediaries?**

<!-- Disclose any steps in a stakers journey that depend on trusting humans with the keys to their funds or distribution of rewards. -->

**If a pooled staking service, can users participate as a node operator without permission?**

<!-- Is permission to run a node controlled by an individual, company or DAO? -->

**If listing a staking-as-a-service, are users required to sign-up for an account?**

<!-- List any permissions needed for a user to access the service. -->

**If listing a staking-as-a-service, who holds the signing keys, and withdrawal keys?**

<!-- What keys does the user maintain access to? What keys does the service gain access to? -->

**If a pooled staking service, what percent of node operators are running a supermajority CL client?**

<!-- As of last edit, Prysm is the CL client being run by a supermajority of node operators, which is dangerous for the network. If there is currently a supermajority and this data is known, please list it here with link to evidence. -->

**If listing node or client tooling, which CL clients (Lighthouse, Teku, Nimbus or Prysm) are supported?**

<!-- Which clients are supported? Does the software provide an easy way to switch between clients? -->

**What platforms are supported?**

<!-- ie. Linux, macOS, Windows, iOS, Android -->

**What user interfaces are supported?**

<!-- ie. browser app, desktop app, mobile app, CLI app -->

**Social media links**

<!-- List available social media links. ie. Discord, Twitter, Telegram, Reddit-->
4 changes: 3 additions & 1 deletion .github/ISSUE_TEMPLATE/suggest_wallet.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,12 @@
name: Suggest a wallet
about: Suggest a new wallet to list on ethereum.org
title: ""
labels: "feature :sparkles:, content :fountain_pen:"
labels: "wallet :purse:,"
assignees: ""
---

_Please note as part of [our Q2 product roadmap](https://github.com/ethereum/ethereum-org-website/issues/6161) we paused adding new wallets until we establish new, expanded criteria._

Before suggesting a wallet, make sure you've read [our listing policy](https://www.ethereum.org/en/contributing/adding-products/).

Only continue with the issue if your wallet meets the criteria listed there.
Expand Down
Loading

0 comments on commit b7cb0a8

Please sign in to comment.