Re: Hyperledger Besu Proposal is Live


Grace Hartley
 

Hi All,

Thanks for the thoughtful questions. We've responded to them below.

Virgil’s Question: 

Why the name "Besu"?  That seems an odd choice, I'd imagine you'd want to pick an Ethereum-related word like "Rainbow", "Unicorn", or some such.


PegaSys' Response:

As Dan mentioned, we had a trademark challenge with Pantheon and we have to switch our name regardless of the Proposal. We chose Hyperledger Besu because “besu” means base in Japanese. We felt like base indicated how we developed the Ethereum client. We believe it is a solid foundation for blockchain developers to work on to run networks, build applications or send transactions, as an example.


Hyperledger’s naming principles target names that are not “common” words and that are easy to trademark. Unicorn, rainbow and all other words we explored that have more direct connections to Ethereum will have trademark challenges.


Mohan’s Question: 

Hyperledger technologies support a permissioned blockchain. They do not, at least to my understanding, have a crypto aspect. Is the intent to incubate Besu as a permissioned ethereum based blockchain and support interoperability with other platforms like Sawtooth, Iroha , Fabric? Also, how does this relate to Hyperledger Burrow?


PegaSys' Response:
The intent for Besu to be submitted in its current form. It can be run on the Ethereum public network or on private permissioned networks, as well as test networks such as Rinkeby, Ropsten, and Görli. We think public chain compatibility aligns with the enterprise market’s growing interest in using mainnet for a broader and more diverse set of use cases. Because this project is a protocol, it can be used for many different applications. Enabling cryotocurrency is only one of the applications. This project would be the first public chain compatible client within Hyperledger.

Silas provides a great response on his thoughts about how the project relates to Burrow and some ideas around collaboration here. Burrow is most well known for its EVM, which could connect in with Besu. They have a number of other components that we have started discussing with Silas. We are excited about closely working with the Hyperledger community to find areas for interoperability across the other projects. We have ideas mentioned in the Proposal around who we can collaborate with. 


Thanks,
Grace


On Sat, Aug 17, 2019 at 2:43 PM Mohan Venkataraman <mohan.venkataraman@...> wrote:
Hyperledger technologies support a permissioned blockchain. They do not, at least to my understanding, have a crypto aspect. Is the intent to incubate Besu as a permissioned ethereum based blockchain and support interoperability with other platforms like Sawtooth, Iroha , Fabric? Also, how does this relate to Hyperledger Burrow?


Regards

Mohan Venkataraman
Chainyard

On Sat, Aug 17, 2019, 9:41 AM Virgil Griffith via Lists.Hyperledger.Org <virgil=ethereum.org@...> wrote:
Why the name "Besu"?  That seems an odd choice, I'd imagine you'd want to pick an Ethereum-related word like "Rainbow", "Unicorn", or some such.

-V

On Sat, Aug 17, 2019 at 9:21 PM Dan O'Prey via Lists.Hyperledger.Org <dan=digitalasset.com@...> wrote:
There were some trademark issues around "Pantheon", unfortunately

Dan O'Prey

CMO & Head of Community / +1 646 647 5957
Digital Asset, creators of DAML


On Fri, Aug 16, 2019 at 8:28 PM Morgan Bauer <mbauer@...> wrote:

Why rename it?

On 8/8/19 11:23:12, grace.hartley@... wrote:

Hi All, We are excited to share that PegaSys, the Protocol Engineering team at ConsenSys, submitted the Proposal for our Ethereum client, Hyperledger Besu (currently known as Pantheon), for your consideration as a new Hyperledger project. 


We welcome your feedback on the Proposal and look forward to engaging with you on it. Feel free to send our team feedback via email or comment directly in the Proposal document.

Thank you,

PegaSys and ConsenSys Team Joseph Lubin, ConsenSys, joseph.lubin@...Daniel Heyman, ConsenSys/ PegSys, daniel.heyman@...Rob Dawson, ConsenSys/ PegaSys, rob.dawson@...Grace Hartley, ConsenSys/PegaSys, grace.hartley@...Danno Ferrin, ConsenSys/PegaSys, danno.ferrin@...



This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.

Join {toc@lists.hyperledger.org to automatically receive all group messages.