⏱ Epoch in Gonka

What an epoch is in Gonka and why its length is always different.

General information

On the network Gonka all key processes — rewards, PoC weight, vesting, governance — are tied to epochs. At the same time, many people naturally ask:

❓ Why is the duration of an epoch different each time if the number of blocks per epoch is the same?

Let's break it down step by step.

---

🧠 Briefly: the main point

In short:

• ✅ the number of blocks in an epoch is fixed

• ⏳ block time is variable

• 🔁 therefore the epoch duration is slightly different each time

• 📊 you can always view the actual history and forecast on the epochs site

---

🔁 What is an epoch in Gonka

An epoch is a fixed segment of blockchain history consisting of a strictly specified number of blocks.

Important:

• the number of blocks in an epoch is always the same

• but the timeduring which those blocks appear in the blockchain can vary

---

🧱 How many blocks are in one epoch

In the current Gonka implementation:

• 1 epoch = a fixed number of blocks

• this value is set at the protocol level (genesis / protocol parameters)

It is by the number of blocksand not by time:

• that the Reward Coins

• are credited PoC weight

• is recorded

• governance parameters are updated

an epoch closes and a new one begins

• 📄 Detailed logic of epochs and rewards is described in the official documents:

• $danger

Tokenomics

---

(it's convenient to link them in a separate “Documentation” block)

⏳ Why epochs last different amounts of time Although the number of blocks per epoch is fixed,.

the time between blocks is not

Main reasons:

1️⃣ Variable block production time

Gonka is not a blockchain with a strict timer like “1 block = X seconds.”

• Actual block time depends on:

• network load

• number of active nodes

• current consensus conditions

network latencies

• ➡️ As a result:

• sometimes blocks come faster

---

sometimes — slower

2️⃣ Sprint and consensus ≠ metronome Gonka uses aSprint mechanism

• tied to the blockchain, but:

• it doesn't force the network to produce blocks strictly by the second

it synchronizes to the network state, not to a clock

• This is intentional:

• in favor of resilience

• fair distribution of computing weight

---

real PoC, not formal timing

3️⃣ Decentralization ≠ fixed time In decentralized networkstime is a consequence

not a rule.

• Unlike centralized systems:

• no one “turns on a timer”

---

a block appears when the network is ready for it

📊 What the actual epoch duration looks like

• In practice: an epoch can last

• slightly faster or slightly slower than average

deviations are normal and expected 👉The history of all epochs

• , their:

• actual duration

• number of blocks

• current epoch

forecast for the next one

can be viewed here: 🔗 Gonka epochs history and forecast

https://gonkaai.space/#/epochs

• This is a very useful page:

• for miners

• for hosts

---

for understanding approximately when the current epoch will end

🔮 Why the forecast is only a forecast On the epochs page you can seean estimate of the duration of the next epoch

• but it's important to understand: this is

• a calculation based on the current block rate

if network conditions change — the actual time will change too

• Therefore:

• the exact epoch end time is not known in advance only this is certain:

---

the epoch will end when the last block of the epoch is mined

💡 Useful links 🔗 Gonka Documentation: https://gonka.ai/introduction/ 📄 Gonka Whitepaper: https://gonka.ai/whitepaper.pdf 💰 Gonka Tokenomics: https://gonka.ai/tokenomics.pdf Gonka epochs history and forecast

🔗 Gonka epochs history and forecast URL linkable page text (END)