POA Forum

Gnosis as an xDai validator

Hi guys,

This is Denis, software engineer at Gnosis. We are interested in being a validator / node operator of the POA network.

We are the team behind the Gnosis Multisig, Gnosis Safe, Dutch Exchange, Gnosis Protocol / Dfusion and many iterations of the Prediction Markets platform (Conditional Tokens now-a-days)

Best,

Denis

3 Likes

Mining key: 0x1438087186fdbfd4c256fa2df446921e30e54df8
Payout key: 0xe37fbb63c1be762fe4cce21d38e298405dff977a
Voting key: 0xd3537bd39480c91271825a862180551037fdda99
Bridge key: 0x263da4a2f4ed532084a32832d3fcd6af0bd6b95b

1 Like

Hi Denis,

great to have you here. I created a new proposal and voted already.

@xdai-validators please cast your votes.

1 Like

Thank you Sascha!

I’ll finish the setup soon,

Best

1 Like

Protofire has validated that it came from Denis and voted. :white_check_mark:

Easy access: https://voting.poa.network/poa-dapps-voting

2 Likes

Voted in. The quorum is reached.

77:51:11 left to finalize the ballot.

@denisgranha Before the ballot is finalized, you need to setup your node following the instruction https://www.xdaichain.com/for-validators/new-validator-process-flow/new-xdai-validator-node-setup

Hi Denis
Unfortunately we missed the voting timeframe - it was an intense weekend here in Austria. Just wanted to let you know that lab10 collective is happy to have you on board!

Hi guys,

Thank you for the welcome. The node is almost set up but it has the final steps missing, I don’t have these parameters:

  • NETSTATS_SERVER - ask an existing validator (e.g. POA) to provide you with correct url of the netstats server

  • NETSTATS_SECRET - ask an existing validators (e.g. POA) to share the netstats secret code with you or look it up in the private part of the forum if you already have access. Do not share it with non-validators or people outside of xDai network

And the link doesn’t work, can you help me with this?

Cool. I’ve added you to the private support group
here is info about the secret
https://forum.poa.network/t/netstats-server-info/2781/2

Finalized the Vote just now. You’re good to go.

1 Like

It seems that is not running properly?

parity.log

2020-03-16 14:58:46 UTC Running AuRa with a single validator implies instant finality. Use a database?
2020-03-16 14:58:47 UTC Starting Parity-Ethereum/v2.6.8-beta-9bf6ed8-20191231/x86_64-linux-gnu/rustc1.40.0
2020-03-16 14:58:47 UTC Keys path parity_data/keys/DaiChain
2020-03-16 14:58:47 UTC DB path parity_data/chains/DaiChain/db/3c648cbdc4c9333d
2020-03-16 14:58:47 UTC State DB configuration: fast
2020-03-16 14:58:47 UTC Operating mode: active
2020-03-16 14:58:47 UTC Running AuRa with a single validator implies instant finality. Use a database?
2020-03-16 14:58:47 UTC Starting Parity-Ethereum/v2.6.8-beta-9bf6ed8-20191231/x86_64-linux-gnu/rustc1.40.0
2020-03-16 14:58:47 UTC Keys path parity_data/keys/DaiChain
2020-03-16 14:58:47 UTC DB path parity_data/chains/DaiChain/db/3c648cbdc4c9333d
2020-03-16 14:58:47 UTC State DB configuration: fast
2020-03-16 14:58:47 UTC Operating mode: active
2020-03-16 14:58:48 UTC Running AuRa with a single validator implies instant finality. Use a database?
2020-03-16 14:58:48 UTC Starting Parity-Ethereum/v2.6.8-beta-9bf6ed8-20191231/x86_64-linux-gnu/rustc1.40.0
2020-03-16 14:58:48 UTC Keys path parity_data/keys/DaiChain
2020-03-16 14:58:48 UTC DB path parity_data/chains/DaiChain/db/3c648cbdc4c9333d
2020-03-16 14:58:48 UTC State DB configuration: fast
2020-03-16 14:58:48 UTC Operating mode: active
2020-03-16 14:58:48 UTC Running AuRa with a single validator implies instant finality. Use a database?
2020-03-16 14:58:48 UTC Starting Parity-Ethereum/v2.6.8-beta-9bf6ed8-20191231/x86_64-linux-gnu/rustc1.40.0
2020-03-16 14:58:48 UTC Keys path parity_data/keys/DaiChain
2020-03-16 14:58:48 UTC DB path parity_data/chains/DaiChain/db/3c648cbdc4c9333d
2020-03-16 14:58:48 UTC State DB configuration: fast
2020-03-16 14:58:48 UTC Operating mode: active
2020-03-16 14:58:48 UTC Running AuRa with a single validator implies instant finality. Use a database?
2020-03-16 14:58:48 UTC Starting Parity-Ethereum/v2.6.8-beta-9bf6ed8-20191231/x86_64-linux-gnu/rustc1.40.0
2020-03-16 14:58:48 UTC Keys path parity_data/keys/DaiChain
2020-03-16 14:58:48 UTC DB path parity_data/chains/DaiChain/db/3c648cbdc4c9333d
2020-03-16 14:58:48 UTC State DB configuration: fast
2020-03-16 14:58:48 UTC Operating mode: active

netstat err logs

2020-03-16 14:58:15 +00:00: [sys] xxx Received kill signal, shutting down gracefully.
2020-03-16 14:58:16 +00:00: [sys] xxx Received kill signal, shutting down gracefully.
2020-03-16 14:58:33 +00:00: [eth] =✘= Web3 connection attempt #0 failed
2020-03-16 14:58:33 +00:00: [eth] =✘= Trying again in 500 ms
2020-03-16 14:58:72 +00:00: [eth] =✘= Web3 connection attempt #1 failed
2020-03-16 14:58:72 +00:00: [eth] =✘= Trying again in 1000 ms
2020-03-16 14:58:11 +00:00: [eth] =✘= Web3 connection attempt #2 failed
2020-03-16 14:58:11 +00:00: [eth] =✘= Trying again in 1500 ms
2020-03-16 14:58:41 +00:00: [eth] =✘= Web3 connection attempt #3 failed
2020-03-16 14:58:41 +00:00: [eth] =✘= Trying again in 2000 ms
2020-03-16 14:59:59 +00:00: [eth] =✘= Web3 connection attempt #4 failed
2020-03-16 14:59:59 +00:00: [eth] =✘= Trying again in 2500 ms
2020-03-16 14:59:76 +00:00: [eth] =✘= Web3 connection attempt #5 failed
2020-03-16 14:59:76 +00:00: [eth] =✘= Trying again in 3000 ms
2020-03-16 14:59:93 +00:00: [eth] =✘= Web3 connection attempt #6 failed
2020-03-16 14:59:93 +00:00: [eth] =✘= Trying again in 3500 ms
2020-03-16 14:59:10 +00:00: [eth] =✘= Web3 connection attempt #7 failed
2020-03-16 14:59:10 +00:00: [eth] =✘= Trying again in 4000 ms
2020-03-16 14:59:28 +00:00: [eth] =✘= Web3 connection attempt #8 failed
2020-03-16 14:59:28 +00:00: [eth] =✘= Trying again in 4500 ms
2020-03-16 14:59:45 +00:00: [eth] =✘= Web3 connection attempt #9 failed
2020-03-16 14:59:45 +00:00: [eth] =✘= Trying again in 5000 ms
2020-03-16 14:59:62 +00:00: [eth] =✘= Web3 connection attempt #10 failed
2020-03-16 14:59:62 +00:00: [eth] =✘= Trying again in 5500 ms
2020-03-16 15:00:80 +00:00: [eth] =✘= Web3 connection attempt #11 failed
2020-03-16 15:00:80 +00:00: [eth] =✘= Trying again in 6000 ms
2020-03-16 15:00:00 +00:00: [eth] =✘= Web3 connection attempt #12 failed
2020-03-16 15:00:00 +00:00: [eth] =✘= Trying again in 6500 ms
2020-03-16 15:00:17 +00:00: [eth] =✘= Web3 connection attempt #13 failed
2020-03-16 15:00:17 +00:00: [eth] =✘= Trying again in 7000 ms
2020-03-16 15:00:34 +00:00: [eth] =✘= Web3 connection attempt #14 failed
2020-03-16 15:00:34 +00:00: [eth] =✘= Trying again in 7500 ms
2020-03-16 15:00:50 +00:00: [eth] =✘= Web3 connection attempt #15 failed
2020-03-16 15:00:51 +00:00: [eth] =✘= Trying again in 8000 ms
2020-03-16 15:01:68 +00:00: [eth] =✘= Web3 connection attempt #16 failed
2020-03-16 15:01:68 +00:00: [eth] =✘= Trying again in 8500 ms
2020-03-16 15:01:84 +00:00: [eth] =✘= Web3 connection attempt #17 failed
2020-03-16 15:01:84 +00:00: [eth] =✘= Trying again in 9000 ms
2020-03-16 15:01:01 +00:00: [eth] =✘= Web3 connection attempt #18 failed
2020-03-16 15:01:01 +00:00: [eth] =✘= Trying again in 9500 ms
2020-03-16 15:02:18 +00:00: [eth] =✘= Web3 connection attempt #19 failed
2020-03-16 15:02:18 +00:00: [eth] =✘= Trying again in 10000 ms
2020-03-16 15:02:35 +00:00: [eth] =✘= Web3 connection attempt #20 failed
2020-03-16 15:02:37 +00:00: [eth] =✘= Trying again in 10500 ms
2020-03-16 15:02:53 +00:00: [eth] =✘= Web3 connection attempt #21 failed
2020-03-16 15:02:53 +00:00: [eth] =✘= Trying again in 11000 ms
2020-03-16 15:03:70 +00:00: [eth] =✘= Web3 connection attempt #22 failed
2020-03-16 15:03:70 +00:00: [eth] =✘= Trying again in 11500 ms
2020-03-16 15:03:87 +00:00: [eth] =✘= Web3 connection attempt #23 failed
2020-03-16 15:03:87 +00:00: [eth] =✘= Trying again in 12000 ms
2020-03-16 15:03:04 +00:00: [eth] =✘= Web3 connection attempt #24 failed
2020-03-16 15:03:04 +00:00: [eth] =✘= Trying again in 12500 ms
2020-03-16 15:04:21 +00:00: [eth] =✘= Web3 connection attempt #25 failed
2020-03-16 15:04:21 +00:00: [eth] =✘= Trying again in 13000 ms
2020-03-16 15:04:38 +00:00: [eth] =✘= Web3 connection attempt #26 failed
2020-03-16 15:04:38 +00:00: [eth] =✘= Trying again in 13500 ms
2020-03-16 15:05:55 +00:00: [eth] =✘= Web3 connection attempt #27 failed
2020-03-16 15:05:55 +00:00: [eth] =✘= Trying again in 14000 ms
2020-03-16 15:05:72 +00:00: [eth] =✘= Web3 connection attempt #28 failed
2020-03-16 15:05:73 +00:00: [eth] =✘= Trying again in 14500 ms
2020-03-16 15:06:90 +00:00: [eth] =✘= Web3 connection attempt #29 failed
2020-03-16 15:06:90 +00:00: [eth] =✘= Trying again in 15000 ms
2020-03-16 15:06:07 +00:00: [eth] =✘= Web3 connection attempt #30 failed
2020-03-16 15:06:07 +00:00: [eth] =✘= Trying again in 15500 ms
2020-03-16 15:07:24 +00:00: [eth] =✘= Web3 connection attempt #31 failed
2020-03-16 15:07:24 +00:00: [eth] =✘= Trying again in 16000 ms
2020-03-16 15:07:40 +00:00: [eth] =✘= Web3 connection attempt #32 failed
2020-03-16 15:07:41 +00:00: [eth] =✘= Trying again in 16500 ms
2020-03-16 15:08:58 +00:00: [eth] =✘= Web3 connection attempt #33 failed
2020-03-16 15:08:58 +00:00: [eth] =✘= Trying again in 17000 ms
2020-03-16 15:08:74 +00:00: [eth] =✘= Web3 connection attempt #34 failed
2020-03-16 15:08:74 +00:00: [eth] =✘= Trying again in 17500 ms
2020-03-16 15:09:91 +00:00: [eth] =✘= Web3 connection attempt #35 failed
2020-03-16 15:09:91 +00:00: [eth] =✘= Trying again in 18000 ms
2020-03-16 15:10:08 +00:00: [eth] =✘= Web3 connection attempt #36 failed
2020-03-16 15:10:08 +00:00: [eth] =✘= Trying again in 18500 ms
2020-03-16 15:10:25 +00:00: [eth] =✘= Web3 connection attempt #37 failed
2020-03-16 15:10:25 +00:00: [eth] =✘= Trying again in 19000 ms
2020-03-16 15:11:43 +00:00: [eth] =✘= Web3 connection attempt #38 failed
2020-03-16 15:11:43 +00:00: [eth] =✘= Trying again in 19500 ms
2020-03-16 15:11:59 +00:00: [eth] =✘= Web3 connection attempt #39 failed
2020-03-16 15:11:59 +00:00: [eth] =✘= Trying again in 20000 ms

netstat out

2020-03-16 14:40:31 +00:00: [eth]
2020-03-16 14:40:31 +00:00: [eth] NET STATS CLIENT
2020-03-16 14:40:31 +00:00: [eth] v0.1.1
2020-03-16 14:40:31 +00:00: [eth]
2020-03-16 14:40:31 +00:00: [eth]
2020-03-16 14:40:31 +00:00: [eth] =i= Starting web3 connection
2020-03-16 14:41:30 +00:00:
2020-03-16 14:41:30 +00:00: [sys] xxx Closed node watcher
2020-03-16 14:41:31 +00:00:
2020-03-16 14:41:31 +00:00: [sys] xxx Closed node watcher
2020-03-16 14:41:30 +00:00: [sys] xxx Closed out remaining connections.
2020-03-16 14:41:62 +00:00: [eth]
2020-03-16 14:41:63 +00:00: [eth] NET STATS CLIENT
2020-03-16 14:41:63 +00:00: [eth] v0.1.1
2020-03-16 14:41:63 +00:00: [eth]
2020-03-16 14:41:63 +00:00: [eth]
2020-03-16 14:41:63 +00:00: [eth] =i= Starting web3 connection
2020-03-16 14:58:15 +00:00:
2020-03-16 14:58:15 +00:00: [sys] xxx Closed node watcher
2020-03-16 14:58:16 +00:00:
2020-03-16 14:58:16 +00:00: [sys] xxx Closed node watcher
2020-03-16 14:58:14 +00:00: [sys] xxx Closed out remaining connections.
2020-03-16 14:58:88 +00:00: [eth]
2020-03-16 14:58:89 +00:00: [eth] NET STATS CLIENT
2020-03-16 14:58:89 +00:00: [eth] v0.1.1
2020-03-16 14:58:89 +00:00: [eth]
2020-03-16 14:58:89 +00:00: [eth]
2020-03-16 14:58:89 +00:00: [eth] =i= Starting web3 connection

Looks like it fails to start syncing. Might be a rights or network issue.
Does the data folder has to correct access rights?

It was an issue with the mining key, for some reason it wasn’t copied by the ansible script to the proper folder.

Now I have the following issue, the node is not getting peers:

2020-03-16 18:25:19 UTC Running AuRa with a single validator implies instant finality. Use a database?
2020-03-16 18:25:19 UTC Starting Parity-Ethereum/v2.6.8-beta-9bf6ed8-20191231/x86_64-linux-gnu/rustc1.40.0
2020-03-16 18:25:19 UTC Keys path parity_data/keys/DaiChain
2020-03-16 18:25:19 UTC DB path parity_data/chains/DaiChain/db/3c648cbdc4c9333d
2020-03-16 18:25:19 UTC State DB configuration: fast
2020-03-16 18:25:19 UTC Operating mode: active
2020-03-16 18:25:19 UTC Not preparing block; cannot sign.
2020-03-16 18:25:19 UTC Configured for DaiChain using AuthorityRound engine
2020-03-16 18:25:19 UTC Public node URL: enode://d6122f0a61b6d4f0e0d07e9d1db5f7abafa108b652aebd95734cd4a7d5aa7dae2fdc43a665f8a8085aae16ad14c42d16b98b9301a6925c11303f8414afba7b92@3.121.222.238:30303
2020-03-16 18:25:20 UTC Running AuRa with a single validator implies instant finality. Use a database?
2020-03-16 18:25:54 UTC 0/25 peers 920 bytes chain 2 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 2 req/s, 34 µs
2020-03-16 18:26:24 UTC 0/25 peers 920 bytes chain 2 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 2 req/s, 34 µs
2020-03-16 18:26:54 UTC 0/25 peers 920 bytes chain 2 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 2 req/s, 34 µs
2020-03-16 18:27:24 UTC 0/25 peers 920 bytes chain 2 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 2 req/s, 33 µs
2020-03-16 18:27:54 UTC 0/25 peers 920 bytes chain 2 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 2 req/s, 34 µs

maybe a bootnode issue? these are the only two I have

$ cat bootnodes.txt
enode://efd05b4f75958db8811b47c113029c83bb27e2f7d7e96b6373472526497b483e7c7b7d0effae9e96a7c2d8a91b28acd6b7a8dceacc83a456579527e32589c36d@40.114.30.243:30303
enode://6d805cc58074f0ad0698a449b1d1736dedbf698253dce2f7f08ed36c2fc39266db95bc0b356d96acffc2616cb8ff8a1f13ef86421152f09b2fbb8b33ba6e7849@104.211.20.139:30303

Found this list, and now it syncs https://raw.githubusercontent.com/poanetwork/poa-chain-spec/dai/bootnodes.txt

Another issue :sweat_smile:

2020-03-16 18:53:53 UTC Syncing #0 0x4f1d…9756 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 0 Qed #0 5/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:53:58 UTC Syncing snapshot 8/21 #0 5/25 peers 920 bytes chain 2 KiB db 0 bytes queue 5 KiB sync RPC: 0 conn, 2 req/s, 25 µs
2020-03-16 18:54:02 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:54:03 UTC Syncing #0 0x4f1d…9756 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 0 Qed #0 4/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 25 µs
2020-03-16 18:54:04 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:54:09 UTC Syncing snapshot 11/21 #0 6/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 25 µs
2020-03-16 18:54:13 UTC Syncing snapshot 21/21 #0 6/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:54:13 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:54:13 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:54:18 UTC Syncing snapshot 12/21 #0 5/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:54:21 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:54:22 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:54:23 UTC Snapshot initializing (0/21 chunks restored, 0%) #0 5/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:54:29 UTC Syncing snapshot 12/21 #0 6/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:54:31 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:54:33 UTC Syncing #0 0x4f1d…9756 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 0 Qed #0 5/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:54:33 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:54:39 UTC Syncing snapshot 14/21 #0 5/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:54:42 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:54:43 UTC Syncing #0 0x4f1d…9756 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 0 Qed #0 6/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:54:43 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:54:48 UTC Syncing snapshot 11/21 #0 6/25 peers 920 bytes chain 2 KiB db 0 bytes queue 5 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:54:52 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:54:53 UTC Syncing #0 0x4f1d…9756 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 0 Qed #0 6/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:54:53 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:54:59 UTC Syncing snapshot 11/21 #0 7/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:55:02 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:55:02 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:55:03 UTC Syncing snapshot 1/21 #0 6/25 peers 920 bytes chain 2 KiB db 0 bytes queue 5 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:55:08 UTC Syncing snapshot 17/21 #0 7/25 peers 920 bytes chain 2 KiB db 0 bytes queue 6 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:55:10 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:55:11 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:55:13 UTC Syncing snapshot 1/21 #0 7/25 peers 920 bytes chain 2 KiB db 0 bytes queue 5 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:55:19 UTC Syncing snapshot 18/21 #0 7/25 peers 920 bytes chain 2 KiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:55:19 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:55:21 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:55:23 UTC Syncing snapshot 1/21 #0 7/25 peers 920 bytes chain 2 KiB db 0 bytes queue 9 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:55:28 UTC Syncing snapshot 18/21 #0 8/25 peers 920 bytes chain 2 KiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:55:30 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:55:31 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:55:35 UTC Syncing snapshot 9/21 #0 9/25 peers 920 bytes chain 2 KiB db 0 bytes queue 9 KiB sync RPC: 0 conn, 6 req/s, 26 µs
2020-03-16 18:55:38 UTC Syncing snapshot 20/21 #0 9/25 peers 920 bytes chain 2 KiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:55:38 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:55:40 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:55:44 UTC Syncing snapshot 11/21 #0 9/25 peers 920 bytes chain 2 KiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:55:48 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:55:48 UTC Syncing #0 0x4f1d…9756 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 0 Qed #0 9/25 peers 920 bytes chain 2 KiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 2 req/s, 27 µs
2020-03-16 18:55:49 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:55:54 UTC Syncing snapshot 12/21 #0 9/25 peers 920 bytes chain 2 KiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 6 req/s, 26 µs
2020-03-16 18:55:57 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:55:58 UTC Syncing #0 0x4f1d…9756 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 0 Qed #0 9/25 peers 920 bytes chain 2 KiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 2 req/s, 26 µs
2020-03-16 18:55:59 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:56:04 UTC Syncing snapshot 15/21 #0 9/25 peers 920 bytes chain 2 KiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 1 req/s, 26 µs
2020-03-16 18:56:07 UTC verify_block_external: bad proposer for step: 316872622
2020-03-16 18:56:08 UTC Encountered error during snapshot restoration: Engine error: Engine error (Author is not a current proposer: Expected 0xa335…80e6, found 0x9233…f103)
2020-03-16 18:56:08 UTC Syncing #0 0x4f1d…9756 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 0 Qed #0 10/25 peers 920 bytes chain 2 KiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 2 req/s, 26 µs

1 Like

Ok, the issue has been solved, apprently the command “git checkout dai” was copied and pasted but not executed and I didn’t realise this step until checking for the bootnode list.

1 Like

Ok, node has ben setup correctly and up to sync https://dai-netstat.poa.network/

2 Likes

@denisgranha OK, now please set your metadata: https://www.xdaichain.com/for-validators/new-validator-process-flow/new-xdai-validator-node-setup#10-set-metadata

1 Like