PortCityProphet
Follow me to the truth
Law firm's report says DraftKings employee locked in roster before receiving data
Yall seen this:
Menu
ABC News
00:00
Law firm's report says DraftKings employee locked in roster before receiving data
A DraftKings employee who accidentally published internal data on the same weekendhe won $350,000 on a rival site did not have access to the information before he set his winning lineup, according to an investigation performed by an outside law firm for DraftKings.
DraftKings released a statement, obtained by ESPN on Monday, saying the investigation determined that written content manager Ethan Haskell did not receive the internal data until after he had locked his lineup.
http://media.video-cdn.espn.com/motion/2015/1019/dm_151019_nfl_adikkes_mariota_analysis/dm_151019_nfl_adikkes_mariota_analysis_default.jpg
Mariota's mobility could be in question if he plays against Falcons
Pats win AFC Championship rematch with Colts
Meyer to meet with players before QB announcement
Coach K done coaching USA basketball after 2016
sc
The investigation was led by former U.S. Attorney John Pappalardo of law firm Greenberg Traurig and took close to two weeks to complete.
On Sunday, Sept. 27, after the early NFL games had kicked off but before the afternoon slate had begun, Haskell published data revealing what players were on the most rosters. The same weekend, Haskell finished second in a million-dollar NFL contest at FanDuel, winning $350,000.
According to the investigation, Haskell received an Excel file containing aggregate player ownership percentages for all weekend NFL games for use on the weekly story he composed. The data was not previously available to the public. The report shows a FanDuel account registered to Haskell submitted a lineup in the $25 buy-in, $5 million guaranteed NFL Sunday contest at 3:28 a.m. on Sept. 27.
"[Greenberg Traurig] has confirmed the Company's conclusion that Mr. Haskell could not possibly have entered the winning lineup based upon his receipt of the Company's non-public aggregate ownership percentage information, because he did not receive that information until 40 minutes after the lineup was locked," the investigation concluded.
Haskell, who remains employed at DraftKings, apologized for publishing the data on a forum post on the daily fantasy sports community site RotoGrinders.com, setting off a fury of controversy over DraftKings and FanDuel employees with access to internal data competing on other sites.
"We are very pleased that the independent investigation by Greenberg Traurig has confirmed the findings to our internal review of this matter and our conclusion that there was no improper use of information by our employee," DraftKings CEO Jason Robins said in a statement. "In fact, as the investigation also concluded, it was not even possible for non-public information to have been used improperly."
On Sunday, Sept. 27, after the early NFL games had kicked off but before the afternoon slate had begun, Haskell published data revealing what players were on the most rosters. The same weekend, Haskell finished seco
Yall seen this:
Menu
ABC News
00:00
Law firm's report says DraftKings employee locked in roster before receiving data
- By DAVID PURDUM via ESPN
- Star
A DraftKings employee who accidentally published internal data on the same weekendhe won $350,000 on a rival site did not have access to the information before he set his winning lineup, according to an investigation performed by an outside law firm for DraftKings.
DraftKings released a statement, obtained by ESPN on Monday, saying the investigation determined that written content manager Ethan Haskell did not receive the internal data until after he had locked his lineup.
http://media.video-cdn.espn.com/motion/2015/1019/dm_151019_nfl_adikkes_mariota_analysis/dm_151019_nfl_adikkes_mariota_analysis_default.jpg
Mariota's mobility could be in question if he plays against Falcons
Pats win AFC Championship rematch with Colts
Meyer to meet with players before QB announcement
Coach K done coaching USA basketball after 2016
sc
The investigation was led by former U.S. Attorney John Pappalardo of law firm Greenberg Traurig and took close to two weeks to complete.
On Sunday, Sept. 27, after the early NFL games had kicked off but before the afternoon slate had begun, Haskell published data revealing what players were on the most rosters. The same weekend, Haskell finished second in a million-dollar NFL contest at FanDuel, winning $350,000.
According to the investigation, Haskell received an Excel file containing aggregate player ownership percentages for all weekend NFL games for use on the weekly story he composed. The data was not previously available to the public. The report shows a FanDuel account registered to Haskell submitted a lineup in the $25 buy-in, $5 million guaranteed NFL Sunday contest at 3:28 a.m. on Sept. 27.
"[Greenberg Traurig] has confirmed the Company's conclusion that Mr. Haskell could not possibly have entered the winning lineup based upon his receipt of the Company's non-public aggregate ownership percentage information, because he did not receive that information until 40 minutes after the lineup was locked," the investigation concluded.
Haskell, who remains employed at DraftKings, apologized for publishing the data on a forum post on the daily fantasy sports community site RotoGrinders.com, setting off a fury of controversy over DraftKings and FanDuel employees with access to internal data competing on other sites.
"We are very pleased that the independent investigation by Greenberg Traurig has confirmed the findings to our internal review of this matter and our conclusion that there was no improper use of information by our employee," DraftKings CEO Jason Robins said in a statement. "In fact, as the investigation also concluded, it was not even possible for non-public information to have been used improperly."
On Sunday, Sept. 27, after the early NFL games had kicked off but before the afternoon slate had begun, Haskell published data revealing what players were on the most rosters. The same weekend, Haskell finished seco
