Re: PoC

There are two ways you could go to make this work.

1) Write a ledger plugin
<https://github.com/interledger/rfcs/blob/master/0004-ledger-plugin-interface/0004-ledger-plugin-interface.md>
that
issues the relevant commands for your legacy ledger.
2) Gregor Gololicic, Robert Boothby and others have suggested developing a
ledger adaptor that implements the crypto conditions, holds, and
notifications needed by clients and connectors. This could implement a
standard ledger API that would (greatly) reduce the number of plugins
clients need to support.

I really like #2, but since this is a relatively new idea it'll take a
little bit of time to get it set up.

On Tue, Jul 12, 2016 at 11:49 AM, Romero, Javier (ISBANUK) <
Javier.RomeroColomo@isbanuk.com> wrote:

> Hi guys,
>
> I am trying to do an internal PoC with ILP with one of our existing
> processes and had a quick question:
>
> In the case of "legacy" ledgers, do I need to build an ilp ledger on top
> or could a connector be sufficient?
>
> This was my understanding: http://i.imgur.com/eQG7xUG.png
>
> But I am not sure now?
>
> BTW, is this the correct forum to ask this type of questions? Apologies if
> it's not!
>
> Thanks
>
> **********************DISCLAIMER*****************
> This message is private and confidential and it is intended exclusively
> for the addressee. If you receive this message by mistake, you should not
> disseminate, distribute or copy this e-mail. Please inform the sender and
> delete the message and attachments from your system. No confidentiality nor
> any privilege regarding the information is waived or lost by any
> mistransmission or malfunction.
> Any views or opinions contained in this message are solely those of the
> author, and do not necessarily represent those of ISBAN, unless otherwise
> specifically stated and the sender is authorized to do so.
> E-mail transmission cannot be guaranteed to be secure, confidential, or
> error-free, as information could be intercepted, corrupted, lost,
> destroyed, arrive late or incomplete, or contain viruses. ISBAN does not
> accept responsibility for any changes, errors or omissions in the contents
> of this message after it has been sent.
> This message is provided for informational purposes and should not be
> construed as a solicitation or offer to buy or sell any securities or
> related financial instruments.
>
> *********************AVISO LEGAL **********************
> Este mensaje es privado y confidencial y solamente para la persona a la
> que va dirigido. Si usted ha recibido este mensaje por error, no debe
> revelar, copiar, distribuir o usarlo en ningun sentido. Le rogamos lo
> comunique al remitente y borre dicho mensaje y cualquier documento adjunto
> que pudiera contener. No hay renuncia a la confidencialidad ni a ningun
> privilegio por causa de transmision erronea o mal funcionamiento.
> Cualquier opinion expresada en este mensaje pertenece unicamente al autor
> remitente, y no representa necesariamente la opinion de ISBAN, a no ser que
> expresamente se diga y el remitente este autorizado para hacerlo.
> Los correos electronicos no son seguros, no garantizan la confidencialidad
> ni la
> correcta recepcion de los mismos, dado que pueden ser interceptados,
> manipulados, destruidos, llegar con demora o incompletos, o con virus.
> ISBAN no se hace responsable de los cambios, alteraciones, errores u
> omisiones que pudieran hacerse al mensaje una vez enviado.
> Este mensaje solo tiene una finalidad de informacion, y no debe
> interpretarse como una oferta de venta o de compra de valores ni de
> instrumentos financieros relacionados.
> Ref:[PDB#015]
>



-- 
Evan Schwartz | Software Architect | Ripple
[image: ripple.com] <http://ripple.com>