Fixed client port issues in 'run.sh'

README.md

@@ -109,7 +109,7 @@ run `gg18_keygen_client` as follows: `./gg18_keygen_client http://127.0.0.1:8000
 
 ### Sign
 
-Run `./gg18_sign_client`. The application should be in the same folder as the `keys.store` file (or custom filename generated in keygen). the application takes three arguments: `IP:port` as in keygen, `filename` and message to be signed: `./gg18_sign_client http://127.0.0.1:8001 keys.store "KZen Networks"`. The same message should be used by all signers. Once `t+1` parties join the protocol will run and will output to screen signature (R,s).
+Run `./gg18_sign_client`. The application should be in the same folder as the `keys.store` file (or custom filename generated in keygen). the application takes three arguments: `IP:port` as in keygen, `filename` and message to be signed: `./gg18_sign_client http://127.0.0.1:8000 keys.store "KZen Networks"`. The same message should be used by all signers. Once `t+1` parties join the protocol will run and will output to screen signature (R,s).
 
 The `./gg18_sign_client` executable initially tries to unhex its input message (the third parameter). Before running ensure two things:
 

demo/run.sh

@@ -21,7 +21,7 @@ echo "keygen part"
 for i in $(seq 1 $n)
 do
     echo "key gen for client $i out of $n"
-    ./target/release/examples/gg18_keygen_client http://127.0.0.1:8001 keys$i.store &
+    ./target/release/examples/gg18_keygen_client http://127.0.0.1:8000 keys$i.store &
     sleep 3
 done
 
@@ -33,7 +33,7 @@ echo "sign"
 for i in $(seq 1 $((t+1)));
 do
     echo "signing for client $i out of $((t+1))"
-    ./target/release/examples/gg18_sign_client http://127.0.0.1:8001 keys$i.store "KZen Networks" &
+    ./target/release/examples/gg18_sign_client http://127.0.0.1:8000 keys$i.store "KZen Networks" &
     sleep 3
 done