This repository was archived by the owner on Sep 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 33
Update ILP Glossary #123
Open
pgarg-ripple
wants to merge
21
commits into
interledger:master
Choose a base branch
from
pgarg-ripple:pg-glossary
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update ILP Glossary #123
Changes from 1 commit
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
4aa3b86
Add glossary
pgarg-ripple 6709018
add links
pgarg-ripple d661e8e
add links
pgarg-ripple 2c8bbfc
Update docs/markdown/glossary.md
pgarg-ripple fdd60a8
Update docs/markdown/glossary.md
pgarg-ripple 672f5fc
Update docs/markdown/glossary.md
pgarg-ripple 9a8c7b2
Update docs/markdown/glossary.md
pgarg-ripple 4603311
Update docs/markdown/glossary.md
pgarg-ripple 6ce2358
Update docs/markdown/glossary.md
pgarg-ripple ac7492e
Update docs/markdown/glossary.md
pgarg-ripple 1d4a0e3
remove outdated terms
pgarg-ripple 82c6a7f
update glossary
pgarg-ripple 234a7cd
update glossary
pgarg-ripple f71cb4e
update glossary
pgarg-ripple f806ecd
add link
pgarg-ripple 1e2d622
Update docs/markdown/glossary.md
pgarg-ripple f730643
update definitions and add more links
pgarg-ripple c1e203e
update more definitions
pgarg-ripple 5a89962
fix space between headers
pgarg-ripple d892b21
Merge branch 'master' of https://github.com/pgarg-ripple/interledger.…
pgarg-ripple d406825
update bandwidth definition
pgarg-ripple File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,8 +4,7 @@ This glossary provides definitions for key terms in the Interledger ecosystem. | |
|
|
||
| ## Account | ||
|
|
||
| An accounting relationship between two Interledger participants. | ||
| In Interledger, two participants establish an account with one another to track the current obligations they hold with one another. | ||
| An accounting relationship between two Interledger participants. In Interledger, two participants establish an account with one another to track the current obligations they hold with one another. | ||
|
|
||
| ## Address | ||
|
|
||
|
|
@@ -45,27 +44,27 @@ See instead: [Router](#router) | |
|
|
||
| ## Cyclic Transaction | ||
|
|
||
| A transaction where the destination account is the same account, on the same ledger, as the source account. This can be useful when rebalancing liquidity (to enable future payments), or when rebalancing stored value (to spread risk, or to take advantage of changing exchange rates). | ||
| A transaction where the destination account is the same account on the ledger as the source account. This can be useful when rebalancing liquidity (to enable future payments), or when rebalancing stored value (to spread risk, or to take advantage of changing exchange rates). | ||
|
pgarg-ripple marked this conversation as resolved.
Outdated
|
||
|
|
||
| ## Destination Account | ||
|
|
||
| The account of the receiver whose address is included in the Interledger packet. Note that anyone can claim to have a certain Interledger address; address ownership is not enforced. | ||
|
pgarg-ripple marked this conversation as resolved.
Outdated
|
||
|
|
||
| ## Destination Amount | ||
|
|
||
| The amount to be received by the receiver. | ||
| The amount to be received by the receiver through ILP. | ||
|
pgarg-ripple marked this conversation as resolved.
Outdated
|
||
|
|
||
| ## Distributed Ledger | ||
|
|
||
| A ledger that is operated by a group of entities and runs on multiple servers. This term is used somewhat interchangeably with "Blockchain" or "Decentralized Ledger". | ||
|
|
||
| ## Exchange Rate | ||
|
|
||
| The price of one ledger's asset in terms of another ledger's asset. Routers may generate revenue from the difference in value between incoming and outgoing transfers. The exchange rate between source and destination is determined by the product of exchange rates at each hop. | ||
| The price of one ledger's asset in terms of another ledger's asset. Routers may generate revenue from the difference in value between incoming and outgoing transfers. The exchange rate between a sender and a receiver is determined by the product of exchange rates at each hop. | ||
|
|
||
| ## Fulfillment | ||
|
pgarg-ripple marked this conversation as resolved.
Outdated
|
||
|
|
||
| A 32-byte value used to trigger the execution of a transfer. In most Interledger payments, the fulfillment is known only to the receiver (or in the case of the STREAM protocol it is known to the sender and the receiver). | ||
| Also known as the "preimage" or "hash preimage", fulfillment is a 32-byte value used to trigger the execution of a transfer. In most Interledger payments, the fulfillment is known only to the receiver (or in the case of the STREAM protocol it is known to the sender and the receiver). | ||
|
pgarg-ripple marked this conversation as resolved.
Outdated
|
||
|
|
||
| ## Hop | ||
|
|
||
|
|
@@ -96,6 +95,8 @@ The public network of ledgers connected via the Interledger protocol stack. | |
| An Interledger address provides a way to route ILP packets to their intended destination through a series of hops, including any number of ILP routers. | ||
|
|
||
| An Interledger address is a dot-separated string that contains prefixes to group ledgers. An example address might look like `g.us.acmebank.acmecorp.sales.199` or `g.crypto.bitcoin.1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2`. | ||
|
pgarg-ripple marked this conversation as resolved.
Outdated
|
||
|
|
||
|
|
||
| Note that anyone can claim to have a certain Interledger address, there is no registry of them. Whether or not a payment ends up at the intended receiver is ultimately safeguarded by the hashlock condition, not by enforcement of address ownership. | ||
|
pgarg-ripple marked this conversation as resolved.
|
||
|
|
||
| See also: [IL-RFC 15](https://github.com/interledger/rfcs/blob/master/0015-ilp-addresses/0015-ilp-addresses.md) | ||
|
|
@@ -140,14 +141,18 @@ See instead: [Interledger Protocol](#interledger-protocol-ilp) | |
|
|
||
| ## Ledger | ||
|
|
||
| Stateful systems that are used for clearing, settlement, and tracking the ownership of assets. Ledgers contain buckets of assets known as accounts and record transfers between them. Each account has a balance, which is the amount of the ledger's assets the account holds. Account balances may be positive or negative, representing assets or liabilities. | ||
| Stateful systems that are used for settlement and tracking the ownership of assets. Ledgers contain buckets of assets known as accounts and record transfers between them. Each account has a balance, which is the amount of the ledger's assets the account holds. Account balances may be positive or negative, representing assets or liabilities. | ||
|
|
||
| In Interledger v1, all Interledger packets were sent through ledgers. In Interledger v4, ledgers are primarily used as Settlement Systems to settle Balances accrued between nodes. | ||
|
|
||
|
|
||
|
pgarg-ripple marked this conversation as resolved.
|
||
| ## Link | ||
|
|
||
| A communication path between two Interledger nodes to exchange ILP packets over an HTTPS or a WebSocket connection. | ||
| A communication path between two Interledger nodes to exchange ILP packets over an HTTPS or a WebSocket connection. | ||
|
|
||
| ## Money Bandwidth | ||
|
|
||
| See instead: [Bandwidth](#bandwidth) | ||
|
|
||
| ## Node | ||
|
|
||
|
|
@@ -162,6 +167,10 @@ See also: Streaming Payments | |
|
|
||
| In the context of ILPv4, a payment is understood to mean the transfer of value from the sender (payer) to the receiver (payee). Higher-level protocols may execute a "payment" by sending a series of ILP Packets whose sum is equal to the desired payment value. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The clearing and settlement definitions also reference "payer" and "payee," but those are between two peers, not between the sender and receiver |
||
|
|
||
| ## Payment Bandwidth | ||
|
|
||
| See instead: [Bandwidth](#bandwidth) | ||
|
|
||
| ## Payment Channel | ||
|
|
||
| A payment channel is a medium used by two parties to perform multiple value transactions amongst them, without sending these transactions to the underlying ledger. One or both parties will generally transfer some of their value assets on the ledger to the payment channel. Value transfers are then made between the two parties by exchanging "claims" that update their balance. When one of the parties wishes to close the channel, they submit the final balance to the ledger. | ||
|
|
@@ -170,7 +179,11 @@ A payment channel is a medium used by two parties to perform multiple value tran | |
|
|
||
| A payment pointer is a standardized identifier for accounts that can receive payments. It is like an email address, but for sending/receiving value. | ||
|
pgarg-ripple marked this conversation as resolved.
|
||
|
|
||
| A payment pointer resolves to an HTTPS URL that provides the location of a payment setup service endpoint at which a sender can initiate a payment to the receiver. | ||
| A payment pointer resolves to an HTTPS URL that provides the location of a payment setup service endpoint at which a sender can initiate a payment to the receiver. | ||
|
|
||
| For example, a pointer pointer such as `$example.com/bob` will resolve to `https://example.com/bob` endpoint URL. | ||
|
|
||
| See also: [IL-RFC 26](https://github.com/interledger/rfcs/blob/master/0026-payment-pointers/0026-payment-pointers.md) | ||
|
|
||
| ## Peer | ||
|
|
||
|
|
@@ -194,7 +207,7 @@ A (final) transfer state whereby funds have been returned to the sender. | |
|
|
||
| ## Route | ||
|
|
||
| A set of transfers chained together by the routers between them. The route is the path a payment has taken, or a future payment could take. | ||
| The path a payment has taken or a future payment could take. | ||
|
|
||
| ## Router | ||
|
|
||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.