Game 1: Both Teams Slay Baron Nashor?

• 01
  Active signal

  Resolution-risk observation firing

  Expires in 7h. Spread is extremely wide.

• 02
  Spread cost

  Wide spread — 94.0¢

  Bid-ask spread is wide enough that intraday moves overstate any tradeable advantage. Most of the headline pp move would be eaten by spread on a market order.

Each factor is grounded in a single named metric you can verify on this page — probability, volume, liquidity, signal, resolution state. No predictions, no prose hallucinations.

This market is about whether both teams slay the Baron Nashor at least once during Game 1. Baron Nashor is a powerful neutral objective in League of Legends that first spawns at 20:00 game time and respawns 6 minutes after each death, granting the slaying team the Hand of Baron buff. This market will resolve to "Yes" if both Fukuoka SoftBank Hawks Gaming and CTBC Flying Oyster each slay Baron Nashor at least once during Game 1. This market will resolve to "No" if either team (or both teams) does not slay Baron Nashor during Game 1. If the match is canceled (not played at all) or is delayed beyond 7 days from the scheduled date, this market will resolve to 50-50. If Game 1 is never played due to forfeit, disqualification, or walkover, this market will resolve to 50-50. If Game 1 is not played because the series result has already been determined (e.g., a team clinches the series before Game 1 is needed), this market will resolve to 50-50. If Game 1 begins but is not completed and ends via surrender, this market will resolve based on whether both teams had slain Baron Nashor prior to stoppage. If the condition was not met, this market will resolve to "No". If Game 1 is remade, resolution will be based on the remade game only. The resolution source for this market will be official information from https://gol.gg/esports/home. However, if https://gol.gg/esports/home has not published final results within 2 hours after the event's conclusion, a consensus of credible reporting may be used instead including video evidence.

Categories come from a deterministic engine: manual overrides (highest priority) → sports hard markers → event-tag rules → keyword rules → Gamma category hint → default. The engine is versioned in category-overrides.ts; methodology lives at /methodology.