Configure initial delegation

[novalis]

Should wait for https://gitlab.com/tezos/tezos/-/merge_requests/5071 to merge.

[nicolasochem]

I tried this by:

• generating a chain with mkchain with 2 bakers
• removing one of the bakers and renaming its key to baker-0-delegate
• merging the lb_toggle branch
• importing the genesis parameters from dailynet
• setting the boot protocol to alpha
• building a custom image of octez based on MR5071
• setting delegate_to in the account as follows:

  baker-0-delegator:                                                                                                                                                                 
    bootstrap_balance: '4000000000000'                                                                                                                                               
    is_bootstrap_baker_account: false                                                                                                                                                
    key: edsk3H2d19nzQMxgSAmybcCpEkC2a4vFuZ2MF1xXJscQWtuHpW4PD2                                                                                                                      
    type: secret                                                                                                                                                                     
    delegate_to: baker-0                          

Then looking at activation logs:

          │         "bootstrap_delegations": [                                                                                                                                                │
│             {                                                                                                                                                                     │
│                 "from_pkh": "tz1erGynP5PAP5WJbnvYi8Ho4XsRYS3Ti4gn",                                                                                                               │
│                 "to_pkh": "tz1VuV7MYyJgVmdWywarAeUa6JQicZriAbvP"                                                                                                                  │
│             }                                                                                                                                                                     │
│         ]        

which is expected.

But then I opened a shell to the node and I didn't see what I was expecting:

 ~ $ tezos-client list known addresses
baker-0: tz1VuV7MYyJgVmdWywarAeUa6JQicZriAbvP (http sk known)
baker-0-delegator: tz1erGynP5PAP5WJbnvYi8Ho4XsRYS3Ti4gn (pk known)
~ $ tezos-client get delegate for baker-0
tz1VuV7MYyJgVmdWywarAeUa6JQicZriAbvP (known as baker-0)
~ $ tezos-client get delegate for baker-0-delegator
none

What did I get wrong? Here is my complete values.yaml

Also I think we should document this feature in the values.yaml comments (as we do for all features).

[novalis]

Are you using the Alpha protocol, or the default (Ithaca)? Of course the new feature only works on Alpha. But also in order to use alpha, a bunch of new configs have to be added. On April 22, 2022 5:21:29 PM EDT, Nicolas Ochem ***@***.***> wrote: ***@***.*** requested changes on this pull request.

…

I tried this by: * generating a chain with mkchain with 2 bakers * removing one of the baker and renamin its key to baker-0-delegate * merging the `lb_toggle` branch * importing the genesis parameters from dailynet * setting the boot protocol to alpha * building a custom image of cotez based on [MR5071](https://gitlab.com/tezos/tezos/-/merge_requests/5071) * setting `delegate_to` in the account as follows: ``` baker-0-delegator: > bootstrap_balance: '4000000000000' > is_bootstrap_baker_account: false > key: edsk3H2d19nzQMxgSAmybcCpEkC2a4vFuZ2MF1xXJscQWtuHpW4PD2 > type: secret > delegate_to: baker-0 > ``` Then looking at activation logs: ``` │ "bootstrap_delegations": [ │ │ { │ │ "from_pkh": "tz1erGynP5PAP5WJbnvYi8Ho4XsRYS3Ti4gn", │ │ "to_pkh": "tz1VuV7MYyJgVmdWywarAeUa6JQicZriAbvP" │ │ } │ │ ] > ``` which is expected. But then I opened a shell to the node and I didn't see what I was expecting: ``` ~ $ tezos-client list known addresses baker-0: tz1VuV7MYyJgVmdWywarAeUa6JQicZriAbvP (http sk known) baker-0-delegator: tz1erGynP5PAP5WJbnvYi8Ho4XsRYS3Ti4gn (pk known) ~ $ tezos-client get delegate for baker-0 tz1VuV7MYyJgVmdWywarAeUa6JQicZriAbvP (known as baker-0) ~ $ tezos-client get delegate for baker-0-delegator none ``` What did I get wrong? [Here](https://gist.github.com/nicolasochem/30893d54f9d14e337a18179fc66ec682) is my complete values.yaml Also I think we should document this feature in the values.yaml comments (as we do for all features). -- > Reply to this email directly or view it on GitHub: #429 (review) You are receiving this because you authored the thread. Message ID: ***@***.***>

[nicolasochem]

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

[novalis]

dmttest_values.txt

My values file, which does work

[nicolasochem]

It works now with the latest pushes on MR5071.

[novalis]

Upstream MR is now merged

[nicolasochem]

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 it's no longer the case. Instead, I am seeing:

│             [                                                                                                                                                                     │
│                 "tz1cP2pmkWKDcgefqdjPrRbhbk5jRWc3Rttj",                                                                                                                           │
│                 "4000000000000",                                                                                                                                                  │
│                 "tz1gwzp3DKDWgfjGnxfMGTmjqnuysXuGBzKv"                                                                                                                            │
│             ]                              

This was apparently changed during one force-push: https://github.com/oxheadalpha/tezos-k8s/compare/38b7dfc8a8e3a5ed758e58af1222bb963ff6d3c5..7efaa2209acf94f30609319d385d53426de25c82#diff-1a28c90349a94d90b197e351f0a82a1ed3f70207ebcaaa2ecff3f57b1089831aL503

Was it accidental? Or are we in the process of changing the syntax in parameters.json?

[novalis]

Yes, we changed the syntax. The new syntax works for me.

[nicolasochem]

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 array with the third element being set to the correct hash:

│             [                                                                                                                                                                     │
│                 "tz1eawTP2ueRCqsYZq3DebwW9PkthdCqcZa8",                                                                                                                           │
│                 "4000000000000",                                                                                                                                                  │
│                 "tz1WrZpjVRpsmjv8VL3781RhyLi5JyHsGXK2"                                                                                                                            │
│             ]                                    

However I don't see the delegation:

~ $ tezos-client list known addresses
Warning:
  
                 This is NOT the Tezos Mainnet.
  
           Do NOT use your fundraiser keys on this network.

baker: tz1WrZpjVRpsmjv8VL3781RhyLi5JyHsGXK2 (http sk known)
delegator: tz1eawTP2ueRCqsYZq3DebwW9PkthdCqcZa8 (pk known)
~ $ tezos-client get delegate for delegator
Warning:
  
                 This is NOT the Tezos Mainnet.
  
           Do NOT use your fundraiser keys on this network.

none

Last time I checked prior to merge it was working. Here is my values.yaml (you may have to modify the utils container to match what you built locally):

david_values.yaml.txt

[novalis]

Aargh, I'm seeing this too, and I have no idea why. Will investigate.