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
{{ message }}
This repository has been archived by the owner on Dec 13, 2019. It is now read-only.
All apps have to be collateralized, which means waiting for on-chain updates (i.e deposit/withdrawal) means bad UX.
Example: Streaming payments. End users could be waiting to receive more payments, but have them blocked by a pending deposit transaction.
Example: De-collateralizing. Intermediaries could be de-collateralizing a channel and users would not be able to make a payment until that transaction is mined.
The text was updated successfully, but these errors were encountered:
This is particularly an issue right now while gas prices are spiking and so transactions are sometimes taking 20 minutes to mine. Would suck to lose access to your channel for 20 minutes.
You could implement a timeout but then that introduces potential channel-breaking conditions where a deposit goes through AFTER timeout. Even if you enforce timeout onchain (somehow), this would mean poor UX because none of your deposits would work. (We're going through this exact problem in v1 right now)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
All apps have to be collateralized, which means waiting for on-chain updates (i.e deposit/withdrawal) means bad UX.
Example: Streaming payments. End users could be waiting to receive more payments, but have them blocked by a pending deposit transaction.
Example: De-collateralizing. Intermediaries could be de-collateralizing a channel and users would not be able to make a payment until that transaction is mined.
The text was updated successfully, but these errors were encountered: