Created
March 28, 2018 14:05
-
-
Save nissshh/eb303e352f55700fbfe373035f9b906f to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Below are the validators | |
On Terminal 0 I started Validato 0,Rest API 0, settings-tp 0 and identity tp0 | |
1.sudo sawtooth-validator -vv --bind network:tcp://10.34.14.1:8800 --bind component:tcp://10.34.14.1:4004 --peering dynamic --endpoint tcp://10.34.14.1:8800 --scheduler serial --network-auth challenge | |
2.settings-tp -C tcp://10.34.14.1:4004 | |
3.identity-tp -C tcp://10.34.14.1:4004 | |
4.sawtooth-rest-api -C tcp://10.34.14.1:4004 -B 10.34.14.1:8008 | |
I also registered a valida user for settings as below for user dev. | |
$sawset proposal create sawtooth.identity.allowed_keys=02a8d5d019a596e979e073dedd559ab23e4982f35d79292e50b94e2aa8e2f5d626 --url http://10.34.14.1:8008 | |
$ sudo sawtooth identity policy create policy_sandip "PERMIT_KEY 03a16e1d0dc29ba97a6af90679b3ce7ba0fd452bd1210f8fa02d46f5b4f92526c1" --url http://10.34.14.1:8008 -k ~/.sawtooth/keys/dev.priv | |
Policy committed in 0.142006 sec | |
$sudo sawtooth identity role create network policy_sandip -k /home/dev/.sawtooth/keys/dev.priv --url http://10.34.14.1:8008 | |
Role committed in 0.136423 sec | |
$ sudo sawtooth identity role create transactor policy_sandip -k /home/dev/.sawtooth/keys/dev.priv --url http://10.34.14.1:8008 | |
Role committed in 0.134269 sec | |
$ sawtooth identity role list --url http://10.34.14.1:8008 | |
network: policy_sandip | |
transactor: policy_sandip | |
then I started validator,settings,identity and rest api on other node as another ubuntu machine whose validator pub key is 03a16e1d0dc29ba97a6af90679b3ce7ba0fd452bd1210f8fa02d46f5b4f92526c1 | |
$sudo sawtooth-validator -v --bind network:tcp://10.34.15.58:8800 --bind component:tcp://10.34.15.58:4004 --peering dynamic --endpoint tcp://10.34.15.58:8800 --seeds tcp://10.34.14.1:8800 --scheduler serial --network-auth challenge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Any example with more than one PERMIT_KEY?
The key that you permit is the validator key?