feat: DevP2P

docs/wiki/dev/cs-resources.md

@@ -52,9 +52,33 @@
 
 ## Networking
 
+This section covers a brief overview of the differences and similarities between the OSI (Open Systems Interconnection) and TCP/IP (Transmission Control Protocol/Internet Protocol) models,
+as well as the protocols involved in the transport layer used in DevP2P: TCP and UDP.
+
+In terms of networking, both models refer to the same process of communication between layers.
+Just as Kurose and Ross explain (2020), the computer networks are divided into different layers, and each one of them has a specific responsibility. The OSI model has seven layers, while the TCP/IP model has four layers. The OSI model is more theoretical and the TCP/IP model is more practical.
+The OSI model is a reference model created by the International Organization for Standardization (ISO) to provide a framework for understanding networks. The TCP/IP model was created by the Department of Defense (DoD) to ensure that messages could be transmitted between computers regardless of the types of computers involved.
+The TCP/IP model is a concise version of the OSI model:
+
+![alt text](../../images/el-architecture/osi-tcpip-models.png)
+
+In summary, the OSI model layers are:
+1. Physical layer: responsible for the transmission and reception of raw data between devices.
+2. Data link layer: responsible for the node-to-node delivery of the message.
+3. Network layer: responsible for the delivery of packets from the source to the destination.
+4. Transport layer: responsible for the delivery of data between the source and the destination.
+5. Session layer: responsible for the establishment, management, and termination of connections between applications.
+6. Presentation layer: responsible for the translation, compression, and encryption of data.
+7. Application layer: responsible for providing network services directly to the end-user.
+
+Assuming the communication schema proposed by Claude Shannon (1948), every communication implies both a sender and a receiver, a message to be exchanged between them, a transmission medium, and a protocol to be followed.
+This is important to mention because regardless of the computer architecture, it could be part of a network if it follows the communication and protocol specifications of the models mentioned above.
+
 - 🎥 [Introduction to Computer Networking](https://www.youtube.com/playlist?list=PLEAYkSg4uSQ2dr0XO_Nwa5OcdEcaaELSG)
 - 🎥 [Computers and the Internet | Khan Academy](https://www.khanacademy.org/computing/code-org/computers-and-the-internet)
 - 🎥 [Computer Networking: a Top-Down Approach](https://gaia.cs.umass.edu/kurose_ross/online_lectures.htm)
+- Clause E. Shannon (1948). "A Mathematical Theory of Communication". *Bell System Technical Journal*. Vol. 27.
+- Jim Kurose and Keith Ross (2020). *Computer Networking: A Top-Down Approach*. 8th edition. Pearson.
 
 ## Distributed systems and blockchain
 

docs/wiki/pectra-faq.md

@@ -147,9 +147,8 @@
 
 The consolidation will fail as the validators must be active on the beacon chain at the time of consolidation execution.
 
 #### **Q:** Whats the ABI of the consolidation system contract?
-
-The EIP-7251 consolidations contract is deployed here `0x0000BBdDc7CE488642fb579F8B00f3a590007251`, here you can find the [source](https://github.com/ethereum/sys-asm/blob/main/src/consolidations/main.eas).
+The EIP-7251 consolidations contract is deployed here `0x0000BBdDc7CE488642fb579F8B00f3a590007251`, source here: https://github.com/ethereum/sys-asm/blob/main/src/consolidations/main.eas. 
 The consolidations are put in a queue and dequeued at a rate of 2 per block.
 The contract is not written in solidity, nor do they have a typical solidity ABI in order to not enshrine the API.
 
@@ -196,7 +195,7 @@
 
 #### **Q:** Whats the ABI of the withdrawal system contract?
 
-The EIP-7002 contract is deployed here `0x00000961Ef480Eb55e80D19ad83579A64c007002` you can find the [source here](https://github.com/ethereum/sys-asm/blob/main/src/withdrawals/main).
+The EIP-7002 contract is deployed here `0x00000961Ef480Eb55e80D19ad83579A64c00700` source here: https://github.com/ethereum/sys-asm/blob/main/src/withdrawals/main. 
 The withdrawals are put in a queue and at maximum 16 are dequeued per block.
 The contract is not written in solidity, nor do they have a typical solidity ABI in order to not enshrine the API.
 The functionality of the withdrawal contract in pseudo code:

wordlist.txt

@@ -12,6 +12,7 @@ ACD
 ACL
 addons
 Aditional
+AES
 aggregative
 Akula
 Aleth
@@ -90,6 +91,8 @@ Boneh
 bool
 booleans
 bootup
+bootnode
+bootnodes
 borderless
 BPE
 broadcasted
@@ -140,6 +143,7 @@ Composability
 composable
 computability
 computable
+connectionless
 config
 congestions
 Conor
@@ -177,6 +181,7 @@ dapp
 Dapplion
 dapps
 DAS
+Datagram
 dataset
 deboost
 decrementation
@@ -204,12 +209,14 @@ Devops
 devp
 Devs
 DEX
+DHT
 Diffie
 DILITHIUM
 Dimitar
 disambiguated
 Discordo
 discv
+discport
 distro
 DNS
 docsify
@@ -228,6 +235,7 @@ EAL
 EB
 ECADD
 ECC
+ECDH
 ECDSA
 ECDSA's
 ECMUL
@@ -250,9 +258,12 @@ ELs
 EL's
 emptyset
 Encodings
+endian
 Endian
 enr
 env
+enode
+ENR
 EOA
 EOAs
 EOF
@@ -274,6 +285,7 @@ ethash
 Ethash
 ETHCC
 Ethereum
+Ethereumjs
 Ethereum's
 Ethernodes
 ethers
@@ -300,6 +312,7 @@ fanout
 farcaster
 fastssz
 faytey
+Feamster
 Feist
 Femboy
 Ferrin
@@ -346,6 +359,7 @@ getPayloadV
 getters
 ghost
 Gilles
+GCM
 Goerli
 Golang
 Goldwasser
@@ -388,6 +402,7 @@ IETF
 iframe
 ify
 Imandra
+img
 impera
 implementers
 incentivize
@@ -413,6 +428,7 @@ IOP
 IPC
 ipfs
 Ipsilon
+IPv
 IRTF
 ISA
 Jitsi
@@ -435,6 +451,7 @@ Kira
 Kleppmann
 Koblitz
 Kubernetes
+Kurose
 Kurtosis
 Kyber
 KZG
@@ -444,6 +461,7 @@ lceil
 ldots
 learnings
 Ledgerwatch
+Leffew
 Lefteris
 leftarrow
 leq
@@ -467,6 +485,7 @@ Longrightarrow
 lookahead
 lookups
 lor
+loopback
 LSB
 LSM
 LSP
@@ -516,6 +535,7 @@ MSB
 MSIZE
 mstore
 MUL
+multiaddr
 multiproofs
 Murr
 MVE
@@ -529,6 +549,8 @@ namespace
 namespaces
 Nand
 natively
+neighbours
+neighbourhood
 neq
 Nethermind
 neuder
@@ -584,6 +606,7 @@ pipelining
 PKCS
 Playdate
 pmod
+png
 POC
 POS
 POSIX
@@ -653,6 +676,7 @@ RANDAO
 Rareskills
 RB
 rceil
+reachability
 README
 reciept
 referrerpolicy
@@ -756,6 +780,8 @@ subcurrency
 subnet
 subnets
 suboptimal
+Subprotocol
+subprotocol
 subprotocols
 substack
 substate
@@ -766,6 +792,7 @@ Supermajority
 systemd
 Szabo
 Takenobu
+Tanenbaum
 Tani
 TBD
 tbhl
@@ -805,6 +832,7 @@ txdatanonzero
 txdatazero
 txpool
 txs
+UDP
 UI
 uint
 unaggregated
@@ -849,7 +877,9 @@ WB
 webkit
 WebRTC
 Whistleblower
+Wetherall
 Whitepaper
+WHOAREYOU
 WIP
 withdrawable
 withdrawalHash
@@ -954,5 +984,14 @@ Wireshark
 SigP
 opcode's
 Karim
+TalkReq
+Plaintext
+digram
+initating
+decrypts
+ECIES
+KDF
+HMAC
+decrypted
 trie's
-Synchronising
+Synchronising