In Arrow’s season 7, episode 5 titled “Demon” has confirmed the existence of Batman in the Arrowverse. While the availability of Batman characters for the CW has been limited, there have been a few vague hints at Batman’s existence on the same Earth as other Arrowverse heroes. However, this new episode has offered the most convincing evidence yet.

The last few episodes of Arrow have seen Oliver Queen looking for The Demon, a mysterious inmate held in Slabside Penitentiary. Oliver believes that Demon has some useful information that can lead him to the crime boss that’s threatening his family. The Demon reveals herself as Talia Al Ghul, his former ally and mentor.

When asked by Oliver what she was doing in the prison, she says that she “ran afoul of an old foe in Gotham.” While fans are aware of the comic book version of Talia, who took over the League of Assassins, the Arrowverse version of Talia is slightly different. Unlike the comics, Talia abandons the League of Assasins to act as a teacher to those who wanted to fight for the world, including Oliver Queen.

Obviously, this isn’t the first time the show has hinted at the existence of Batman in the Arrowverse. Earlier in season 6 “tribute” episode, Oliver Queen joked about the possibility of Bruce Wayne being a masked hero. The Flash has also referenced Bruce Wayne with the news of Wayne Tech-Queen Inc merger on the front page of a newspaper.

Supergirl herself has made a reference to Batman on two different occasions, talking about a vigilante who worked with her cousin and had “tons of gadgets” and “lots of demons.” This comes off as an interesting reference before the debut of Batwoman in the Arrowverse.

Earlier, CW President Mark Pedowitz stated that the network has no plans of introducing The Dark Knight on Arrow for now. While this news would certainly disappoint many, it’s still good to know that he exists somewhere out there.

Facebook comments:

Leave a Reply

Adcodes and Instructions provided for: ============================================== ============================================== ======================================== SID 15564 ======================================== PLACE THIS CODE BEFORE THE TAG Edge Ad Code: ======================================== ======================================== ***EDGE Trafficking Instructions:*** ======================================== EDGE ad code should be placed directly on the site within the body at the end of the page. The default EDGE configuration is described below. If you have requested a custom configuration, please disregard default settings below. EDGE can be trafficked through ad servers via javascript tags, 1x1 javascript pixel, or DFP/GPT synchronous tag. In DFP, make sure that SafeFrame is disabled (it is automatically enabled by default), otherwise the tags will not work properly. For DFP/GPT, see this link to "Traffic and serve out-of-page creatives": ======================================== ======================================== ***EDGE Default Configuration:*** ======================================== SLIDER - Rails w/ Content Detect and Footer w/ Ad Detect: - Serve rail placements (160x600, 300x250 and 300x600) for Desktop when open space is available. All sizes are located at the bottom of the window by default. - When rail space is not available, serve 728x90 or 970x90 footer. With Ad Detect enabled for desktop footers, a 728x90 or 970x90 will not be served when it covers a standard IAB format (728x90, 300x250, 160x600, and/or 300x600). ======================================== ======================================== ***EDGE Default Settings:*** ======================================== - Device Targeting: Desktop, Tablet, and Mobile Phone - 100/24 Frequency cap - Minimum Time between EDGE sliders: 3 seconds is the minimum time allowed; may be increased ========================================