Cryptospecting

FACTS // VERIFIED 2026-10-19

Do 10-second blocks make PulseChain centralised?

Short answer

Not decided by those two numbers. The consensus protocol is Ethereum’s, with a shorter slot, rewards scaled to the larger stake number and part of the rewards burned. On 2026-10-19 the chain had 46,644 active validators — but how many independent operators run them cannot be read from the chain, so the claim is neither proven nor refuted.

The claim

“PulseChain's 10-second blocks and huge validator stake make it centralised.”

A recurring claim; no single original source is attributed here.

What the code shows

PulseChain runs the Ethereum beacon-chain protocol (forks of Lighthouse and Prysm) with different constants — 10-second slots (config.yaml:40-41), 32,000,000 PLS per validator (phase0.yaml:32), a base reward factor scaled to match (phase0.yaml:70) — and its own reward burn (pulse.rs:3-11). On 2026-10-19 there were 46,644 active validators. The code fixes the rules, not the number of independent operators, which the chain does not show. Read the consensus config.

What exactly is claimed?

The claim points at two parameters. First, blocks every 10 seconds instead of Ethereum’s 12. Second, a validator stake of 32,000,000 PLS, which sounds enormous next to Ethereum’s 32 ETH. From these it concludes that only a few large players can run the network.

What do the parameters actually say?

Parameter PulseChain Ethereum Code
Slot (block) time 10 s 12 s config.yaml:40-41
Validator stake 32,000,000 PLS 32 ETH phase0.yaml:32
Base reward factor 64,000 64 phase0.yaml:70
Reward burn rewards × 10/12, then × 3/4 (62.5 % of the formula) none pulse.rs:3-11
Consensus protocol Ethereum beacon chain (Lighthouse and Prysm forks) Ethereum beacon chain clients on GitLab

The protocol is the same; constants differ, and PulseChain’s clients add a burn of part of the validator rewards. In units, the stake is a million times Ethereum’s number. Rewards scale with the square root of the total stake, which therefore grows a thousand times, so the reward factor is multiplied by 1,000 — in our reading of the formula, this keeps the percentage reward in the same range as Ethereum’s.

How is decentralisation measured, then?

By counting, not by parameters: how many validators are active and how many independent operators run them. Validator data is public through the beacon API of any PulseChain consensus node (/eth/v1/beacon/states/head/validators) and through the official explorer.

Reading Value
Active validators 46,644
Combined effective stake 1,488,456,000,000 PLS
Beacon slot / time 10,862,693 / 2026-10-19 12:21:25 UTC

The figures were read from a public beacon node with the call above (statuses active_ongoing, active_exiting, active_slashed). They count validators, not operators: one operator can run many validators, and the chain does not say who runs which. The method is on Verify it yourself.

What is fair in the criticism?

The 32,000,000 PLS stake is a real entry threshold for running a validator alone; what it costs depends on the PLS price at the time. Whether the validator set is concentrated is a legitimate question — it just has to be answered with measurements. How validation works: Validators.

Verdict

Unproven as stated. Neither a 10-second slot nor the size of the stake number makes a chain centralised by itself; PulseChain uses Ethereum’s consensus protocol with adjusted constants and a reward burn. The validator count is measurable (46,644 on 2026-10-19); the number of independent operators behind them is not visible on-chain, so the claim can be neither confirmed nor refuted from chain data alone.

Sources // last verified 2026-10-19

  1. T1 · Primary lighthouse-pulse — PulseChain consensus client (GitLab)
  2. T1 · Primary prysm-pulse — PulseChain consensus client (GitLab)
  3. T1 · Primary go-pulse — PulseChain execution client (GitLab)
  4. T1 · Primary PulseChain beacon API (community node) — validator count read 2026-10-19
  5. T2 · Official pulsechain.com — validator stake of 32,000,000 PLS

Source tiers are explained in Sources & methodology.