-
Notifications
You must be signed in to change notification settings - Fork 75
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
DKG Example failing "dial backoff" #243
Comments
Hi mvanmeerbeck, We will check it and fix it. Thanks for your information. |
Hi, |
Hi,
I guess that the threshold t = 2 in your situation. You can set
threshold t=3, then 1, 0, 0 and 1,0, 1 should be passed.
If the above guess is wrong, please let me know. Thanks a lot.
Sincerely,
Chih Yun
Maxime Vanmeerbeck ***@***.***> 於 2023年3月8日 週三 下午6:58寫道:
… Hi,
I also tried all the releases 1.0.0, 1.0.1 and 1.0.2, same problem.
FYI, i'm on ubuntu 18, go1.20.1
—
Reply to this email directly, view it on GitHub
<#243 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK4AJBAENANFAV3MFVBH3XTW3BQ5JANCNFSM6AAAAAAVROIGOQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I didn't change any configuration so t=3 already
|
If i use only 2 parties, it works
|
Hi mvanmeerbeck, |
Thank you, |
Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT (but probably just miss configuration)
What happened:
I can't get the dkg example to work, except few "Received request" and "Sent message ", the nodes keeps failing to connect to others nodes with the error
"dial backoff"
What you expected to happen:
I didn't do much except following the DKG demo, launched the 3 commands locally. No file is created in
./example/dkg
Here the logs
Node 1
Node 2
Node 3
How to reproduce it (as minimally and precisely as possible):
make tss-example
and on the same machine, in 3 terminals:
./example dkg --config dkg/id-10001-input.yaml
./example dkg --config dkg/id-10002-input.yaml
./example dkg --config dkg/id-10003-input.yaml
Anything else we need to know?:
Thanks for this work & your help!
The text was updated successfully, but these errors were encountered: