AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Getamped2 inherits3/12/2023 ![]() Recurring invoices are not implemented in this release, but will be available at a later point. For now an AMP invoice can only be settled by one payment. That said, this release does include support for simulating recurring payments, making the existing AMP invoices "pseudo-reusable" by allowing users to specify a new random payment address. Payment Optimizations MPP/AMP Payment Splitting on by Default The default expiry for AMP invoices is 30 days. Payment splitting was previously made available on an opt-in basis. In this version of lnd, MPP/AMP payment splitting is now activated by default. The default number of attempted splits is 16 and it’s also possible to specify the size of the largest split. This can be used to force a maximum payment size leading to more frequent payment splitting. Typically lnd will mark a channel as a zombie when both of its edges aren't re-advertised within a two week period. This is typically referred to as a channel's heartbeat update. Analysis by Conner Fromknecht demonstrated that the channel graph itself could be shrunk by ~20% if a stricter pruning heuristic was adopted: pruning a channel once only a single edge fails the heartbeat check. The latest version implements this stricter pruning alternative in an opt-in manner. The spec compliant anchor channel format was introduced in v0.12. In v0.13, if both nodes support it, the anchor channel format is the default channel type. Anchor channels are a safer and more reliable channel type as they allow for fee bumping the commitment transaction in the event a channel is force closed. ![]() They take away the up-front guesswork of determining what the proper on-chain fees will be, as they allow a node to dynamically increase the fee of a pending commitment transaction using Child Pays for Parent (CPFP). Since a node with anchor channels must keep on-chain funds around in case unilateral fee bumping is needed, we reserve 10k sats per channel for this purpose. ![]() In this release, we cap this hold at 100k sats and avoid reserving this value for private channels.
0 Comments
Read More
Leave a Reply. |