Skip to content

docs: clarify module purpose, cleanup readme #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

emschwartz
Copy link
Contributor

No description provided.

@emschwartz emschwartz requested a review from sharafian August 2, 2017 12:38
> framework for attaching on-ledger settlement mechanisms.
> Implements a trustline ledger plugin that can be extended to settle automatically via a payment channel

The ILP Plugin Payment Channel Framework implements a [trustline](https://github.com/interledger/rfcs/blob/master/0022-hashed-timelock-agreements/0022-hashed-timelock-agreements.md#trustlines) that can be extended with an automatic settlement mechanism such as a payment channel.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should link payment channel to the HTLA doc as well


This module exports a `makePaymentChannelPlugin` function that
takes a [Payment Channel Module](#payment-channel-module-api), and returns a
LedgerPlugin class. Because trustlines and payment channels require maintaining state,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'require maintaining state' -> 'are required to maintain state'

This module exports a `makePaymentChannelPlugin` function that
takes a [Payment Channel Module](#payment-channel-module-api), and returns a
LedgerPlugin class. Because trustlines and payment channels require maintaining state,
users of these plugins must provide a more sophisticated [backend](#backend-api-with-extensions-for-payment-channels)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the regular store in the connector can still be provided; an advanced backend is only required if it has to be multi-process

users of these plugins must provide a more sophisticated [backend](#backend-api-with-extensions-for-payment-channels)
than is required by other types of plugins.

- [Installation](#installation)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This table of contents should go higher up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants