Until today, organizations had to create proprietary versions of a permissioned corporate Ethereum implementation. Thanks to the EEA new client spec, the global development community can now design their Ethereum solutions via a coordinated, interoperable foundation.
Announced today, the Enterprise Ethereum Alliance has released the Enterprise Ethereum Client Specification 1.0.
Incorporating components developed by the Ethereum Foundation, the alliance declares the new spec has been designed to provide global corporate Ethereum developers with a “single, open-source, cross-platform standards-based framework to speed up business transactions, build a greater trust in contracts, and create more efficient business models.”
Based on the recently developed Enterprise Ethereum Architecture Stack, the new EEA client specification will effectively replace the costly multi-protocol approaches that previously defined the corporate Ethereum landscape.
Resulting from 18 months of “intense collaboration” between leading enterprises and the EEA’s technical committee, Client Specification 1.0 could help spur mass adoption “at a depth and breadth otherwise unachievable in individual corporate silos,” said EEA Executive Director Ron Resnick.
“Microsoft joins the other members of the EEA in celebrating the release of the Enterprise Ethereum Client Specification 1.0 open standard for high-performance, cross-platform enterprise blockchain. With this significant step, the EEA has defined a modern layered architecture designed to deliver a high-performance, cross-platform solution and ecosystem for the global enterprise community comprised of the world’s largest companies and the most innovative startups,” said Marley Gray, a founding EEA member from Microsoft and principal architect of the company’s Azure blockchain.
By utilizing “hybrid architectures,” Spec 1.0 may assist with general Ethereum development issues, such as scalability, privacy, and security for both permissioned and public Ethereum networks.
The EEA is planning to introduce a testnet for further exploration and trials of interoperability across its members’ projects. Additionally, a forthcoming EEA certification program will eventually ensure that solutions conform with developed standards. Using members in the telecom industry as an example, Resnick told ETHNews:
“What we’re going to do is build out a global testnet. That testnet will be able to have all the telecom vendors anywhere in the world access this testnet. They can then take their vendors who they might buy phones from or accessories that could have blockchain implementations in them, and they’ll be able to work with those vendors because they are members of the EEA … They’ll all be able to use our testnet to do proof of concepts, or even a little next-level trialing of how things will work. It’s going to be available for all our members.”
When asked how he felt the EEA’s work could motivate companies to help find solutions for the mainnet, Resnick intimated, “I’ve already talked to multiple members, and they all even the financial and entertainment sides they recognize that the benefit of having the Ethereum public net is like a game changer. If we can come up with ways where we have better models to get past firewalls and still have privacy and security, by connecting their private networks so they can reach folks everywhere for the kinds of business opportunities they foresee using the public mainnet is exciting to them.”
“The EEA specification represents a new and seamless way for enterprises to leverage Ethereum to develop innovative, blockchain based solutions,” said Lior Glass, an EEA member from BNY Mellon. “As a Founding EEA Member, we are excited to help create a new industry standard that supports the continued adoption of blockchain in the financial services industry.”
With over 500 organizations as members, including some of the most prominent financial and technology companies on the planet, the EEA’s second standardization release in as many months is evidence of the EEA’s renewed vigor in 2018.
“Job one was to publish the architecture stack,” says Resnick. “Job two was to publish the specification itself, which was based upon the stack. Third, is work on a plan for the testnet and get that up and running. I can’t say how soon that will be, but lots of companies are excited to work on it.”
source : www.ethnews.com