Latest On Cavs, Tristan Thompson

JULY 8TH, 9:10am: The sides made a bit of progress Tuesday, sources told Sam Amico of Fox Sports Ohio, who includes the tidbit at the end of a broader story on Amico Hoops.

JULY 6TH, 1:02pm: Talks between the sides continue, but the dialogue isn’t producing much of substance at this point, Haynes hears. Other teams are keeping a keen watch on the Thompson dialogue, given that LeBron James reportedly won’t talk to the Cavs about re-signing until Thompson’s deal is done, as Haynes details.

1:10pm: The gap isn’t vast, and there’s no animosity between the sides, as Chris Haynes of the Northeast Ohio Media Group hears (Twitter link).

JULY 2ND, 12:05pm: A gap remains between the sides in spite of the progress they made Wednesday, Windhorst tweets.

JULY 1ST, 2:09pm: The Cavaliers and Tristan Thompson are close to an agreement on a deal that would pay him north of $80MM, report Marc Stein and Brian Windhorst of (Twitter link). It appears that would be about the maximum that he could receive in a five-year arrangement. LeBron James made it clear this spring that he wanted his fellow Rich Paul client back with the Cavs, months after Thompson and Cleveland didn’t come to terms on an extension this past fall.

A deal for Thompson would be yet another significant commitment for Cleveland, which will retain Kevin Love, reportedly for the max, and almost certainly will do the same with LeBron. The team has already had internal discussions about a payroll of $100-110MM next season with a tax payment of some $75MM, as Windhorst previously reported.

Thompson turned down a four-year, $52MM extension offer this past fall, betting that he could do better this summer, even though the Cavs had brought in Kevin Love at his position. Thompson came off the bench most of the time, but he excelled as a starter in the playoffs when Love was injured. Still, a max deal is quite a high price to pay for the 24-year-old who averaged only 8.5 points per game this past season, particularly with Love coming back, too.

View Comments (7)