feat(f3): set initial power table for mainnet

[Kubuxu]

As reported by two of our nodes in lotus f3 status.
Set initial power table to bafy2bzacecklgxd2eksmodvhgurqvorkg3wamgqkrunir3al2gchv2cikgmbu.

EDIT: add first line

[ribasushi]

Is there some sort of CLI or whatnot that allows one to run independently and arrive at the same CID given a tipset? If not - can we add something to lotus-shed in a subsequent PR?

[Kubuxu]

@ribasushi
Run lotus f3 status or lotus f3 manifest

[masih]

lotus f3 manifest fills in the initial power table CID if it is not explicitly configured.

There is also:

$ lotus f3 certs get 0
Instance:     0
Power Table:
  Next:       bafy2bzacecklgxd2eksmodvhgurqvorkg3wamgqkrunir3al2gchv2cikgmbu
  Delta:      None
Finalized Chain:
  Length:     20
  Epochs:     4919580-4919599
  Chain:
    ├──4919580 (length: 5): [bafy2bzaceatt3chdvzyyvyhbyqxlas6kxfct6s5n7tv2gmopkxeh7u7uutpf6, bafy2bzacecdaop7tvkzs4zkgmgls5zuuu5ces4c5dwmhwpamnuihb6disz76k, ...]
    ├──4919581 (length: 4): [bafy2bzacebowxot7yenqzdxefjlvoj6lzcknsuv6anmwasoioxhod5t5jtw4a, bafy2bzacea55ffsfwql46juws3swb2idty774izkttt2nq7rx6ovfxpjh5x2k, ...]
    ├──4919582 (length: 7): [bafy2bzacebzfkgjobgrx7tezccpiu3qtnr54uycpx5navw4of3wbjctui5rii, bafy2bzaceafy7g3pcto7b3zalpz5funmlubbowqqihu7cbi5qstkpveaeac6o, ...]
    ├──4919583 (length: 8): [bafy2bzacec6mxoqvtipc7zeh2eqguul663lqwj5raqikfun7oc2kb6yk3z65s, bafy2bzaceb2sazh756oqsdct22or5ckhxg5ayw6glt3y3cdprhfqwssncwg4q, ...]
    ├──4919584 (length: 6): [bafy2bzacedthh4lgwlyl5l4j6y5abkvrnb5baufhhghcwjztf3zobxmhih4gy, bafy2bzaceaxk4soyxov7iiudb6xlnhcdasj65puwv5xc6ohsknpeiddbv4g7i, ...]
    ├──4919585 (length: 4): [bafy2bzacebyhwialpvjnjq3vffsdgmilvzrtprmh36nspxcfbh7igox77coxw, bafy2bzacealu7az46cicxuja4kejtfiboxztrjwkwibhudhxsheroppcw6ctq, ...]
    ├──4919586 (length: 3): [bafy2bzaceb6rgsvop4fm7c3qrfgnhtzc46h3qymie7jrf5efox4slpzblrwnk, bafy2bzacebi7wqczpw62unsuzyjvczw6ce6glzpvbzxjvoyglsevyldaaoj6m, ...]
    ├──4919587 (length: 6): [bafy2bzacebticsj5wcznan5wu6p6jwdz6dxxjjzn2ltohc5cnnpxbnukje2pi, bafy2bzacecnaggh7splsvnldew5odkfp72qb3vr2ud7czbrcxq7wkggrlppce, ...]
    ├──4919588 (length: 3): [bafy2bzaced6hupcodsdu4aulntqgwwsptkzw6iyu4ymoogzc7x66ngxmqud3u, bafy2bzacedzpqwh5nerlxw6e76ytovdjkkx6zphvs6ljg3tgfg5nu2lyogzva, ...]
    ├──4919589 (length: 8): [bafy2bzacebhlcn4dotvvo2hb5mgbenpyxwpozrcjddwqufifeo773ftkzkxt4, bafy2bzacebcg6bfygygm3cfx4jqfdhuf7kmigaq25lc7tusscw3hy37ll55xu, ...]
    └──...omitted the remaining 10 tipsets.
Signed by 959 miner(s).

Because of the head lookback of 10 the power table used by the first 10 instances of F3 are the same indicating the initial power table CID.

On arriving to this independently, it would take getting the power table at bootstrap epoch. and pruning the list to actors with power, then sort in ascending order of actor ID IIRC. You can use this function to compute the CID. The certs.go also has other utilities for validating a certificate chain, power diffs, etc.