According to the website Enterprise Ethereum Alliance (EEA), this alliance is a member-run standards organization whose charter is to develop open blockchain specifications that promote harmony and interoperability for businesses and consumers around the world.
Members of the EEA global community are made up of leaders, adopters, innovators, developers and businesses who collaborate to create an open, decentralized website for the benefit of everyone.
In essence, the EEA is a space for institutions to share knowledge and promote widespread adoption of the Ethereum protocol among institutional payers.
Some of its founding members are Accenture, EY, Ethereum Foundation, a banking conglomerate (including BBVA and Santander), and other key companies in various industries.
One of the first papers I came across while studying the EEA was how the alliance motivates its architectural stack. In my opinion, it is important to understand how different protocols, software, and dApps will communicate with other blockchains and with each other.
You can see the EEA’s proposed architecture stack below the alliance’s website.
Personally, I believe that the EEA stack’s ultimate goal is to promote widespread adoption of the Ethereum blockchain by making it more accessible and scalable.
At the base of the stack, we have the network protocols in use. At the time of writing, there was only one public protocol, the Ethereum protocol, available. On the network protocol, we have ledger and consensus mechanisms in the core blockchain layer.
Stack shows how many algorithms can be used (PoW, PoA, dBFT, etc.) with the goal of increasing the number of storage solutions both on-chain and off-chain to increase speed while maintaining levels high security. Execution is done through the Ethereum virtual machine (EVM) or through pre-agreed contracts.
On another level, we will see how businesses communicate with different protocols. It can add any amount of features like increased centralization, privacy, or any other licensing check. In essence, the EEA could introduce private blockchain solutions that are somehow similar to Ethereum’s functionality.
In the above two levels, we see both the tools and their respective applications. In short, tools are used by developers to facilitate communication between blockchain applications and layers, such as wallets or integrated libraries. In the application layer, applications like standard token (ERC), identity management, or Ethereum Name Service (ENS) exist in the form of programs (smart contracts).
Recommended use cases
There are several use cases suggested by the EEA to facilitate the adoption of blockchain technology.
The most notable cases that can be found on GitHub are:
• International payments
• National smart contract platform
• Cross-value adjustment
• Securities liquidity management
• Anonymous voting system
With the introduction of predetermined modules to apply the entire development stack, there is an added incentive for companies to pursue this technology. Enforcement not only becomes easier with many proven use cases, but organizations also have quality documentation issued by EEA members at their disposal.
In short, the Enterprise Ethereum Alliance is bridging the gap between public and private blockchain technology organizations and applications.