Revered NFT artist XCOPY has seen one of his pieces, titled Bad Flavour, sell for 280 ETH – approximately $665,000 USD.
This comes amidst a general decline in NFT trading and NFT prices, with August 2024 being the worst month for NFT trading of the year so far.
This has sparked discussions in the community about a possible revival in NFT prices, although it should be noted that XCOPY’s pieces specifically are achieving high prices at the moment, with his Damage Control series seeing particular popularity.
Source: SuperRare
Who is XCOPY?
XCOPY is the pseudonym for an anonymous London-based digital artist, notable in blockchain circles for his highly-prominent NFTs. His work has a distinctly dystopian flavour, commonly featuring animation and a limited array of colours.
Emerging in 2010, XCOPY created regular pieces of art of Tumblr, doing so on a monthly basis for over 10 years. XCOPY began exploring NFTs as a medium for his work, and has gone on to secure record prices for his work.
Right-Click and Save As Guy sold in December 2021 for $7 million USD, A Coin for the Ferryman garnered $6 million USD, and Max Pain – an open edition – achieved a total sale price of almost $23 million USD in 2022.
Source: X
Who purchased Bad Flavour?
XCOPY’s Bad Flavour was purchased for 280 ETH on September 10 by @punk4945.
This anonymous individual is a notable collector of XCOPY’s works, revealing his collection of 25 of XCOPY’s pieces in August 2024 – alongside a Bored Ape and his eponymous CryptoPunk.
It remains to be seen whether this is any indicator of a revival in the NFT art market, though the strength of such a sale of a prominent piece by one of the most notable artists in the industry should not be understated.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
