Pantheon

Pantheon is an Apache 2.0 licensed Ethereum client written in Java. Pantheon is public chain compatible, with a more modular architecture and roadmap to add privacy, permissioning, and new consensus algorithms.

We chose Java due to its appeal to enterprises, large open-source community, and mature ecosystem.

Why build with Pantheon?

Today

Multiple ConsenSus

  • Includes PoA for fast private networks
  • (Next release) Improvements to IBFT for fast, reliable finality

Modular Architecture

  • Mainnet compatible for future upgrades to Ethereum
  • Java-based to improve pluggability

Easy to Deploy

  • Dev-tools available to launch networks in minutes
  • Available via Microsoft Azure and Docker, and aiming for Kubernetes

Tomorrow

Privacy

  • Multiple approaches to privacy using EEA standard as guidelines (private transactions, on-chain)

Permissioning

  • Roles and permissions to control activities by members
  • Designed for private consortium networks

Ethereum 2.0

  • Our R&D team is working closely with the Ethereum Foundation
  • Currently testing improvements for massive scale

We regularly conduct code audits to address potential security concerns. We worked with Trail of Bits to audit Pantheon’s code base prior to devcon iv.

Roadmap

October 2018

Public Chain

Mainnet compatible
Early 2018

Private Chain

Private, permissioned
2019 and beyond

Next-Gen

Sharding, libp2p, WebAssembly

Our public client, Pantheon, has been open source for use by Ethereum application developers since October 2018.

We started with a public chain client to improve code maintainability, giving us direct access to innovation from public Ethereum, like sharding and plasma.

Public Pantheon will also have some enterprise features such as consensus algorithms.

Private, permissioned versions of Pantheon will be released some months after, using the requirements outlined in the Enterprise Ethereum Alliance spec as a basis for its design.

For instructions for deploying from public clouds, Docker, or other platforms, please review our documentation.