Ethereum Verifier Check: In 97% of the time, all rewards above 32 ETH will be swept away

Pledge Ethereum: Prefix determines the fate of earnings

When you pledge Ethereum, a two-character prefix will determine whether your rewards will continue to accrue or be deducted regularly from the verifier balance. This is called a "Withdrawal Credential" and each validator is in one of three states: 0x00 , 0x01 , or 0x02 . Only if the type is 0x02 will the reward remain in the pledge and generate compound interest. For 0x01 , the portion exceeding 32 ETH will be automatically deducted. With 0x00 , you cannot access your balance at all.

On September 9, 2026, cryptoticker.io conducted statistics on the distribution in the verifier set. The results are unambiguous: 97.0% of active validators still stay on the old 0x01 type. The proportion of 0x02 using compound interest type is only 2.1% of . This analysis was completed by cryptoticker.io on September 9, 2026.

Lido introduces compound interest model to the test network: The trigger point on September 8

What prompted this count was the previous day's report. Crypto Briefing reported on September 8, 2026 that pledge provider Lido has launched a certificate type based 0x02 A new version of the Community Staking Module was built. This version currently runs only on the test network; it is reported that the main network release is scheduled for October 2026, but it still needs to be approved by Lido DAO. There is no guarantee that this date will be fulfilled as scheduled, and no such statement is made here.

What's really interesting is not the individual providers, but the model behind them. Large operators are currently migrating their validators to the compound interest type because this allows them to pool capital. Individuals who pledge individually often fall behind unknowingly. This gap is quantifiable, which is the reason explained in this article.

0x00 , 0x01 , and 0x02 : The meaning of the three validator credential types

Extracted credentials are records stored in the protocol that indicate where the validator's balance can flow. It is located in the verifier record on the beacon chain and does not appear in account reports or application settings. There are currently three prefixes in circulation, and their names remain unchanged in the protocol parameters. This newsroom has directly queried the public beacon node for these parameters.

Why prefixes rather than wallets are important

• 0x00 (BLS certificate): This is the original state of Shapella before the upgrade. The execution level does not store any withdrawal targets. As long as this situation persists, verifiers cannot pay rewards or release deposited funds. The balance is locked.
• 0x01 (Execution Address): This is the standard state since Shapella upgrade. An Ethereum address is stored and the withdrawal function is available. The key limit is the upper limit: the balance used to calculate rewards is capped at 32 ETH. Documentation at ethereum.org states that any balance above 32 ETH will be automatically cleared.
• 0x02 (Compound interest certificate): This is the type introduced in the Pectra upgrade. The upper limit here is increased to 2,048 ETH instead of 32 ETH. Rewards remain within the verifier and continue to earn interest in the next reward cycle. The parameter defined for this in the protocol is called MAX_EFFECTIVE_BALANCE_ELECTRA and has a value of 2,048,000,000 Gwei, which is exactly 2,048 ETH.

A frequently occurring term needs to be clearly defined here: Effective Balance refers to the portion of the balance that is rounded to the full ETH, which is used by the agreement to calculate rewards and penalties. Under the 0x01 type, no additional benefits will be gained for the excess.

Internal statistics: 97% of active validators still stay at 0x01

For analysis, the newsroom extracted two independent random samples from the entire verifier registry of the beacon chain between 15:56 and 16:00 UTC on September 9, 2026, with 6,000 indexes per sample, for a total of 12,000. Data is retrieved through the node operator's public beacon interface, and each request returns an HTTP status of 200. At the time of measurement, there were 2,362,534 issued verifier indexes in the registry ; 38.6% of the samples were active, and the rest had exited and received payment.

Among the 4,633 active validators in the sample, the distribution of credential types is as follows:

• 0x01 : 4,495 validators, accounting for 97.02%(95% confidence interval: 96.53% to 97.51%)
• 0x02 : 95 validators, accounting for 2.05%(1.64% to 2.46%)
• 0x00 : 43 validators, accounting for 0.93%(0.65% to 1.20%)

Two independent samples yielded a result of 97.0%. Extrapolating the share of active validators to the registry, there are approximately 912,000 active validators, with a statistical range of approximately 892,000 to 933,000.

Another data from the same measurement explains why looking at quantity alone is misleading. In terms of capital, the compound interest type is no longer a marginal phenomenon: the 95 0x02 type verifiers found held an average of approximately 820 ETH, while 4,495 0x01 Type verifiers hold an average of 32.008 ETH. In the sample, approximately one-third of the pledged Ethereum is in the hands of 0x02 . This capital share is much more uncertain than quantitative because it is based on only 95 observations and is extremely widely distributed; changes in a single large validator can significantly affect the results. But in terms of orders of magnitude, the conclusion is still true: a few large operators apply compound interest, but the majority of individual validators do not.

The number 32.008 ETH is not a coincidence, it is proof of the existence of a mechanism. The price of ether at the time of measurement was US$2,489.61 (Kraken, September 9, 2026 UTC 16:00).

There are two voucher types for the same pledge: only one can allow the reward to continue working

Clearing mechanism: Why your balance keeps falling back to 32 ETH

The process of the protocol automatically pushing excess balances from the verifier to the stored withdrawal address is called Clearing (Sweep). It runs without your participation, without cost, and without your confirmation. For verifiers with 0x01 credentials, all parts exceeding 32 ETH will be cleared during this process.

The speed of this process can be deduced from the two protocol values and the quantity obtained this time. Each block network handles a maximum of 16 withdrawals (MAX_WITDRAWALS_PER_PAYLOAD), with a block appearing every 12 seconds (SECONDS_PER_SLOT). With approximately 912,000 active validators, a complete iteration of the registry requires approximately7.9 days . About every eight days, your validator is cleared and reset to 32 ETH.

The average balance of 32.008 ETH measured among the 0x01 verifiers is the result of this mechanism: this is a small surplus accumulated since the last liquidation. In fact, all of these validators had balances slightly above the mark line, and few were significantly above it. The money is working, but the rewards it generates do not work with it.

How to check which credential type your validator carries in two minutes

Check that neither a private key nor a login is required. You only need the validator's index or public key, which is the identifier you see in the monitoring system.

Call the verifier record in the public beacon browser or directly through the beacon interface and view the withdrawal_credentials field. What matters is the first four characters of the value. If it reads as 0x02 , your reward will be compounded. If the readings are 0x01 , they will be cleared regularly. If the reading is 0x00 , no withdrawal target is stored and action is urgently needed at this time.

Anyone running a validator on their own node will find the same value in the validator status path output of the beacon interface. Anyone pledging through a provider will usually not be able to see it there and must inquire; more on this is explained below.

It's worth checking the balance again. If the validator has been running for months but the balance is always just above 32 ETH, then you are seeing a clearing mechanism in action rather than displaying an error.

0x00 : When withdrawal targets are not stored, no one can touch the balance

The most serious findings in the analysis involve the smallest group. Among the 4,633 active validators in the sample, 43 still carry credentials of type 0x00 , accounting for 0.93%. These validators continue to earn rewards but have no goal of receiving payments. As long as this state persists, it is impossible to retrieve the reward or the original deposit of 32 ETH.

extrapolates to the entire set, this share corresponds to approximately 8,500 validators, with a statistical interval of approximately 5,900 to 10,900. Their average balance in the sample was approximately 37 ETH, which was significantly higher than the 32 ETH in the 0x01 group, precisely because no funds were cleared and the rewards had been accumulated over the years. Multiply the two and the amount locked is approximately between 220,000 and 407,000 ETH. At September 9, 2026 prices, this is roughly equivalent to US$550 million to US$1 billion.

This range is deliberately kept wide and based on 43 observations, the text does not smooth it out to a neat single number. But one thing is certain: this is a considerable amount of capital that could have been retrieved since Shapella's upgrade, but it cannot be retrieved because no one performed the switch.

Affected people are usually verifiers in the early pledge era, and their keys were generated in 2020 or 2021. If you started pledging at that time and have not made any changes since then, this should be at the top of your list. Switching from 0x00 to the withdrawal target requires the original withdrawal key, which is derived from your mnemonic. Without this key, there is no way back.

Verifiers with 0x00 certificates continue to earn but not release any funds without a withdrawal target

It is possible to switch to 0x02 , There is a fee and is irrevocable to move

from 0x01 to 0x02 requires a request triggered by you at the execution level, such as through the official launch pad's validator interface or through the node setup tool. Technically, this is a merge request directed to your own verifier, introduced by the EIP-7251 standard.

It is important to understand three points in advance. First, the applicable network fee depends on the network load. Second, the switch is final: the ethereum.org documentation clearly states that the steps from 0x01 to 0x02 are irreversible. Third, switching fundamentally changes payment behavior because there is no longer automatic outflow after that. Anyone who relies on these regular inflows for continued income will lose exactly this.

Sequence when switching from 0x00 state

For verifiers in the 0x00 state, the order is different: first store the withdrawal target, that is, switch to 0x01 . Only after that was 0x02 considered.

Whether it's worth switching for you depends on factors that this article doesn't know about: your holding period, fees and tax status. Therefore, this article does not make recommendations. It just says you should understand the status before making a decision.

Pledge through exchanges or pools: The only question asked to providers

Most German investors pledge through exchanges, pools or pledged products rather than through their own validators. To them, the certificate type is not directly visible, but it works exactly the same way.

The question you can ask your provider is simple: Will my reward stay in the pledge for compound interest, or will it be paid out and idle? Providers that have migrated to 0x02 can answer this question. If the answer is vague, you have learned something.

A related point concerns payment aspects. If the amount of time to wait for capital in the event of an exit depends on the exit queue of the network, and therefore depends on factors other than the type of voucher. See our analysis of Ethereum pledge queues for details on how queues work and how they fluctuate. Regulatory requirements applicable to pledged products in Germany since MiCA, we have in another article on pledge under MiCA It has been explained in the article. Anyone who wants to view different providers and their terms side by side can find it in our Pledge Platform Overview .

Tax Perspective: Why is the receipt time under 0x02 an open issue

Switching credential types changes matters that have a tax impact: the time the reward reaches your address. Under 0x01 , they flow in regularly, approximately every eight days. Under 0x02 , they remain in the verifier balance, adding only the number there.

Whether this will change the time of receipt for tax purposes has not yet been finalized. The German Federal Ministry of Finance's notice of March 6, 2025 on individual issues related to the treatment of cryptocurrency income tax is relevant administrative guidance, but it does not explicitly address the issue of compound interest verifiers. Therefore, this article does not advocate any legal position where no legal position has been established. Please consult tax advice before switching and properly record the switching time.

Regardless of the above, the obligation to record still exists. Tools to automatically record this are listed in the Crypto Tax Tools and Combination Trackers Overview.

Limitations of this analysis: What the sample does not show

The survey is based on an index of 12,000 validators randomly selected from a registry of 2,362,534 entries, measured at a single time point on September 9, 2026. So the results are snapshots rather than comprehensive surveys.

This analysis clearly cannot provide three things. The dataset does not assign any operator to any credential because the beacon chain does not contain this information; so the share of large providers and individuals remains open. The measurement results did not mention the operator's place of residence, so it is unknown how many German pledgers were affected. The capital share of 0x02 is based on 95 observations and is extremely widely distributed, so it is only presented here as an order of magnitude rather than a robust ratio.

Everything can be recalculated. The protocol parameters come from the configuration endpoint of the public beacon node, and the verifier data comes from the status endpoint of the same node. For the definitions of the three credential types, see the Extraction credential document of ethereum.org The trigger point, the testnet version of the Lido module, can be read in the Crypto Briefing report on September 8, 2026.

Check your Ethereum Verifier credentials: Summary of key points

Check the prefix, it's today.

Call your validator record and read the first four characters of withdrawal_credentials. If it is 0x00 , you save the withdrawal target first, otherwise your capital will be locked. Those who have not yet pledged and are weighing entry should first obtain an overview of available pledge platforms and their terms.

consciously decides whether to switch to 0x02 .

It allows rewards to compound interest, which is final, and ends the regular inflow. Check beforehand whether you need these inflows and use Tax and Portfolio Tool to record the switching moment.

If you do not verify yourself, ask your provider.

One question is enough: Is my reward compound or paid? Changes in exit waiting times can be tracked in our Pledge Queue Analysis .

(As of September 9, 2026. This article does not constitute investment advice. Price and fee structures are subject to change; please check terms with your provider before purchasing.)