{"id":2432,"date":"2018-08-07T00:00:00","date_gmt":"2018-08-07T00:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/ethereum-proof-of-authority-on-azure"},"modified":"2023-05-11T15:38:18","modified_gmt":"2023-05-11T22:38:18","slug":"ethereum-proof-of-authority-on-azure","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/ethereum-proof-of-authority-on-azure\/","title":{"rendered":"Ethereum Proof-of-Authority on Azure"},"content":{"rendered":"

We\u2019ve had great traction with our support of Ethereum on Azure. The existing Proof-of-Work solution has been deployed tens of thousands of times across a variety of industry verticals. Through the extensive development on our platform, we\u2019ve received great feedback from the community that has helped us shape our next Ethereum ledger product. I\u2019m excited to announce the release of Ethereum Proof-of-Authority on Azure<\/a>.<\/p>\n

Proof-of-Authority<\/h2>\n

Proof-of-Work is a Sybil-resistance mechanism that leverages computation costs to self-regulate the network and allow fair participation. This works great in anonymous, open networks where competition for cryptocurrency promotes security on the network. However, in private\/consortium networks the underlying ether has no value. An alternative protocol, Proof-of-Authority, is more suitable for permissioned networks where all consensus participants are known and reputable. Without the need for mining, Proof-of-Authority is more efficient while still retaining Byzantine fault tolerance.<\/p>\n

Enterprise-ready<\/h2>\n

We\u2019ve built this solution with the same principles that we drive in all our production services at Microsoft. In Proof-of-Authority, each consensus node on the network has its own Ethereum identity. In the case that a node goes down, it\u2019s important that the member doesn\u2019t lose consensus participation. Ideally, each member would run redundant consensus nodes to ensure a highly available network presence. To accomplish this, we\u2019ve built an abstraction which allows each consensus participant to delegate multiple nodes to run on their behalf. Each Azure Proof-of-Authority network comes with our identity leasing system that ensures that no two nodes carry the same identity. In the case of a VM or regional outage, new nodes can quickly spin up and resume the previous nodes\u2019 identities.<\/p>\n

Web Assembly Smart Contracts<\/h2>\n

Enterprise developers often cite Solidity language as one of the largest pain points when developing on Ethereum. To address this, we\u2019ve enabled Parity\u2019s web-assembly support, allowing developers to author smart contracts in familiar languages such as C, C++, and Rust.<\/p>\n

Azure Monitor<\/h2>\n

This solution also comes with Azure Monitor to track node and network statistics. For application developers, this provides visibility into the underlying blockchain to track block generation statistics. Network operators can use Azure Monitor to quickly detect and prevent network outages through infrastructure statistics and queryable logs.<\/p>\n

\"image\"<\/p>\n

Extensible governance<\/h2>\n

Many of our customers want to participate in a consortium, but don\u2019t want to manage the network infrastructure. We\u2019ve leveraged Parity\u2019s highly extensible Proof-of-Authority client to build a level of abstraction that allows our users to separate consortium governance from network operation. Each consortium member has the power to govern the network and can optionally delegate the consensus participation to the operator of their choosing. The Proof-of-Authority deployment comes with a Governance DApp to simplify voting and validator delegation. With this solution, each consortium member has custody over his or her own keys, allowing secure signing to be performed in the wallet of preference, for example, MetaMask in-browser wallet, Ledger hardware wallet, or Azure Key Vault with ECC signing.<\/p>\n

Governance DApp features<\/h2>\n