Nicolas Ochem

I am using alpha. On ithaca, it (predictably) refuses to bootstrap the chain because of an unknown param `bootstrap_delegations`.

It works now with the latest pushes on MR5071.

I tried again with a recent master branch build and it does not work anymore. Based on my previous comments, I expect to see `bootstrap_delegations` in my activation parameters, but...

I can't make it work with a recent container from master branch: https://hub.docker.com/layers/tezos/tezos/tezos/master_2c2c093b_20220525220334/images/sha256-3ee6dbff99a260a9b85bf642b2dfa033ef927fec6f8c4fcfbf10aacb01f70c45?context=explore I am using proto alpha. I checkeded in the activation job log that the parameters contain the...

Another thought: this change restricts usage of snapshots to "known" chains which are hardcoded in octez (mainnet, jakartanet). If someone wants to use tezos-k8s to create a totally private chain...

@harryttd oh yes, it does. I guess it needs to be documented?

@elric1 let's wrap this up? We need to add ghostnet support. Additionally, this will enable a one-liner helm in the new [doc website](https://news.tezoscommons.org/double-baking-and-remote-signers-639bf8ef7e65): a single line of helm to install...

replaced by #525

These are not trusted peers, these are links between 2 nodes. We already have `nodes`, what's wrong with `links`? What's not obvious about it?

I agree with replacing the fqdns with just the hostnames. Also replacing `links` with `peering_links` is fine. I think defining links separately from nodes is cleaner. I briefly searched for...