Bounty for fixing Core Lightning issues

7 replies 149 views
Gig4L0rdSenior Member
Posts: 234 · Reputation: 1329
#1Jan 26, 2018, 12:34 AM
There's a Bitcoin address set up to get Core Lightning fixed. If you wanna help with the development, you can send some funds to 1AzajWfrD8X6XoJEZ2Vshbd5492B1sxamT. Core Lightning's got a pretty serious issue: the pay function just doesn't work (check it out here). Boltz Exchange whipped up a workaround plugin, but honestly, it doesn't cut it. What CLN really needs is a proper native pay function that just works straight up. Sure, LND and Phoenix can struggle a bit with finding payment routes too, but CLN takes the cake for failing to pay invoices all the time. It doesn't matter how many nodes are connected, how much balance is in the channel, or what the invoice amount is, it just won't go through. Once they get CLN fixed and users can actually rely on the native pay function without needing any add-ons or plugins, the money sitting in that address will be handed out to the developers who took part in the fix. If more than one person chips in, the cash will be split based on what each developer contributed, with Rusty Russell, the lead dev for CLN, deciding how to divvy it up. For the latest updates on this bounty, just check this link.
8 Reply Quote Share
im_lynxHero Member
Posts: 515 · Reputation: 2161
#2Jan 27, 2018, 07:21 PM
Do you control the address 1AzajWfrD8X6XoJEZ2Vshbd5492B1sxamT and has the initial funding of 2BTC been transfered by you (I'm aware we can't check your answer, unless you sign bitcoin messages from this and the funding address)? Your account is new and has no reputation. Despite the initial funding, why would anyone trust you to add additional funds? I'm not against such nice initiatives to fix apparent problems and to boost further development and debugging. Just minor nitpicking: why legacy addresses? Not important to answer, though, I don't want to derail the topic. I get an error when trying to access the pastebin via your provided link:
2 Reply Quote Share
hash_bossLegendary
Posts: 1166 · Reputation: 5261
#3Jan 28, 2018, 12:06 AM
I just have a question, why don't you mention existence of this bounty on the CLN GitHub instead? That way, you could attract more developer who could fix the problem. OP or pastebin moderator already fix that problem. Currently, that pastebin is duplicate of this thread.
3 Reply Quote Share
colddiamondHero Member
Posts: 623 · Reputation: 2467
#4Jan 28, 2018, 12:56 AM
I am with Cricktor. Why legacy? And how are you related to this bounty? And what has Core Lightning / and or Rusty Russell  said about the bounty. On a side note, it does work for me I just used it to pay a bitrefill invoice so I don't know how widespread this issue really is. -Dave
3 Reply Quote Share
Gig4L0rdSenior Member
Posts: 234 · Reputation: 1329
#5Jan 28, 2018, 08:30 AM
I do control the address. Verify with: I am not petitioning for additional funds to be sent to the address, but the option to do so remains. The pastebin access error you encountered should be resolved. Legacy because I lack knowledge about how to use modern Bitcoin Core. Thank you for your suggestion. https://github.com/ElementsProject/lightning/issues/7180#issuecomment-2408146316 My ignorance. I am the initiator. Nothing yet. It is the most commented ongoing issue on the Core Lightning Github page: https://github.com/ElementsProject/lightning/issues?q=is%3Aissue+is%3Aopen+sort%3Acomments-desc
1 Reply Quote Share
Posts: 6 · Reputation: 80
#6Jan 29, 2018, 08:56 AM
I can suggest these changes in libplugin-pay.c.
6 Reply Quote Share
im_lynxHero Member
Posts: 515 · Reputation: 2161
#7Jan 31, 2018, 07:06 PM
Signature verifies true. To prove that you as user buildalight are able to make such signatures or collude with someone else who signs on your bidding, you'd need to sign a message containing your identity and current date and time, something like "My account is buildalight and I started this topic 'Bounty to fix Core Lightning' on 2024-10-11, 00:57:15 UTC. This message has been signed 2024-10-xy." (replace xy with day no. of signage). What you signed before doesn't contain much to link it to your account. Messages signed without such details could be signed way in the past. Just saying... I'm not nagging you to do so. Please, don't see it as hostility: I highly recommend to read and understand the Unofficial list of (official) Bitcointalk.org rules, guidelines, FAQ. Multiple consecutive posts within short time frames (less than 24h) as you did are not allowed according to rule #32. It's OK to bump a topic after a minimum of 24h. Delete your own most recent older bumps if you re-bump a topic. There's no need to answer different users in separate posts. You can always edit your last post and insert quotes of other users you want to respond to by using the Insert Quote links in the Topic Summary below the reply entry box.
4 Reply Quote Share
Gig4L0rdSenior Member
Posts: 234 · Reputation: 1329
#8Jan 31, 2018, 11:19 PM
@ElonMusk_ia I can't read this code, but get the CLN developers to incorporate your solution into Core Lightning's codebase to fix CLN's native pay function. Once you have achieved this, please let everybody know and we'll download the latest CLN package to verify that the pay function has been fixed, and I'll pay you whatever proportion of the allocated funds CLN lead developer Rusty Russell specifies. @Cricktor Thanks for the suggestions.
1 Reply Quote Share
?Reply
Sign in to reply to this topic

Related topics