Skip to content
Browse articles

A new Light on Chunda

By Sailaja Kinkar Rai

Vol. 11 · No. 3September - 1935pp. 559–563English

Summary

Chunda, founder of the Chupdawit section of the Sjsodiya Rajputs, is traditionally celebrated for selflessly relinquishing his claim to Mewar's throne in favor of his younger step-brother Mokal, as recounted in Colonel Tod's *Annals and Antiquities of Rajasthan*. However, this analysis critiques the reliability of such narratives, noting discrepancies between sources. The *Annals of Mewar*, written centuries after Chunda's time, portrays him as an exaggerated hero, while the 17th-century *Khyat®* of Muhanote Nensi offers earlier but equally contentious insights. The political context of early 15th-century Western India—with Gujarat and Malwa asserting independence from Delhi post-Timur's invasions—shaped regional alliances. Mewar, under Rana Lakha (r. 1406–1419), sought to strengthen ties with Marwar's Rathor chief Rav Chunda (r. 1391–1421) through a matrimonial alliance. When Chunda's daughter Hemsavai was proposed to Mewar's heir, Chunda (same name), the traditional account claims Chunda selflessly ceded his throne claims to avoid future succession disputes. However, inconsistencies emerge: Rani Lakha had nine sons from his first wife, with Mokal being the youngest, suggesting earlier heirs held prior claims. Additionally, Lakha's alleged "warlike pilgrimage" to Gaya is contradicted by evidence showing he resolved conflicts diplomatically, paying taxes to local rulers rather than engaging in battle. The analysis questions whether Chunda's renunciation was voluntary, citing his

AI-generated summary, automatically checked against the article text.

Conclusion

This study re-examines Chunda's historical significance through dual narratives, revealing complexities in traditional accounts. While Colonel Tod's version portrays Chunda as a self-sacrificing figure who relinquished Mewar's throne for familial harmony, the earlier Khyat of the seventeenth century offers contrasting insights, necessitating critical analysis of both sources. The political context of post-Timurid India underscores Chunda's strategic alliance with Mewar through matrimony, reflecting broader regional dynamics. The research highlights how historical memory, shaped by Rajput cultural norms like the symbolic 'coconut proposal', influenced Chunda's legacy. By juxtaposing these accounts, the study demonstrates how historical narratives balance idealized heroism with pragmatic political maneuvers, offering a nuanced perspective on Chunda's role in early sixteenth-century Rajputana.

Key passages

Chosen by AI from the article's text. Each one is checked word for word against the text before it is shown.

  • “In our view of the case, the throne પાડ never lovked upon in Mewar, not in any Rajput state, as a personal property that could he given away at will by the occupier or 1010.”
  • “We thus find that Chundd does not deserve the great honour which has been bestowed 000 him by tradition. His so-called self-abnegation is nothing but a2 renunciation forced upon him by his voluptuous father, with the so-called consent of his Sardars,”
  • “It would thus appear that if any credit for renun- ciation is 10 be given to Chundd, such credit must be shared by his younpger uterine brothers as well”

Works cited in this article

  1. Rajputjibansandhyd by R. C. Dutta
  2. Crooke’s edition of Tod's Rejusthan
  3. Bhavoagar Luseriptions

Discussed in this article

People

  • Chunda
  • Mokal
  • Rav Chundd
  • Hemsavai
  • Righavadeva
  • Colonel Tod
  • Rana Lakha
  • Rana Hammir
  • Rana Khetra Simha

Dynasties, sects & groups

  • Chupdawit section of the Sjsodiya Rajputs

AI guide

Discuss this record

Ask about the article, its topics, issue context, selected passages, or reading strategy.

Start with the record

I can unpack the summary, turn it into study questions, explain a selected passage, or compare it with the other articles in this issue.

Original PDF

Inline viewer

Checking source PDF

The viewer will load here if the archive file is reachable.