You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ILP STREAM isn't necessary the best fit for Rafiki payments, at least in the near term.
Rafiki only uses configured trusted ILP peers.
Prospective Rafiki operators have indicated they will likely only allow transacting with direct peers, with no intermediary connectors, which Rafiki doesn't even support yet:
An alternative ILP transport is STREAM's predecessor PSKv2, which should support single packet quoting and sending, but whose library appears deprecated?
@justmoon would that complicate Dassie <> Rafiki payments? What are your general thoughts on that idea? I know that you always have the analogy that we also use TCP/IP locally.
Basically, I wonder whether we complicate things by allowing different transport layer protocols.
ILP STREAM isn't necessary the best fit for Rafiki payments, at least in the near term.
Rafiki only uses configured trusted ILP peers.
Prospective Rafiki operators have indicated they will likely only allow transacting with direct peers, with no intermediary connectors, which Rafiki doesn't even support yet:
An alternative ILP transport is STREAM's predecessor PSKv2, which should support single packet quoting and sending, but whose library appears deprecated?
ilpStreamConnection
with methods/transports open-payments#219The text was updated successfully, but these errors were encountered: