Multiparty Entanglement
Bell pairs entangle two parties, but many network applications — conference key agreement, distributed sensing, anonymous broadcasting, leader election — need three or more nodes sharing correlations at once. The workhorse multiparty resource is the GHZ state, named after Greenberger, Horne and Zeilinger.
The GHZ state
For parties, each holding one qubit, the GHZ state is
For that is . It is the natural generalisation of the Bell pair : all parties are either or all are , with nothing in between.
Building it on a chain
A GHZ state is prepared with one Hadamard followed by a cascade of CNOTs:
The Hadamard seeds the superposition on the first qubit; each CNOT then forces the next qubit to agree with the running value, propagating the all-/all- branch structure across the whole register. Across a network, this can be done by a source that fans out CNOTs, or assembled from Bell pairs and fusion operations at a central node and then distributed.
A telling fragility
GHZ entanglement is powerful but brittle. Measure (or lose) a single qubit of in the computational basis and the entanglement of the remaining qubits collapses entirely — they are left in a plain product state. Contrast this with a different multiparty class, the W state , whose pairwise entanglement survives the loss of a party. GHZ and W are inequivalent: no sequence of local operations and classical communication can turn one into the other. The right multiparty resource depends on whether your application needs all-or-nothing correlation (GHZ) or robustness to dropout (W).
Correlations across bases
Like the Bell pair, the GHZ state hides its entanglement from any single party: each qubit on its own is maximally mixed. In the basis the parties see perfect agreement ( or , each with probability ). In the basis the parity of the outcomes is fixed — the source of the celebrated GHZ contradiction with local hidden variables, which needs no inequalities and no statistics: a single run can refute local realism. That same parity structure is what multiparty protocols measure to detect eavesdroppers or to extract shared randomness.
Try it
Build a 3-party GHZ state across Alice, Bob and Charlie, then measure. The grader checks the
distribution: only 000 and 111 should appear, each with probability .
In the Probabilities tab you should see exactly two bars of height — the multiparty all-or-nothing signature.
Sign in on the full site to ask questions and join the discussion.