4
votes
Accepted
what is the reason for "wrong predecessor" when endorsing
This means that you try to inject an endorsement in your mempool for a block that wasn't the head block. Maybe the chain reorganized between the time your endorser started preparing an endorsement and ...
- 4,599
2
votes
Accepted
Downsides to running multiple endorsers?
This is correct but extremely and dangerously (for yourself) optimistic.
Yes, in theory, as long are the 2 nodes you attach an endorser to are perfectly aligned "It's the same block, and the same ...
2
votes
Missed my endorsement
This question was originally asked on r/Tezos where I replied with the following:
Unfortunately this is a fact of life for bakers (endorsers) from time to time. In general, there are a number of ...
- 332
2
votes
Missed my endorsement
Posting the reddit answer by BakeTzForMe:
Unfortunately this is a fact of life for bakers (endorsers) from time
to time. In general, there are a number of possible causes for
something like ...
- 604
2
votes
Accepted
Why my endorser did not endorse the block 316956?
The error logs clearly suggest that the ENOTTY error for the "auth" key is your problem.
You cannot directly use an encrypted key to authenticate the docker daemons to a remote signer, because you ...
- 2,506
1
vote
Accepted
Ignore block : forged too far the past
It means that when your node received that block, the block was more than 30 minutes old already (its timestamp was from more than 30 minutes ago). Your endorser correctly acknowledged that the node ...
Only top scored, non community-wiki answers of a minimum length are eligible