David Fuelling

Results 175 issues of David Fuelling

In the [IL-RFC-29](https://github.com/interledger/rfcs/blob/master/0029-stream/0029-stream.md#513-maximum-number-of-packets-per-connection) the spec warns against sending and receiving too many Stream packets with the same shared secret. We can likely utilize the sequence number here to detect this...

enhancement
crate/interledger-stream

Since ILP is intended to be able to support more than just currency exchange, we should rename the "thing" in the connector currently called "currency" to be "asset". Looking at...

Hyperledger would like the following files to exist in all HL repos (see report [here](https://gist.github.com/christo4ferris/13df399dff3613d405e8a60f23847385#file-gistfile1-txt-L4542)): - [ ] notice-file-exists: not found: (NOTICE*) The NOTICE file is described in section 4.4...

good first issue
documentation

Paying a PaymentPointer that doesn't exist responds with a T00 error, but instead should stop the payment. This is primarily a problem in StreamReceiver likely. A payment to a non-existent...

bug
stream

ILP Pay currently uses a PacingFilter and MaxPacketAmount filter to throttle the payment. We should consider adding something like the AIMDCongestionController into the mix. For JS, see [here](https://github.com/interledgerjs/interledgerjs/blob/master/packages/pay/src/controllers/liquidity-congestion.ts).

The latest JS ilp-protocol-stream is no longer generating a random token, but is instead encrypting it based upon the server secret. We should consider doing the same. See code here:...

https://azure.microsoft.com/

When an `IlpOverHttpLink` tries to send a packet, the send operation will occasionally fail with a `SocketTimeoutException`. In these cases, it would be useful to see the `LinkId` in the...

enhancement
ilp-link

The Link abstraction requires a LinkSettings, but it doesn't appear to be used in AbstractLink nor in IlpOverHttpLink. This is a good indicator that maybe we can remove this class,...

question
dependencies
ilp-link

The current implementation of PaymentPointer allows parses `$https://dev.foo.example.com/someone` to the URL `https://https//dev.foo.example.com/someone` which is not a valid URL. The PaymentPointer's normalization method should enforce that the [host](https://paymentpointers.org/syntax-resolution/#syntax) portion of a...

bug