Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signature failing during the funding_sign with core lightning #123

Open
vincenzopalazzo opened this issue Nov 11, 2024 · 0 comments
Open
Labels
🐛 bug 🐛 Something isn't working discussion issue designed for discussion 🔨 CI/CD 🔨 Related to Github workflow 🔨 to be reproduced 🔨 Required to be reproduced in the test env

Comments

@vincenzopalazzo
Copy link
Collaborator

vincenzopalazzo commented Nov 11, 2024

While running the current code on the latest core lightning while I am trying to simplify it a little bit but I am starting to realize that it is a complete mess and we should rewrite it from scratch.

However, back to the issue. When lnprototest init a v1 funding channel there is a funding signature check failure.

If I remove the assertion inside the test https://github.com/rustyrussell/lnprototest/blob/master/tests/test_bolt2-01-open_channel.py#L265 the test tests/test_bolt2-01-open_channel.py::test_open_channel_opener_side will pass, otherwise will fail with the following error

2024-11-11T17:26:42.013Z DEBUG   hsmd: Shutting down

ERROR    root:utils.py:98 Traceback (most recent call last):
  File "/home/vincent/github/work/lnprototest/lnprototest/utils/utils.py", line 95, in run_runner
    runner.run(test)
  File "/home/vincent/github/work/lnprototest/lnprototest/runner.py", line 100, in run
    all_done = sequence.action(self)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/vincent/github/work/lnprototest/lnprototest/structure.py", line 55, in action
    all_done &= e.action(runner)
                ^^^^^^^^^^^^^^^^
  File "/home/vincent/github/work/lnprototest/lnprototest/event.py", line 602, in action
    raise EventError(self, "{} != {}".format(a, b))
lnprototest.errors.EventError: `20b36f9b3fb0577d078b13021e49c7b93d124bf3eb7c8f75d7decf6bdcd2c9475a76a118e1b8f44ce32eca7abee2704f463c54df223cccaa35a8624c3a4819b6 != Sig(0000000000000000000000000000000000000000000000000000000000000010,e6e1cf9c861f1b4c245652ff281a4f052427aa1342e3299e23d262390e73101c)` on event [{"event": "CheckEq", "file": "test_bolt2-01-open_channel.py", "pos": "265"},]
======================================================================================================================= short test summary info ========================================================================================================================
FAILED tests/test_bolt2-01-open_channel.py::test_open_channel_opener_side - AssertionError: `20b36f9b3fb0577d078b13021e49c7b93d124bf3eb7c8f75d7decf6bdcd2c9475a76a118e1b8f44ce32eca7abee2704f463c54df223cccaa35a8624c3a4819b6 != Sig(0000000000000000000000000000000000000000000000000000000000000010,e6e1cf9c861f1b4c245652ff281a4f052427aa134...

the type Sig is really black magic for me now and git blame point to @rustyrussell

@rustyrussell Du you have any clue on what can cause this regression? it is possible that a code change inside core lightning?

@Psycho-Pirate Do you see this problem in LDK sample?

@vincenzopalazzo vincenzopalazzo added 🐛 bug 🐛 Something isn't working 🔨 CI/CD 🔨 Related to Github workflow 🔨 to be reproduced 🔨 Required to be reproduced in the test env discussion issue designed for discussion labels Nov 11, 2024
vincenzopalazzo added a commit that referenced this issue Nov 18, 2024
cln version 24.05 is the last version of core lightning that it is
working with the version of prototest. Most lickly this is a cln
bug described in the following issue [1].

However, we pin the cln version and report the bug to mainline probably
someone will be able to find the real issue in the cln or lnprototest
at some point.

[1] #123
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
vincenzopalazzo added a commit that referenced this issue Nov 18, 2024
cln version 24.05 is the last version of core lightning that it is
working with the version of prototest. Most lickly this is a cln
bug described in the following issue [1].

However, we pin the cln version and report the bug to mainline probably
someone will be able to find the real issue in the cln or lnprototest
at some point.

[1] #123
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
vincenzopalazzo added a commit that referenced this issue Nov 18, 2024
cln version 24.05 is the last version of core lightning that it is
working with the version of prototest. Most lickly this is a cln
bug described in the following issue [1].

However, we pin the cln version and report the bug to mainline probably
someone will be able to find the real issue in the cln or lnprototest
at some point.

[1] #123
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
vincenzopalazzo added a commit that referenced this issue Nov 18, 2024
cln version 24.05 is the last version of core lightning that it is
working with the version of prototest. Most lickly this is a cln
bug described in the following issue [1].

However, we pin the cln version and report the bug to mainline probably
someone will be able to find the real issue in the cln or lnprototest
at some point.

[1] #123
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug 🐛 Something isn't working discussion issue designed for discussion 🔨 CI/CD 🔨 Related to Github workflow 🔨 to be reproduced 🔨 Required to be reproduced in the test env
Projects
None yet
Development

No branches or pull requests

1 participant