Merge branch 'dev' into pr/pete-vielhaber/16528

Author: wackerow

.all-contributorsrc

@@ -1305,7 +1305,7 @@
     },
     {
       "login": "wslyvh",
-      "name": "Wesley van Heije",
+      "name": "Wesley",
       "avatar_url": "https://avatars2.githubusercontent.com/u/25974464?v=4",
       "profile": "https://twitter.com/wslyvh",
       "contributions": [
@@ -13770,6 +13770,15 @@
       "contributions": [
         "tool"
       ]
+    },
+    {
+      "login": "baiwfg2",
+      "name": "Lewis Chan",
+      "avatar_url": "https://avatars.githubusercontent.com/u/5157680?v=4",
+      "profile": "https://github.com/baiwfg2",
+      "contributions": [
+        "content"
+      ]
     }
   ],
   "contributorsPerLine": 7,

README.md

@@ -399,7 +399,7 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
       <td align="center" valign="top" width="14.28%"><a href="https://www.yazkhoury.com"><img src="https://avatars2.githubusercontent.com/u/9094204?v=4?s=100" width="100px;" alt="Yaz Khoury"/><br /><sub><b>Yaz Khoury</b></sub></a><br /><a href="#content-YazzyYaz" title="Content">🖋</a></td>
       <td align="center" valign="top" width="14.28%"><a href="http://yos.io"><img src="https://avatars3.githubusercontent.com/u/1084226?v=4?s=100" width="100px;" alt="Yos Riady"/><br /><sub><b>Yos Riady</b></sub></a><br /><a href="#content-yosriady" title="Content">🖋</a></td>
       <td align="center" valign="top" width="14.28%"><a href="http://infura.io"><img src="https://avatars2.githubusercontent.com/u/1210802?v=4?s=100" width="100px;" alt="Andrew Cohen"/><br /><sub><b>Andrew Cohen</b></sub></a><br /><a href="https://github.com/ethereum/ethereum-org-website/issues?q=author%3Aandrewjcohen" title="Bug reports">🐛</a></td>
-      <td align="center" valign="top" width="14.28%"><a href="https://twitter.com/wslyvh"><img src="https://avatars2.githubusercontent.com/u/25974464?v=4?s=100" width="100px;" alt="Wesley van Heije"/><br /><sub><b>Wesley van Heije</b></sub></a><br /><a href="#content-wslyvh" title="Content">🖋</a> <a href="#infra-wslyvh" title="Infrastructure (Hosting, Build-Tools, etc)">🚇</a></td>
+      <td align="center" valign="top" width="14.28%"><a href="https://twitter.com/wslyvh"><img src="https://avatars2.githubusercontent.com/u/25974464?v=4?s=100" width="100px;" alt="Wesley"/><br /><sub><b>Wesley</b></sub></a><br /><a href="#content-wslyvh" title="Content">🖋</a> <a href="#infra-wslyvh" title="Infrastructure (Hosting, Build-Tools, etc)">🚇</a></td>
     </tr>
     <tr>
       <td align="center" valign="top" width="14.28%"><a href="https://github.com/gr0uch0dev"><img src="https://avatars1.githubusercontent.com/u/17497722?v=4?s=100" width="100px;" alt="gr0uch0dev"/><br /><sub><b>gr0uch0dev</b></sub></a><br /><a href="#content-gr0uch0dev" title="Content">🖋</a></td>
@@ -2131,6 +2131,7 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
     </tr>
     <tr>
       <td align="center" valign="top" width="14.28%"><a href="https://github.com/trikunai"><img src="https://avatars.githubusercontent.com/u/46504155?v=4?s=100" width="100px;" alt="trikunai"/><br /><sub><b>trikunai</b></sub></a><br /><a href="#tool-trikunai" title="Tools">🔧</a></td>
+      <td align="center" valign="top" width="14.28%"><a href="https://github.com/baiwfg2"><img src="https://avatars.githubusercontent.com/u/5157680?v=4?s=100" width="100px;" alt="Lewis Chan"/><br /><sub><b>Lewis Chan</b></sub></a><br /><a href="#content-baiwfg2" title="Content">🖋</a></td>
     </tr>
   </tbody>
 </table>

public/content/decentralized-identity/index.md

@@ -160,7 +160,7 @@ There are many ambitious projects using Ethereum as a foundation for decentraliz
 - **[Ethereum Name Service (ENS)](https://ens.domains/)** - _A decentralized naming system for onchain, machine-readable identifiers, like, Ethereum wallet addresses, content hashes, and metadata._
 - **[Sign in with Ethereum (SIWE)](https://siwe.xyz/)** - _Open standard for authentication with Ethereum accounts._
 - **[SpruceID](https://www.spruceid.com/)** - _A decentralized identity project which allows users to control digital identity with Ethereum accounts and ENS profiles instead of relying on third-party services._
-- **[Ethereum Attestation Service (EAS)](https://attest.sh/)** - _A decentralized ledger/protocol for making onchain or offchain attestations about anything._
+- **[Ethereum Attestation Service (EAS)](https://attest.org/)** - _A decentralized ledger/protocol for making onchain or offchain attestations about anything._
 - **[Proof of Humanity](https://www.proofofhumanity.id)** - _Proof of Humanity (or PoH) is a social identity verification system built on Ethereum._
 - **[BrightID](https://www.brightid.org/)** - _A decentralized, open-source social identity network seeking to reform identity verification through the creation and analysis of a social graph._
 - **[walt.id](https://walt.id)** — _Open source decentralized identity and wallet infrastructure that enables developers and organizations to leverage self-sovereign identity and NFTs/SBTs._

public/content/developers/docs/apis/backend/index.md

@@ -25,7 +25,7 @@ These libraries abstract away much of the complexity of interacting directly wit
 **Alchemy -** **_Ethereum Development Platform._**
 
 - [alchemy.com](https://www.alchemy.com/)
-- [Documentation](https://docs.alchemy.com/)
+- [Documentation](https://www.alchemy.com/docs/)
 - [GitHub](https://github.com/alchemyplatform)
 - [Discord](https://discord.com/invite/alchemyplatform)
 
@@ -61,7 +61,7 @@ These libraries abstract away much of the complexity of interacting directly wit
 **GetBlock-** **_Blockchain-as-a-service for Web3 development_**
 
 - [GetBlock.io](https://getblock.io/)
-- [Documentation](https://getblock.io/docs/)
+- [Documentation](https://docs.getblock.io/)
 
 **Infura -** **_The Ethereum API as a service._**
 
@@ -77,7 +77,7 @@ These libraries abstract away much of the complexity of interacting directly wit
 **NOWNodes - _Full Nodes and Block Explorers._**
 
 - [NOWNodes.io](https://nownodes.io/)
-- [Documentation](https://documenter.getpostman.com/view/13630829/TVmFkLwy#intro)
+- [Documentation](https://nownodes.gitbook.io/documentation)
 
 **QuickNode -** **_Blockchain Infrastructure as a Service._**
 
@@ -114,7 +114,7 @@ These libraries abstract away much of the complexity of interacting directly wit
 
 **Python Tooling -** **_Variety of libraries for Ethereum interaction via Python._**
 
-- [py.ethereum.org](https://python.ethereum.org/)
+- [py.ethereum.org](https://snakecharmers.ethereum.org/)
 - [web3.py GitHub](https://github.com/ethereum/web3.py)
 - [web3.py Chat](https://gitter.im/ethereum/web3.py)
 
@@ -152,8 +152,8 @@ These libraries abstract away much of the complexity of interacting directly wit
 
 **Coinbase Cloud Node -** **_Blockchain Infrastructure API._**
 
-- [Coinbase Cloud Node](https://www.coinbase.com/cloud)
-- [Documentation](https://docs.cloud.coinbase.com/)
+- [Coinbase Cloud Node](https://www.coinbase.com/developer-platform)
+- [Documentation](https://docs.cdp.coinbase.com/)
 
 **DataHub by Figment -** **_Web3 API services with Ethereum Mainnet and testnets._**
 

public/content/developers/docs/apis/json-rpc/index.md

@@ -565,7 +565,7 @@ curl -X POST --data '{"jsonrpc":"2.0","method":"eth_accounts","params":[],"id":1
 
 ### eth_blockNumber {#eth_blocknumber}
 
-Returns the number of most recent block.
+Returns the number of the most recent block.
 
 <ButtonLink size="sm" variant="outline" href="https://ethereum-json-rpc.com/?method=eth_blockNumber">
   Try endpoint in playground
@@ -594,7 +594,7 @@ curl -X POST --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id
 
 ### eth_getBalance {#eth_getbalance}
 
-Returns the balance of the account of given address.
+Returns the balance of the account at a given address.
 
 <ButtonLink size="sm" variant="outline" href="https://ethereum-json-rpc.com/?method=eth_getBalance">
   Try endpoint in playground
@@ -658,7 +658,7 @@ contract Storage {
 }
 ```
 
-Retrieving the value of pos0 is straight forward:
+Retrieving the value of pos0 is straightforward:
 
 ```js
 curl -X POST --data '{"jsonrpc":"2.0", "method": "eth_getStorageAt", "params": ["0x295a70b2de5e3953354a6a8344e616ed314d7251", "0x0", "latest"], "id": 1}' localhost:8545
@@ -720,7 +720,7 @@ params: [
 
 **Returns**
 
-`QUANTITY` - integer of the number of transactions send from this address.
+`QUANTITY` - integer of the number of transactions sent from this address.
 
 **Example**
 
@@ -1102,7 +1102,7 @@ Generates and returns an estimate of how much gas is necessary to allow the tran
 
 **Parameters**
 
-See [eth_call](#eth_call) parameters, except that all properties are optional. If no gas limit is specified geth uses the block gas limit from the pending block as an upper bound. As a result the returned estimate might not be enough to executed the call/transaction when the amount of gas is higher than the pending block gas limit.
+See [eth_call](#eth_call) parameters, except that all properties are optional. If no gas limit is specified geth uses the block gas limit from the pending block as an upper bound. As a result the returned estimate might not be enough to execute the call/transaction when the amount of gas is higher than the pending block gas limit.
 
 **Returns**
 
@@ -1172,10 +1172,9 @@ params: [
 curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBlockByHash","params":["0xdc0818cf78f21a8e70579cb46a43643f78291264dda342ae31049421c82d21ae", false],"id":1}'
 // Result
 {
-{
-"jsonrpc": "2.0",
-"id": 1,
-"result": {
+  "jsonrpc": "2.0",
+  "id": 1,
+  "result": {
     "difficulty": "0x4ea3f27bc",
     "extraData": "0x476574682f4c5649562f76312e302e302f6c696e75782f676f312e342e32",
     "gasLimit": "0x1388",
@@ -1198,7 +1197,7 @@ curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getBlockByHash","params":["0
     "transactionsRoot": "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
     "uncles": [
     ]
-}
+  }
 }
 ```
 
@@ -1394,7 +1393,7 @@ params: ["0x85d995eba9763907fdf35cd2034144dd9d53ce32cbec21349d4b12823c6860c5"]
 
 It also returns _either_ :
 
-- `root` : `DATA` 32 bytes of post-transaction stateroot (pre Byzantium)
+- `root` : `DATA` 32 bytes of post-transaction state root (pre Byzantium)
 - `status`: `QUANTITY` either `1` (success) or `0` (failure)
 
 **Example**
@@ -1431,7 +1430,7 @@ curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionReceipt","para
 
 ### eth_getUncleByBlockHashAndIndex {#eth_getunclebyblockhashandindex}
 
-Returns information about a uncle of a block by hash and uncle index position.
+Returns information about an uncle of a block by hash and uncle index position.
 
 <ButtonLink size="sm" variant="outline" href="https://ethereum-json-rpc.com/?method=eth_getUncleByBlockHashAndIndex">
   Try endpoint in playground
@@ -1465,7 +1464,7 @@ Result see [eth_getBlockByHash](#eth_getblockbyhash)
 
 ### eth_getUncleByBlockNumberAndIndex {#eth_getunclebyblocknumberandindex}
 
-Returns information about a uncle of a block by number and uncle index position.
+Returns information about an uncle of a block by number and uncle index position.
 
 <ButtonLink size="sm" variant="outline" href="https://ethereum-json-rpc.com/?method=eth_getUncleByBlockNumberAndIndex">
   Try endpoint in playground
@@ -1777,7 +1776,7 @@ This will start the HTTP RPC interface on `http://localhost:8545`.
 We can verify that the interface is running by retrieving the coinbase address (by obtaining the first address from the array of accounts) and balance using [curl](https://curl.se). Please note that data in these examples will differ on your local node. If you want to try these commands, replace the request params in the second curl request with the result returned from the first.
 
 ```bash
-curl --data '{"jsonrpc":"2.0","method":"eth_accounts","params":[]", "id":1}' -H "Content-Type: application/json" localhost:8545
+curl --data '{"jsonrpc":"2.0","method":"eth_accounts","params":[], "id":1}' -H "Content-Type: application/json" localhost:8545
 {"id":1,"jsonrpc":"2.0","result":["0x9b1d35635cc34752ca54713bb99d38614f63c955"]}
 
 curl --data '{"jsonrpc":"2.0","method":"eth_getBalance", "params": ["0x9b1d35635cc34752ca54713bb99d38614f63c955", "latest"], "id":2}' -H "Content-Type: application/json" localhost:8545
@@ -1793,7 +1792,7 @@ web3.fromWei("0x1639e49bba16280000", "ether")
 
 Now that there is some ether on our private development chain, we can deploy the contract. The first step is to compile the Multiply7 contract to byte code that can be sent to the EVM. To install solc, the Solidity compiler, follow the [Solidity documentation](https://docs.soliditylang.org/en/latest/installing-solidity.html). (You might want to use an older `solc` release to match [the version of compiler used for our example](https://github.com/ethereum/solidity/releases/tag/v0.4.20).)
 
-The next step is to compile the Multiply7 contract to byte code that can be send to the EVM.
+The next step is to compile the Multiply7 contract to byte code that can be sent to the EVM.
 
 ```bash
 echo 'pragma solidity ^0.4.16; contract Multiply7 { event Print(uint); function multiply(uint input) public returns (uint) { Print(input * 7); return input * 7; } }' | solc --bin

public/content/developers/docs/blocks/index.md

@@ -50,36 +50,36 @@ There is a lot of information contained within a block. At the highest level a b
 
 The block `body` contains several fields of its own:
 
-| Field                | Description                                        |
-| :------------------- | :------------------------------------------------- |
-| `randao_reveal`      | a value used to select the next block proposer     |
-| `eth1_data`          | information about the deposit contract             |
-| `graffiti`           | arbitrary data used to tag blocks                  |
-| `proposer_slashings` | list of validators to be slashed                   |
-| `attester_slashings` | list of attesters to be slashed                   |
-| `attestations`       | list of attestations in favor of the current block |
-| `deposits`           | list of new deposits to the deposit contract       |
-| `voluntary_exits`    | list of validators exiting the network             |
-| `sync_aggregate`     | subset of validators used to serve light clients   |
-| `execution_payload`  | transactions passed from the execution client      |
+| Field                | Description                                      |
+| :------------------- | :----------------------------------------------- |
+| `randao_reveal`      | a value used to select the next block proposer   |
+| `eth1_data`          | information about the deposit contract           |
+| `graffiti`           | arbitrary data used to tag blocks                |
+| `proposer_slashings` | list of validators to be slashed                 |
+| `attester_slashings` | list of attesters to be slashed                  |
+| `attestations`       | list of attestations made against previous slots |
+| `deposits`           | list of new deposits to the deposit contract     |
+| `voluntary_exits`    | list of validators exiting the network           |
+| `sync_aggregate`     | subset of validators used to serve light clients |
+| `execution_payload`  | transactions passed from the execution client    |
 
 The `attestations` field contains a list of all the attestations in the block. Attestations have their own data type that contains several pieces of data. Each attestation contains:
 
-| Field              | Description                                                 |
-| :----------------- | :---------------------------------------------------------- |
-| `aggregation_bits` | a list of which validators participated in this attestation |
-| `data`             | a container with multiple subfields                         |
-| `signature`        | aggregate signature of all attesting validators             |
+| Field              | Description                                                    |
+| :----------------- | :------------------------------------------------------------- |
+| `aggregation_bits` | a list of which validators participated in this attestation    |
+| `data`             | a container with multiple subfields                            |
+| `signature`        | aggregate signature of a set of validators against `data` part |
 
 The `data` field in the `attestation` contains the following:
 
-| Field               | Description                                              |
-| :------------------ | :------------------------------------------------------- |
-| `slot`              | the slot the attestation relates to                      |
-| `index`             | indices for attesting validators                         |
-| `beacon_block_root` | the root hash of the Beacon block containing this object |
-| `source`            | the last justified checkpoint                            |
-| `target`            | the latest epoch boundary block                          |
+| Field               | Description                                                     |
+| :------------------ | :-------------------------------------------------------------- |
+| `slot`              | the slot the attestation relates to                             |
+| `index`             | indices for attesting validators                                |
+| `beacon_block_root` | the root hash of the Beacon block seen as the head of the chain |
+| `source`            | the last justified checkpoint                                   |
+| `target`            | the latest epoch boundary block                                 |
 
 Executing the transactions in the `execution_payload` updates the global state. All clients re-execute the transactions in the `execution_payload` to ensure the new state matches that in the new block `state_root` field. This is how clients can tell that a new block is valid and safe to add to their blockchain. The `execution payload` itself is an object with several fields. There is also an `execution_payload_header` that contains important summary information about the execution data. These data structures are organized as follows:
 

public/content/developers/docs/data-availability/index.md

@@ -73,7 +73,7 @@ The core Ethereum protocol is primarily concerned with data availability, not da
 ## Further reading {#further-reading}
 
 - [WTF is Data Availability?](https://medium.com/blockchain-capital-blog/wtf-is-data-availability-80c2c95ded0f)
-- [What Is Data Availability?](https://coinmarketcap.com/alexandria/article/what-is-data-availability)
+- [What Is Data Availability?](https://coinmarketcap.com/academy/article/what-is-data-availability)
 - [A primer on data availability checks](https://dankradfeist.de/ethereum/2019/12/20/data-availability-checks.html)
 - [An explanation of the sharding + DAS proposal](https://hackmd.io/@vbuterin/sharding_proposal#ELI5-data-availability-sampling)
 - [A note on data availability and erasure coding](https://github.com/ethereum/research/wiki/A-note-on-data-availability-and-erasure-coding#can-an-attacker-not-circumvent-this-scheme-by-releasing-a-full-unavailable-block-but-then-only-releasing-individual-bits-of-data-as-clients-query-for-them)

src/components/StartWithEthereumFlow/LetUseSomeApps/index.tsx

@@ -9,9 +9,9 @@ import { Tag } from "@/components/ui/tag"
 import { trackCustomEvent } from "@/lib/utils/matomo"
 
 import AaveImage from "@/public/images/dapps/aave.png"
+import FarcasterImage from "@/public/images/dapps/farcaster.png"
 import OpenSeaImage from "@/public/images/dapps/opensea.png"
 import UniswapImage from "@/public/images/dapps/uni.png"
-import WarpcastImage from "@/public/images/dapps/warpcast.png"
 
 const LetUseSomeApps = ({
   stepIndex,
@@ -24,8 +24,8 @@ const LetUseSomeApps = ({
 
   const dappsList = [
     {
-      name: "Warpcast",
-      description: t("page-start-apps-warpcast-description"),
+      name: "Farcaster",
+      description: t("page-start-apps-farcaster-description"),
       tag: (
         <Tag
           status="tag"
@@ -35,8 +35,8 @@ const LetUseSomeApps = ({
           {t("page-start-apps-socials-tag")}
         </Tag>
       ),
-      url: "https://warpcast.com/",
-      image: WarpcastImage,
+      url: "https://www.farcaster.xyz/",
+      image: FarcasterImage,
     },
     {
       name: "Aave",

src/components/UpcomingEventsList.tsx

@@ -96,7 +96,7 @@ const UpcomingEventsList = () => {
     })
   }
 
-  if (Object.keys(monthGroupedEvents)?.length) {
+  if (Object.keys(monthGroupedEvents)?.length === 0) {
     return (
       <Alert variant="update">
         <AlertEmoji text=":information_source:" />