unboundsecurity / blockchain-crypto-mpc

Protecting cryptographic signing keys and seed secrets with Multi-Party Computation.
GNU General Public License v3.0
454 stars 167 forks source link

getting the same share for both parties with the python mpc script #22

Closed Tony-Stark closed 2 years ago

Tony-Stark commented 2 years ago

I followed the comments in mpc_demo.py to test key generation. The example is as follows. Example 1: Generate a split EDDSA key user1@host1> python mpc_demo.py --out_file key_share.bin --server user2@host2> python mpc_demo.py --type EDDSA --command generate --out_file key_share.bin --host host1

I ran them both on the same machine, but in two different sessions kinda like this: user1@host1> python mpc_demo.py --out_file key_share1.bin --server user1@host1> python mpc_demo.py --type EDDSA --command generate --out_file key_share2.bin --host localhost

but key_share1 and key_share2 are identitcal. What's happening? Is it because it runs on the same machine? Or did I misunderstood something else?

Tony-Stark commented 2 years ago

I tried to check the python script (the same way as above) using two machines instead of localhost. I checked the firewall rules, and checked that the correct ports are up on both sides. The 2 machines communicate fine with other programs, and there's a ping. But using the python script nothing happens for awhile and then I get Traceback (most recent call last): File "mpc_demo.py", line 273, in run_client() File "mpc_demo.py", line 216, in run_client clientsocket.connect((args.host, args.port)) TimeoutError: [Errno 110] Connection timed out

Philamericus commented 2 years ago

Hi. On September 1, 2021 we stopped supporting this project, so unfortunately I don't have anyone from the project to answer your question. Sorry!