" or "Hvorfor ventetiden på en epoch". Let's use "Hvorfor den ene-epoch ventetid".
Then: "The feature gate went live at slot 440,208,000, which is epoch 1019. But the actual change to block time didn't take effect until the next epoch, 1020, because SIMD-0525 requires a full epoch to let the network settle before a new timing target kicks in. That's the same mechanism Solana will use for the next stages."
Translation: "Feature-gaten gik live ved slot 440.208.000, som er epoch 1019. Men den faktiske ændring af bloktiden trådte først i kraft i den næste epoch, 1020, fordi SIMD-0525 kræver en hel epoch for at lade netværket stabilisere sig, før et nyt timingmål aktiveres. Det er den samme mekanisme, Solana vil bruge til de næste faser."
Note: "slot" is kept as is, "feature gate" might be "feature-gate" or "funktionsport" but we can keep "feature gate" as it's technical. We'll use "feature-gate" with hyphen.
Next: "Brennan Watt, CEO of Anza, said the 300ms stage is intended to become effective at epoch 1024, which should arrive around Aug. 28. That hasn't happened yet, as of Aug. 26. The network can pause between stages if skipped-block rates climb, meaning the 350ms run is also a live test for how much tighter the chain can go without breaking."
Translation: "Brennan Watt, CEO for Anza, sagde, at 300 ms-fasen er planlagt til at træde i kraft ved epoch 1024, som forventes at ankomme omkring den 28. august. Det er endnu ikke sket pr. 26. august. Netværket kan pause mellem faserne, hvis antallet af sprangne blokke stiger, hvilket betyder, at 350 ms-kørslen også er en live-test for, hvor meget strammere kæden kan gå uden at gå i stykker."
Note: "skipped-block rates" -> "antallet af sprangne blokke" or "springprocent" but we'll use "sprangne blokke" for clarity.
Next: "
What the numbers show
" -> "
Hvad tallene viser
"
Then: "Telemetry from Trillium measured a slot-weighted mean of 365.4ms in the post-change epoch 1021. For comparison, the pre-change epoch 1015 ran at 420.7ms. So the actual average is already below the old target, though still above the new one."
Translation: "Telemetri fra Trillium målte et slot-vægtet gennemsnit på 365,4 ms i den post-ændrede epoch 1021. Til sammenligning kørte den før-ændrede epoch 1015 med 420,7 ms. Så det faktiske gennemsnit er allerede under det gamle mål, men stadig over det nye."
Note: "slot-weighted mean" -> "slot-vægtet gennemsnit" (we can use "slot-vægtet" as a compound).
Next: "Skipped slots fell sharply. In epoch 1015, there were 1,890 skipped slots, or 0.438% of the total. In epoch 1021, that dropped to 331, which is 0.077%. Early indicators point to stability, not degradation, after the change."
Translation: "Antallet af sprangne slots faldt markant. I epoch 1015 var der 1.890 sprangne slots, eller 0,438% af det samlede antal. I epoch 1021 faldt det til 331, hvilket er 0,077%. Tidlige indikatorer peger på stabilitet, ikke forringelse, efter ændringen."
Note: Use Danish number formatting: 1.890 (with dot as thousands separator) and 0,438% (comma as decimal separator). Also "slots" is kept.
Next: "
Faster slots, shorter leader window
" -> "
Hurtigere slots, kortere ledervindue
"
Then: "Block time directly affects how long a leader holds the slot window. With four slots per leader, the window shrinks from 1.6 seconds to 1.4 seconds. That's a 12.5% reduction in how long each leader controls the network's output."
Translation: "Bloktiden påvirker direkte, hvor længe en leder holder slot-vinduet. Med fire slots per leder skrumper vinduet fra 1,6 sekunder til 1,4 sekunder. Det er en reduktion på 12,5% i, hvor længe hver leder kontrollerer netværkets output."
Note: Use comma for decimal: 1,6 and 1,4.
Next: "The proposal keeps four slots per leader and 432,000 slots per epoch. But the per-slot compute, account-write, vote, data, and shred limits all scale down proportionally to the shorter target. So the network doesn't just run faster — it also does less per slot to keep the overall throughput steady."
Translation: "Forslaget bevarer fire slots per leder og 432.000 slots per epoch. Men per-slot-beregningen, konto-skrivning, afstemning, data- og shred-grænser skaleres alle ned proportionalt med det kortere mål. Så netværket kører ikke bare hurtigere – det gør også mindre per slot for at holde den samlede gennemstrømning stabil."
Note: "compute" -> "beregning", "account-write" -> "konto-skrivning", "vote" -> "afstemning", "data" -> "data", "shred" is a technical term, keep as "shred". "throughput" -> "gennemstrømning".
Next: "The roadmap calls for 300ms, then 250ms, and finally 200ms. The 300ms stage is still pending, and it's the one that Watt says should arrive at epoch 1024. But the network won't move forward automatically — if skipped-block rates start climbing, the pause kicks in and the next stage waits."
Translation: "Køreplanen kræver 300 ms, derefter 250 ms og til sidst 200 ms. 300 ms-fasen er stadig afventende, og det er den, Watt siger bør ankomme ved epoch 1024. Men netværket vil ikke bevæge sig fremad
