1. Messages
  2. [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers

Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers

Adrian Hope-Bailie <adrian@...>
 

> there may well be other interoperability style projects in the future e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important

That does raise the question whether those could fall under this project or would have to stand-alone.

Interledger is intended to be a layer of abstraction above Lightning, as an example. We have actually done some work using the JS implementation to make ILP payments over Lightning (i.e. Lighning is another network that is made interoperable with any others over which an ILP implementation is available). So an outcome of this project could be interop between Lightning and Aroha for example.

For that reason I'm leaning toward a very generic name that does allow the project to evolve and include numerous "integrations" and still make sense.

Personally I like Hyperledger Quilt, also because it's unique and would be difficult to confuse with anything else.

@Isaac: Any other ideas?


On 8 September 2017 at 11:32, Dan O'Prey <dan@...> wrote:
Some input from the marketing side for your consideration:

  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.

On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey
Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

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.