Chris Paul responsible for Nuggets’ unwillingness to trade Carmelo to the Knicks?

The Nuggets’ stance towards the Knicks has been puzzling. They claim that New York doesn’t have the assets they want in exchange for Carmelo Anthony, but a quick look at the roster reveals a few good pieces: Danilo Gallinari, Landry Fields, Wilson Chandler, Anthony Randolph and Toney Douglas, just to name a few. Certainly the Knicks could work with a third team to bring another player into the mix if Denver offered up a list of players/assets that it wanted. But when GM Donnie Walsh has asked for this, the Nuggets have been non-responsive.

There was a little nugget (no pun intended) from Ric Bucher in ESPN’s Daily Dime which might explain why the Nuggets don’t want to trade Carmelo to the Knicks:

Stan Kroenke, the Nuggets’ former owner who ceded control to son Josh, is vehemently against dealing with the Knicks after being embarrassed at Anthony’s wedding in Manhattan by talk of his star becoming a Knick…

Bucher is presumably talking about Chris Paul’s wedding toast, where he allegedly said, “We’ll form our own Big 3,” referring to the possibility that Paul, Anthony and Amare Stoudemire could team up in New York.

Apparently, that didn’t sit well with the former Nugget owner and that perceived slight has affected these trade negotiations. Bucher goes on to say that the Knicks “can’t offer the Nuggets anywhere close to the same package of building blocks” as the Nets can. Still, it’s interesting that Kroenke still holds a grudge against the Knicks about comments made at a wedding by a player who isn’t even on the Knick roster.

Not yet, anyway.

Follow the Scores Report editors on Twitter @clevelandteams and @bullzeyedotcom.

Related Posts

One response to “Chris Paul responsible for Nuggets’ unwillingness to trade Carmelo to the Knicks?”

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>