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
This file contains 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
This file contains 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
This file contains 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
use publisher confirms to wait until all messages have been published
This file contains 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
This file contains 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
I'm pushing for the hash-based solution because it can be implemented and developed quickly and easily and fixes the main issues we've seen on testnet:
routing sync on mobile nodes
"route not found" errors when you're missing routing info.
It can be deployed as an optional feature and will give us time to specify and implement proper IBLT-based filters.
It can be combined with the timestamp approach: nodes would send bucket hashes + low and high watermarks.
This file contains 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
We then create 3 directories for our eclair node, create an eclair.conf configuration file in each data directory, and all we need to change are the connections ports (so they can connect to the Litecoin client) and the fee rate (so that our opening/closing transactions will be relayed by the Litecoin client). And that’s it ! You can even see in the video that labels are still in BTC/milliBTC.
We then connected A to B, B to C, waited for all funding transactions to be confirmed and all channels announced, made a few payments, closed all channels and waited again for all closing transactions to be confirmed.
Sonatype: create a staging repository and pass it as a Github Action output.
This file contains 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