Staking glosari

---

Archival node

• Archive nodes diperlukan jika anda ada pertanyaan seperti baki akaun di dalam sebuah blok.

• Data ini diwakili dalam unit terabytes (lebih daripada 20TB untuk Geth), menjadikan archive nodes kurang menarik bagi kebanyakan pengguna tetapi sangat berguna untuk service seperti meneroka blok, vendor dompet, dan analisa rantaian.

Syncing clients dalam apa-apa mode selain daripada archive akan mengakibatkan pruned blockchain data. Ini bermakna mode lain tiada arkib sejarah penuh tetapi full node boleh membinanya jikalau diminta.

Archive nodes tidak diperlukan untuk terlibat dengan pengesahan blok dan secara teori ia boleh membina semula daripada genesis.

Attestation (Pengesahan)

Salah satu komponen penting berkaitan dengan keberkesanan ialah undi chain head. Ini merupakan undi dibuat validator bahawanya percaya blok itu adalah blok semasa dan sahih di rantaian pada masa pengesahan dibuat. Struktur undi chain head mengandungi komponen yang berikut:

• Slot - Definasi dimana validator percaya chain head semasa ialah apa.

• Hash - Definasi apa validator percaya chain head semasa ialah apa.

Kombinasi yang unik ini tentukan satu titik pada rantaian. Dengan mengabungkan secukupnya undi chain head rangkaian Ethereum mencapai konsesi keadaan rantaian.

Attestation aggregator

Aggregation mengambil pelbagai attestations yang telah dipilih untuk mengundi dengan committee yang sama bagi chain head vote, dan undi muktamad, selepas itu mencantumkan mereka kepada single aggregate attestation.

Satu aggregate attestation berbeza dalam dua cara dengan satu simple attestation. Yang pertama, ia mempunyai pelbagai validators disenarai. Yang kedua, the signature is an aggregate signature made from the signatures of the matching simple attestations. Aggregate attestations adalah sangat efisien untuk disimpan, tetapi mengandungi tambahan komunikasi dan beban komputasi.

Jika setiap validator diwajibkan aggregate semua attestations ia akan menyebabkan rangkaian segera terlebih beban dengan komunikasi yang diperlukan untuk hantar setiap attestation kepada setiap validator. Perkara yang sama, jika aggregating adalah pilihan validators tidak akan bazirkan sumber untuk membuat demikian. Oleh itu, satu subset validators dipilih oleh rangkaian untuk menjalankan tugas aggregation duties. Ini memanfaatkan jikalau tugas dilakukan dengan baik, kerana aggregate attestations dengan validators yang banyak mempunyai lebih kebarangkalian disertakan dalam rantaian menyebabkan validator juga lebih kebarangkalian menerima ganjaran.

Validators yang menjalankan tugas aggregation process dipanggil aggregators.

Beacon chain

Senarai ini digunakan untuk:

• Tugaskan validators tugas mereka.

• Melaksanakan protokol level random number generation (RNG).

• Kemajuan beacon chain.

Block (Blok)

Block proposer

Block status

Proposed

Blok dicadangkan oleh validator.

Scheduled

Validators sedang menyalurkan data.

Missed/skipped

Pencadang tidak mencadangkan blok pada masa yang ditentukan, oleh itu blok missed/skipped.

Orphaned

Untuk memahami, mari kita tengok penerangan di bawah "1, 2, 3, ... ,9" mewakili slots.

1. Validator di slot 1 mencadangkan the block “a”.

2. Validator at slot 2 mencadangkan “b”.

3. Slot 4 dilangkau kerana tidak mencadangkan blok (e.g.: offline).

4. Di slot 5/6 a fork occurs: Validator(5) mencadangkan blok, tetapi validator(6) tidak menerima data tersebut (e.g.: the block didn’t reach them fast enough). Oleh itu Validator(6) mencadangkan bloknya decent informasi yang paling baru daripada validator(3).

Canonical chain (Rantaian utama)

Chain head

Checkpoints

Client

Committees

Consensus layer

Deposit contract

Effectiveness

Purata masa diperlukan untuk validator's attestations dimasukkan kepada rangkaian.

Epoch

Execution layer

Finalization

Untuk menentukan jikalau satu epoch telah dimuktamadkan, validators perlu bersetuju untuk dua epochs terbaru sekaligus berturut-turut, selepas itu semua Epochs sebelumnya boleh dikira sebagai muktamad.

Finality issues

Fork

Full node

Menyimpan dan mengekalkan data penuh rantaian blok pada disk. It serves blockchain data upon request and helps support the network by participating in block validation and by verifying all blocks and states. All states can be derived from a Full node.

Genesis block

The first block in a blockchain, used to initialize a particular network and its cryptocurrency.

Hard fork

Head vote

Inactivity leak

Inclusion distance

The value of an attestation to the Ethereum network is dependent on its inclusion distance, with a low inclusion distance being preferable. This is because the sooner the information is presented to the network, the more useful it is.

To reflect the relative value of an attestation, the reward given to a validator for attesting is scaled according to the inclusion distance. Specifically, the reward is multiplied by 1/d, where d is the inclusion distance.

Input data

Justification

When another block is justified on top of a justified block, it is upgraded to "finalized". Finalizing a block is a commitment to include the block in the canonical chain.

Light clients

An Ethereum client that does not store a local copy of the blockchain, or validate blocks and transactions. It offers the functions of a wallet and can create and broadcast transactions.

MEV

Mempool

When an Ethereum node receives a transaction, it is not instantly added to a block. The transaction is held in a waiting area or a buffer zone.

The transaction goes from a number of levels of verification such as it checks whether the output is greater than the input, whether the signature is valid or not, etc., and then only it is added to a block. The transaction is not added to a block if it fails any of these validations. The role of a mempool comes while a transaction is going through these checks. It is simply kept in this waiting area or a mempool. As soon as the transaction confirms, it is removed from the mempool and added to a block. Mempool is not a master reference shared universally by all nodes. There’s no “one” mempool. This means each node configures its own rules for the node’s mempool. In fact, a node can be the first to receive a transaction but it is possible that it might not have propagated the transaction to the rest of the network.

Node

Any instance of Ethereum client software that is connected to other computers also running Ethereum software, forming a network. A node doesn’t necessarily need a validator but a validator requires a node. Running a node by itself does not generate any revenue but does contribute to the robustness of the network.

Operator

A person who maintains a validator

Participation rate

The participation rate is the percentage of validators that are online and performing their duties.

If the validator set is 1,000 validators, and 250 validators are offline or rarely making proposals or attestations, then it could be estimated that the participation rate is 75%.

Peers

Other nodes running Ethereum clients that connect to each other over a peer-to-peer network. Communication between peers is how the Ethereum network remains decentralized as there is no single point of failure.

Priority fees

Private key

A secret number that allows Ethereum users to prove ownership of an account or contracts, by producing a digital signature.

Proof of stake (PoS)

A method by which a cryptocurrency blockchain protocol aims to achieve distributed consensus. PoS asks users to prove ownership of a certain amount of cryptocurrency (their "stake" in the network) in order to be able to participate in the validation of transactions.

Public key

Signing

Slashable offenses

There are three ways a validator can be slashed, all of which amount to the dishonest proposal or attestation of blocks.

Attestation violation

• Surround votes: Attesting to a block that "surrounds" another one (effectively changing history).

Proposer violation

Slasher node

Slot

Solo staker

An operator who runs a validator on the Ethereum network without a protocol between their validator and the Beaconchain

Source vote

Staker

Someone who has deposited ETH into a validator to secure the network. This can be someone who runs a validator (an operator) or someone who deposited their ETH into a pool, where someone else is the operator of the validator.

Staking deposit CLI

A command-line tool used to generate validator keys and deposit data files.

Suggested fee recipient

Sync committee

Target vote

Validator

Eligible for activation & Estimated activation

Unique index

Current balance & Effective balance

The current balance is the amount of ETH held by the validator as of now. The effective Balance represents a value calculated by the current balance. It is used to determine the size of a reward or penalty a validator receives. The effective balance can never be higher than 32 ETH.

In order to increase the effective balance, the validator requires “effective balance + 1.25 ETH”. In other words, if the effective balance is 20 ETH, a current balance of 21.25 ETH is required in order to have an effective balance of 21 ETH. The effective balance will adjust once it drops by 0.25 below the threshold as seen in the examples above.

Here are examples of how the effective balance changes:

• If the Current balance is 32.00 ETH – the Effective balance is 32.00 ETH.

• If the Current balance dropped from 22 ETH to 21.76 ETH – Effective balance will be 22.00 ETH.

• If the Current balance increases to 22.25 and the effective balance is 21 ETH, the effective balance will increase to 22 ETH.

Validator lifecycle

1. Deposited

32 ETH has been deposited to the ETH1 deposit-contract and this state will be kept for around 7 hours. This offers security in case the Ethereum chain gets attacked.

2. Pending

3. Active validator

Currently attesting and proposing blocks.

The validator will stay active until:

• Its balance drops below 16 ETH (ejected).

• Voluntary exit.

• It gets slashed.

4. Slashing validator

The Validator has been malicious and will be slashed and kicked out of the system.

A Penalty is a negative reward (e.g. for going offline). A Slashing is a large penalty (≥ 1/32 of balance at stake) and a forceful exit ... . - Justin Drake

5. Exiting validator

• Ejected: The validator balance fell below a threshold and was kicked out by the network.

• Exited: Voluntary exit, the withdrawal key holder has the ability to withdraw the current balance of the corresponding validator balance.

Validator pool

Validator queue

• 5 validators per epoch requires 327680 active validators, allowing 1125 validators per day.

• 6 validators per epoch requires 393216 active validators, allowing 1350 validators per day.

• 7 validators per epoch requires 458752 active validators, allowing 1575 validators per day.

• 8 validators per epoch requires 524288 active validators, allowing 1800 validators per day.

• 9 validators per epoch requires 589824 active validators, allowing 2025 validators per day.

• 10 validators per epoch requires 655360 active validators, allowing 2200 validators per day.

• Amount of activations scales with the amount of active validators and the limit is the active validator set divided by 64.

Exiting validators works in the same way, with the amount of validators that can exit the Beacon Chain per day rate limited to preserve the stability of the network.

Validator seed phrase / mnemonic

The Seed Phrase or Mnemonic is a set of words (usually 12, 18 or 24 words long) used to generate your validator keys. Your mnemonic is the backup for your validator keys and will be the ONLY way to withdraw your ETH when the time comes and no one can help you recover your mnemonic if you lose it.

Withdrawal address