Arian Controversy

318Schisms, Heresies & Reformations

Overview

Beginning around 318, the Arian controversy emerged as a pivotal doctrinal dispute that profoundly shaped the trajectory of early Christianity. The conflict originated from the teachings of Arius, a priest in Alexandria, whose theological assertions regarding the nature of the Son in relation to God the Father sparked intense debate across the church. At the heart of the disagreement was the question of whether the Son was co-eternal and consubstantial with the Father, or if he was a created being subordinate to the divine source.

As the theological divide deepened, the controversy threatened the unity of the church and drew the attention of the Roman Empire. The escalating tension necessitated a formal resolution, leading to the convening of the Council of Nicaea in 325. This landmark assembly brought together bishops from across the Christian world to deliberate on the nature of the divinity and establish a unified theological position.

The council ultimately rejected the teachings of Arius, formalising the doctrine that the Son is of the same substance as the Father. This decision was codified in the Nicene Creed, which served to define the boundaries of orthodox belief. The legacy of these proceedings proved foundational for the development of later Christian theology, establishing a standard for orthodoxy that would influence ecclesiastical thought for centuries to come.

  • The controversy centred on the divine nature of the Son.
  • Arius proposed that the Son was a created being.
  • The Council of Nicaea was convened to address the schism.
  • The resulting Nicene Creed established the doctrine of consubstantiality.
  • The conflict became a defining moment for early Christian orthodoxy.

Related links

An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.