FANDOM


The Hanoi Project (ハノイプロジェクト Hanoi Purojekuto), also known as the Lost Incident (ロストけん Rosuto Jiken), is an event that occurred 10 years prior to the start of the Yu-Gi-Oh! VRAINS anime.[1] Kiyoshi Kogami, a researcher at SOL Technologies, developed and executed the incident without the knowledge of his company.[2] This project resulted in the creation of the Ignis.[3]

History

10 years before the present, six children were kidnapped by a certain organization and went missing one-by-one. During those six months of captivity, the children were imprisoned separately in rooms with nothing but a VR equipment. They were forced to Duel in a virtual arena where if they did not win, they were electrocuted and starved. After the children were rescued, the incident was covered up.

In the aftermath of the incident, several of the children suffered from post-traumatic stress disorder, with some taking years of therapy to recover, while others have not recovered at all. As the person to whom the mysterious voice belonged to was not amongst the rescued, Yusaku believes they may still be captured.

The project's name is the main reason why Yusaku and Shoichi Kusanagi suspect the Knights of Hanoi of a major involvement in the incident and thus why they pursue them. Revolver confirmed his knowledge of the incident during his Duel with Yusaku[4] while Kiyoshi, Kyoko Taki and Faust were all present during the incident, watching the victims' suffering.[3]

People Involved

Researchers

Victims

Gallery

References

  1. Yu-Gi-Oh! VRAINS episode 19: "The Incident Buried in the Darkness"
  2. Yu-Gi-Oh! VRAINS episode 20: "Unyielding Justice"
  3. 3.0 3.1 Yu-Gi-Oh! VRAINS episode 28: "Final Commander of the Three Knights"
  4. Yu-Gi-Oh! VRAINS episode 12: "Impregnable Defending Dragon Firewall"

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.