The Kushana Empire was founded by Mahārājādhirāja Kujula Kadphises, a Shaivite Hindu convert from his ancestral Steppe religion of the Yüeh-chih. He was not a Buddhist, as popularly believed.

A thread on the Hindu Emperors of the Kushana Dynasty.

The Kushanas were part of a tribal confederation called the Yüeh-Chih that originally lived in the western part of the Gansu Province of China. They were pushed west by the invasions of the Xiongnu (Huna) confederation. Kuja Kadphises united all the five sub-tribes under Kushana.
Emperor Kuja Kadphises had converted to Shaivism, a Mathura inscription from the Tōkrī Tīla mound (Maṭ village) clears up previous confusion (Based on him being called "satyadharmasthita" or 'steadfast in the true dharma' people speculated he was a Buddhist)

This is incorrect.
The Mathura inscription applied the same epithet to Emperor Huvishka (satyadharmasthita) but explicitly says the Kingdom was conferred upon its founder by Lord Shiva (Sarva is the epithet of Shiva). This makes it clear Kujula Kadphises had adopted Shaivism & the Kharoshti script.
This also makes sense, when we realize his son, Emperor Vima Kadphises was also a devoted Hindu Shaivite (and in his coins we clearly see a trishulin ithyphallic shiva with a tiger skin).

So his son had just been continuing his father's tradition & upbringing.
Emperor Vima Kadphises was also given the epithet māheśvara "worshipper of Shiva" on coinage. He also transformed the temple at Dilberjin to a sanctuary of Shiva & decorated the wall with Shiva, Parvati & Nandi. He bought craftsmen from Ujjain to Bactria to build a water conduit.
Kanishka I continuted the policy of worship of Shiva, the name Oēṣo with Shiva on coinage comes from none other than Sanskrit Vṛṣa > Prakrit Veṣa. Kanishka II patronized Buddhism but made sure to switch Buddhism from Prakrit to Sanskrit and from Kharoshti to just Brahmi.
Emperor Huvishka ensured the dynastic sanctuary of the Kushanavaṃsha at Mathura was rebuilt and ensured regular hospitality for the Brāhmin-s in the assembly hall of the sanctuary. The Iranian War God Orlagno (Verethragna) was replaced by Hindu Gods of War like Skanda, Kumara.
The Emperor Vasudeva I, last of the Great Kushans was a Hindu also as is clear from the name. Also the first to have a Hindu epithet as his name.
The strong Shaivite nature of almost every Kushan Emperor since the founding is no better stated than the fact the last Great Kushan King Vasudeva had only Lord Shiva on his coinage, no other diety.
I think it is unfortunate how the history of Hindu Empires is appropriated and made Buddhist or Jaina so often. I have nothing against those sects, Buddhism played a big role sharing the intellectual tradition of India to the world.. but the record must be set straight
The Kushana Empire was founded by a Shaivite convert, led by his son, also a Shaivite and for the most part patronized Shaivism. Of course, there were syncretic elements but for 99% people it has been reduced to "Buddhist Syncretic" empire.

Same thing with Maurya, Harsha etc..
https://t.co/j0Qs1yxQ09

Thread to view the Hindu Art of the Kushanas

More from Indian History

More from History

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.