4

It is done at the levels corresponding to the cycle positions 255, 511, ..., 4095. Given that cycle_position == (level - 1) % 4096 (the first cycle has started at level 1, genesis being special), the levels are 256, 512, ... The relevant code is here: let may_snapshot_roll ctxt = let level = Alpha_context.Level.current ctxt in let ...


4

This happens when the network is running late. This estimated_time is computed on the "every baker at priority 0 will bake" hypothesis. Each time a block is baked by the baker of priority 1, it is baked later and every following block has to be baked "later"... Reference Thanks to @Pierre Boutillier for helping with this


3

Yes, you missed the documentation about the new ACLs that were introduced. The new ACLs broke RPC for just about everyone. Here is a node config snippet that allows all RPCs from localhost, adjust your config similarly: "listen-addrs": [ ":8732" ], "acl": [ { "address": ":8732", "blacklist": []...


3

What is the meaning of “seed used at cycle”? Before we go any further, let's explain what this seed is. For cycle n's baking rights, cycle n - 7 is the cycle where we determine how many rolls each baker has. In order for the chain to determine the number of rolls each baker has, snapshots are taken throughout cycle n - 7, specifically every 256 blocks or 16 ...


3

It would appear as though those images are indeed wrong. Hard to determine 100% as there is so much going on with that post. (Side note: "tezzie" is wrong; the correct term is "tez"). Simply ask the chain to find the correct answer: $ curl "http://localhost:8732/chains/main/blocks/head/helpers/baking_rights?delegate=tz3RV1MBbZMR6899Okdjb7Mwj6LkbPSUS1eX1&...


3

tl;dr it is home-made CSPRNG based on repeatedly hashing an initial seed with Blake2b. Details: The interface of this CSPRNG can be found in the protocol here, and the implementation here. (Optionally, you can read the interface here, but the formatting is messed up.) The function take generates a new random value using State_hash: let take (S state) = ...


2

Blocks in Tezos are timestamped and it is assumed that nodes have synchronized clocks with bounded clock skew.


1

This webpage gives an explanation of the TzStats baker reliability index.


1

It is not possible to directly retrieve from the RPCs the information you are requesting. Some public services index chain metadata in order to be able to provide extra historical details. For example, in the current cycle 153 you can see that bakendorse displays the priority level of the missed bake. But they choosing to only display this information for ...


1

This is a known problem. As discussed on gitlab, it seems to be two problems disguised as one. The first problem is poor connectivity leading to the baker waiting and missing blocks. The second problem is that the baker may have a bug where even though there are endorsements in the node it thinks that there aren't any and waits. Restarting the baking ...


Only top voted, non community-wiki answers of a minimum length are eligible