Cross-Chain-Kommunikation
Protokolle und Technologien, die es verschiedenen unabhängigen Blockchain-Netzwerken ermöglichen, Daten, Token oder Nachrichten auszutauschen.
Cross-Chain-Kommunikation löst das 'Blockchain-Insel'-Problem. Wichtige Protokolle: [Token-Bridges](/de/terms/token-bridges) (Wormhole), General Messaging (LayerZero, Axelar, CCIP), Native Interop (IBC, XCM), Atomic Swaps (HTLCs).
graph LR
Center["Cross-Chain-Kommunikation"]:::main
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧠 Wissenstest
🧒 Erkläre es wie einem 5-Jährigen
Stell dir vor, [Bitcoin](/de/terms/bitcoin) und [Ethereum](/de/terms/ethereum) sind zwei Inseln, die verschiedene Sprachen sprechen. Cross-Chain-Kommunikation ist wie ein Übersetzer-Schiff, das zwischen den Inseln verkehrt, Nachrichten und Pakete transportiert und sicherstellt, dass keine Insel beim Austausch betrogen wird.
🤓 Expert Deep Dive
❓ Häufig gestellte Fragen
Why are cross-chain bridges so often hacked?
Bridges are high-value targets because they hold large amounts of locked assets. The most common attack vectors are: compromised validator keys (Ronin Bridge), smart contract bugs (Wormhole), and economic exploits on governance logic (Beanstalk). Trusted bridges with small validator sets are especially vulnerable.
What is the difference between a bridge and IBC?
A traditional bridge relies on external validators (a trusted third party) to attest that an event happened on the source chain. IBC (Inter-Blockchain Communication) uses on-chain light clients to cryptographically verify the source chain's state directly, requiring no trusted intermediary.
What is an atomic swap?
An atomic swap is a trustless exchange of tokens between two different blockchains using Hash Time-Locked Contracts (HTLCs). It either completes in full (both parties get their tokens) or fails completely (both get their tokens back). No bridge or intermediary needed, but both chains must support the same hash function.