- Joined
- May 8, 2002
- Posts
- 1,205,601
- Reaction score
- 59
You must be registered for see images attach
Why LaMelo Ball trade to Timberwolves still isn't official originally appeared on The Sporting News. Add The Sporting News as a Preferred Source by clicking here.
As of Thursday morning, LaMelo Ball is technically still a member of the Charlotte Hornets.
That's set to change soon, of course. He's part of an agreed-upon blockbuster trade to the Minnesota Timberwolves.
It's just not official yet.
That should change soon, and the signal will likely be that the Wolves start posting on their social media all sorts of LaMelo content.
But in the meantime, Minnesota fans wait for that final stamp of approval.
MORE: Bronny James' best future doesn't involve a trade from Lakers
Why isn't the LaMelo Ball trade official yet?
The deal couldn't go through until every piece involved was eligible to be moved.
The Timberwolves' involvement in a Julius Randle trade with the Nets and Bulls is set to tie in as part of a larger deal that also includes Naz Reid, the Hornets and Ball.
Because it's all likely to be one trade, there's a hold-up: Mo Gueye is going from the Bulls to the Timberwolves.
MORE: Cavaliers would form GOAT ending for LeBron James
Gueye signed a contract on April 9, so he isn't eligible to be traded until three months later, according to SKOR North's Darren Wolfson. Three months later is Thursday, July 9.
That makes Thursday the first day it can be completed. There's a chance it takes a little while yet as teams combine various pieces to make the most useful trade structure for everyone involved.
Don't expect anything meaningful to change from all the reports. It's just mostly a matter of patience and procedure now from these front offices.
More NBA news:
- Why the Hornets traded LaMelo Ball to the Timberwolves
- How Heat can unite Giannis with his brothers
- Knicks had a superstar opportunity but didn't go for it
- Giannis legacy with the Bucks remains intact
- Quentin Grimes proves where Jonathan Kuminga went wrong
Continue reading...