etc. We need to translate the text inside, preserving the HTML structure. We'll translate the title: "Anza Inför Avgift på 0,5 SOL för Alpenglow Bug Bounty-Insändningar" or something. Let's be natural. "Anza tar ut 0,5 SOL i avgift för inskickade bidrag till Alpenglow bug bounty" but we need to keep it concise. Let's do: "Anza inför avgift på 0,5 SOL för Alpenglow bug bounty-inskickningar" Now content: We'll translate each paragraph. Keep proper nouns: Anza, Solana, Agave, Alpenglow, SIMD-0326, TowerBFT, BLS, Turbine, etc. Numbers and units like SOL, UTC, seconds, milliseconds, percentages, etc. Let's translate step by step. Original:
Anza, the development firm behind the Solana client Agave, is requiring security researchers to pay a non-refundable 0.5 SOL fee for each bug report they submit to the Alpenglow bounty program. The submission window closes at 16:00 UTC on Aug. 19.
Swedish:Anza, utvecklingsföretaget bakom Solana-klienten Agave, kräver att säkerhetsforskare betalar en icke-återbetalningsbar avgift på 0,5 SOL för varje felrapport de skickar till Alpenglow bounty-programmet. Inskickningsfönstret stänger klockan 16:00 UTC den 19 augusti.
Note: "bug report" -> "bugrapport" or "felrapport". I'll use "felrapport" to be natural. "bug bounty" -> "bug bounty" is common, but we can say "bugg-program" but better keep "bug bounty" as is. I'll say "Alpenglow bounty-programmet". Also "non-refundable" -> "icke-återbetalningsbar" but we can say "återbetalningsfri" or "icke-återbetalningsbar". I'll use "icke-återbetalningsbar". "each bug report" -> "varje felrapport". Second paragraph:The fee is collected before Anza assesses whether a finding is valid, severe, or a duplicate. Reports go through a designated portal that burns the fee, meaning the cost is sunk regardless of outcome. For researchers planning to submit multiple findings, the fees add up quickly.
Translation:Avgiften tas ut innan Anza bedömer om en upptäckt är giltig, allvarlig eller en dubblett. Rapporter går genom en särskild portal som bränner avgiften, vilket innebär att kostnaden är förlorad oavsett resultat. För forskare som planerar att skicka in flera upptäckter blir avgifterna snabbt höga.
"bränner" is okay, but maybe "förstör" or "bränner upp" - but "bränner" is fine in crypto context. "sunk cost" -> "sunk cost" but we can say "förlorad kostnad". I'll use "kostnaden är förlorad" or "kostnaden är oåterkallelig". I'll go with "kostnaden är förlorad". Third paragraph:What Alpenglow Is
->Vad Alpenglow är
or "Vad är Alpenglow?" but better to keep as heading: "Vad Alpenglow är" (What Alpenglow is) - maybe "Alpenglow: Vad det är" but I'll do "Vad Alpenglow är". Then:Alpenglow is a proposed replacement for Solana's Proof-of-History and TowerBFT consensus protocol, introduced under SIMD-0326. It's backwards-incompatible and aims to cut transaction finality from 12.8 seconds down to 100-150 milliseconds. The design uses BLS-based vote aggregation, requires 60% stake for notarization and 80% for fast finalization, and keeps Turbine for data dissemination. The proposal defines a 20+20 security model with 40% crash-failure resilience, while acknowledging implementation risk and migration challenges.
Translation:Alpenglow är en föreslagen ersättning för Solanas Proof-of-History och TowerBFT-konsensusprotokoll, introducerad under SIMD-0326. Det är inte bakåtkompatibelt och syftar till att minska transaktionsfinalitet från 12,8 sekunder till 100–150 millisekunder. Designen använder BLS-baserad röstaggregation, kräver 60% av insatsen för notarisering och 80% för snabb finalisering, och behåller Turbine för dataspridning. Förslaget definierar en 20+20-säkerhetsmodell med 40% tolerans för kraschfel, samtidigt som det erkänner implementeringsrisk och migreringsutmaningar.
Note: "Proof-of-History" keep as is. "TowerBFT" keep. "backwards-incompatible" -> "inte bakåtkompatibelt". "finality" -> "finalitet" or "slutgiltighet"? I'll use "finalitet" as it's common. "stake" -> "insats" or "stake"? In crypto, "stake" is often used, but "insats" is fine. I'll use "insats" but "stake" is also understood. I'll use "stake" for consistency? Actually, the Swedish crypto community often uses "stake" or "insats". I'll use "stake" as it's a term. But to be natural, I'll say "kräver 60% av stake" but better to translate: "kräver 60% av insatsen" - I'll use "insatsen". But "stake" is also common. I'll use "stake" to keep technical. Actually, let's be consistent: use "stake" as it's a proper term. But the instruction says "Use appropriate Swedish terminology for crypto/tech terms". So we can use "stake" as it's used in Swedish crypto contexts. I'll use "stake". So: "kräver 60% stake för notarisering och 80% för snabb finalisering". Also "notarization" -> "notarisering" (not common, but "notarization" is a term, maybe "notarius" - but I'll use "notarization" as is? Actually, in Swedish, we can say "notarisering" or "bevittning"? But since it's a specific term, maybe keep "notarization" as "notarisering" is not standard. I'll use "notarisering" but maybe better to say "intygande" but that's not exact. I'll use "notarization" as a loan word? Let's see: The term is "notarization" meaning the act of notarizing, but in crypto it's about "notarization" of votes. I'll use "notarisering" as it's understandable. Or "attestering" but that's different. I'll keep "notarisering" for simplicity. Also "fast finalization" -> "snabb finalisering". "Turbine" keep. "data dissemination" -> "dataspridning". "20+20 security model" -> "20+20 säkerhetsmodell". "crash-failure resilience" -> "kraschfelstolerans" or "motståndskraft mot kraschfel". I'll use "40% kraschfelstolerans". "implementation risk" -> "implementeringsrisk". "migration challenges" -> "migreringsutmaningar". Fifth paragraph:The Bounty Pool and Payouts
->Bounty-poolen och utbetalningar
The total pool can reach 50,000 SOL, but it only unlocks if a loss-of-funds finding is submitted. Individual awards range from 315 to
