tags. We'll translate the headings as well. The original has
How the burn mechanism works
and
Why cap staking at 50%
and
Divided reactions from builders
. We'll translate those.
- "How the burn mechanism works" -> "So funktioniert der Verbrennungsmechanismus"
- "Why cap staking at 50%" -> "Warum das Staking auf 50 % begrenzen?"
- "Divided reactions from builders" -> "Geteilte Reaktionen von Buildern" (or "Entwicklern" but "builders" is often kept as "Builder" in German crypto context, but we can translate as "Entwickler" but that might be ambiguous. Actually "builders" in crypto often refers to developers, but we can say "Geteilte Reaktionen aus der Entwickler-Community" or simply "Geteilte Reaktionen von Buildern". I'll use "Geteilte Reaktionen von Buildern" to keep the nuance.
We'll also keep the quotes and names as is.
Now we need to ensure the JSON is valid. We'll escape any double quotes inside the content. The content has quotes like 'Tapered Issuance Burn' and 'artificial yield floor' - we'll use German quotes? Actually we can keep them as is, but we need to escape double quotes if we use them. We'll use single quotes for quotes inside the text we can
