chore: Setup helm config for alpha testnet#12997
Conversation
| const testAccounts = nodeConfig.testAccounts ? (await getInitialTestAccounts()).map(a => a.address) : []; | ||
| const sponsoredFPCAccounts = nodeConfig.sponsoredFPC ? [await getSponsoredFPCAddress()] : []; | ||
| const initialFundedAccounts = [...testAccounts, ...sponsoredFPCAccounts]; | ||
| const initialFundedAccounts = testAccounts.concat(sponsoredFPCAccounts); |
There was a problem hiding this comment.
I was paranoid that I hadn't used the same concat method used when creating the genesis state in the cli deployment of L1 contracts.
| l1GasPriceMax: 1000 | ||
| resources: | ||
| requests: | ||
| cpu: "3" |
There was a problem hiding this comment.
3 cores so we use the new 4 core pool. Leaves a core for K8s/Google usage
There was a problem hiding this comment.
Also 10Gi memory. These have 16GB available but K8s bloat takes some.
There was a problem hiding this comment.
Does Node's
max-old-space-sizeget set as part of the parent values file?
Nope, good call. Will add
| l1GasPriceMax: 1000 | ||
| sequencer: | ||
| minTxsPerBlock: 0 | ||
| maxTxsPerBlock: 4 |
There was a problem hiding this comment.
4 txs per block (0.1 TPS)
| memory: "10Gi" | ||
|
|
||
| proverAgent: | ||
| replicas: 32 |
There was a problem hiding this comment.
32 x 32 core spot provers (-1 core for K8s)
| aztec: | ||
| realProofs: true | ||
| numberOfDefaultAccounts: 0 | ||
| testAccounts: true |
There was a problem hiding this comment.
testAccounts and sponsoredFPC both true
| sponsoredFPC: true | ||
| bootstrapENRs: "enr:-LO4QLbJddVpePYjaiCftOBY-L7O6Mfj_43TAn5Q1Y-5qQ_OWmSFc7bTKWHzw5xmdVIqXUiizum_kIRniXdPnWHHcwEEhWF6dGVjqDAwLTExMTU1MTExLTAwMDAwMDAwLTAtMTgwNmEwMjgtMWE1MzBmM2KCaWSCdjSCaXCEI8nh9YlzZWNwMjU2azGhA-_dX6aFcXP1DLk91negbXL2a0mNYGXH4hrMvb2i92I0g3VkcIKd0A,enr:-LO4QN4WF8kFyV3sQVX0C_y_03Eepxk5Wac70l9QJcIDRYwKS6aRst1YcfbTDdvovXdRfKf-WSXNVWViGLhDA-dUz2MEhWF6dGVjqDAwLTExMTU1MTExLTAwMDAwMDAwLTAtMTgwNmEwMjgtMWE1MzBmM2KCaWSCdjSCaXCEIicTHolzZWNwMjU2azGhAsz7aFFYRnP5xjTux5UW-HyEQcW_EJrZMT1CNm79N4g-g3VkcIKd0A,enr:-LO4QFrGfkRaCk_iFTeUjR5ESwo45Eov9hx_T1-BLdoT-iHzFgCiHMT4V1KBtdFp8D0ajLSe5HcNYrhalmdJXgv6NTUEhWF6dGVjqDAwLTExMTU1MTExLTAwMDAwMDAwLTAtMTgwNmEwMjgtMWE1MzBmM2KCaWSCdjSCaXCEIlICt4lzZWNwMjU2azGhAlC6nKB3iDtRFqWKWqxf_t-P9hc-SZ6VFBJV4y3bTZBQg3VkcIKd0A" | ||
| contracts: | ||
| registryAddress: "0x290667b79dd73ce03cd2fc901b905e7f1b001d18" |
There was a problem hiding this comment.
Alpha testnet contracts and bootnodes
|
|
||
| l1Salt: "" # leave empty for random salt | ||
| testAccounts: true | ||
| sponsoredFPC: false |
There was a problem hiding this comment.
Is it ok for this value to be false here?
There was a problem hiding this comment.
Hmm, well it depends on what the default behaviour of this is in the cli. I haven't updated our L1 contract deployment process to specify --sponsored-fpc so I would hope this would mean it would default to false.
There was a problem hiding this comment.
Same default as testAccounts, I specified them the same:
There was a problem hiding this comment.
I assume that's false. It's not exactly clear
There was a problem hiding this comment.
Yes, it defaults to false (checked commander.js docs)
|
|
||
| network: | ||
| public: true | ||
| setupL2Contracts: false |
There was a problem hiding this comment.
Did the fee juice contract get initialized out of band?
There was a problem hiding this comment.
I don't think we want the helm deployment setting up the L2 contracts. The genesist state has been setup to fund the FPC, we just need to deploy the contract. But I was going to that once I see the network is up and runing producing empty blocks.
| l1GasPriceMax: 1000 | ||
| resources: | ||
| requests: | ||
| cpu: "3" |
There was a problem hiding this comment.
Does Node's
max-old-space-sizeget set as part of the parent values file?
Nope, good call. Will add
3 participants
This PR sets up helm config for alpha-testnet in K8s. It also moves the tf state to GCS