Ninjastic
Search content
Sort by
Showing 5 of 5 results by buildalight
Post
Topic
Board Development & Technical Discussion
Re: Bounty to fix Core Lightning.
by
buildalight
on 15/10/2024, 23:38:48 UTC

I can suggest these changes in libplugin-pay.c.
[/quote]

@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.
Post
Topic
Board Development & Technical Discussion
Re: Bounty to fix Core Lightning.
by
buildalight
on 11/10/2024, 21:51:06 UTC
Quote from: DaveF on Today at 12:21:14 PM
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

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
Post
Topic
Board Development & Technical Discussion
Re: Bounty to fix Core Lightning.
by
buildalight
on 11/10/2024, 21:36:31 UTC
Quote from: ABCbits on Today at 10:50:33 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.

Thank you for your suggestion.
https://github.com/ElementsProject/lightning/issues/7180#issuecomment-2408146316
Post
Topic
Board Development & Technical Discussion
Merits 1 from 1 user
Re: Bounty to fix Core Lightning.
by
buildalight
on 11/10/2024, 21:21:14 UTC
⭐ Merited by Cricktor (1)
Quote from: Cricktor on Today at 04:52:30 AM
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.


Quote from: buildalight on Today at 12:57:15 AM
For updates to this bounty, see: https://pastebin.com/raw/iACc2pYv

I get an error when trying to access the pastebin via your provided link:
Quote
Forbidden (#403)

Error, this is a private paste or is pending moderation. If this paste belongs to you, please login to Pastebin to view it.

I do control the address.
Verify with:
Code:
bitcoin-cli verifymessage "1AzajWfrD8X6XoJEZ2Vshbd5492B1sxamT" "IAm8YePM6nkiwGbUFiIkR2mztqS6lNNlvv16jvmH3W9adpYTg5CBZAL5ImeEc6NOdyeTVu2e9eyduyzg1j96fN0=" "Fix Core Lightning and Win This Bitcoin!"

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.
Post
Topic
Board Development & Technical Discussion
Topic OP
Bounty to fix Core Lightning.
by
buildalight
on 11/10/2024, 00:57:15 UTC
A Bitcoin address has been created to fix Core Lightning.
To fund development, send funds to 1AzajWfrD8X6XoJEZ2Vshbd5492B1sxamT.
https://bitcoinexplorer.org/address/1AzajWfrD8X6XoJEZ2Vshbd5492B1sxamT

Core Lightning's problem: the pay function fails (https://github.com/ElementsProject/lightning/issues/7180).

Boltz Exchange wrote a workaround plugin (https://github.com/ElementsProject/lightning/issues/6793) but this fix is insufficient. CLN needs a native pay function that works out-of-the box. LND and Phoenix fail to find payment routes at times, but not like CLN, which constantly fails to pay invoices, regardless of the number of nodes connected, channel balance, or invoice amount.
 
Once CLN is fixed and deployed (i.e. once users can use the native pay function reliably without any add-ons/plugins), the funds in the address above will be sent to the developers who are responsible for the fix. If multiple developers contribute to the solution, the funds will be allocated proportionally, with CLN lead developer Rusty Russell determining the payout proportions.

For updates to this bounty, see: https://pastebin.com/raw/iACc2pYv