feat: spartan/bootstrap.sh network_deploy #16639

just-mitch · 2025-08-28T17:38:46Z

Drop the effort to run local workflows via act and instead adopt the existing pattern of:

configure in github action
call bootstrap

You can now, e.g.:

./spartan/bootstrap.sh network_deploy scenario.internal.env
./spartan/bootstrap.sh single_test scenario.local.env spartan/smoke.test.ts

Add documentation in DEVELOP.md
Fix deployments after changes to json processing
nuke a bunch of unused github actions
write github action to do scenario network creation/tests and staging-public network creation

just-mitch · 2025-08-28T17:39:08Z

feat: spartan/bootstrap.sh network_deploy #16639 : 2 dependent PRs (#16648 , #16681 ) 👈 (View in Graphite)
feat: create test-network-scenarios.yml #16595
feat: create deploy-aztec-infra.yml #16580
feat: scaffold deploy-scenario-network.yml #16553
feat: create deploy-rollup-contracts.yml #16549
feat: deploy-eth-devnet.yml github action #16538
next

This stack of pull requests is managed by Graphite. Learn more about stacking.

just-mitch · 2025-08-28T17:56:12Z

spartan/scripts/install_deps.sh

This was persistently asking me for sudo when I was running locally.

just-mitch · 2025-08-31T21:26:39Z

.github/workflows/deploy-staging-networks.yml

+          NAMESPACE="v${{ github.event.client_payload.major_version }}-staging-public"
+          AZTEC_DOCKER_IMAGE="aztecprotocol/aztec:${{ github.event.client_payload.semver }}"
+          ETHEREUM_CHAIN_ID=11155111
+          ETHEREUM_RPC_URLS=${{ secrets.SEPOLIA_RPC_URLS }}


These secrets need to be set.

graphite-app · 2025-09-01T23:48:10Z

Merge activity

Sep 1, 11:48 PM UTC: This pull request can not be added to the Graphite merge queue. Please try rebasing and resubmitting to merge when ready.
Sep 1, 11:48 PM UTC: Graphite disabled "merge when ready" on this PR due to: a merge conflict with the target branch; resolve the conflict and try again..

spalladino

Approving since this is something we definitely want, but I'm worried about the complexity of configuration. If I managed to follow the flow correctly, what happens with a config value is:

Gets defined in an environments/scenario.env file
Gets loaded into scripts/deploy-network.sh (which has its set of defaults)
Gets written into a tfvars file for terraform to pick up
Gets picked up by terraform from a variables.tf file (which has its set of defaults)
Gets passed onto custom_settings for a helm release resource in a tf definition
Gets loaded into helm based on a values.yaml file (which has its set of defaults)
Gets injected as an env var from a template such as validator.yaml (or _pod-template.yaml?)
Gets loaded by the node (which has its set of defaults)

Also, it seems there are now duplicate configurations for slashing in helm. I added comments to point to them.

spalladino · 2025-09-02T17:38:51Z

yarn-project/end-to-end/src/spartan/DEVELOP.md

+
+```bash
+# run one
+./spartan/bootstrap.sh test_single scenario.local.env spartan/smoke.test.ts


Suggested change

./spartan/bootstrap.sh test_single scenario.local.env spartan/smoke.test.ts

./spartan/bootstrap.sh single_test scenario.local.env spartan/smoke.test.ts

spalladino · 2025-09-02T17:39:38Z

yarn-project/end-to-end/src/spartan/smoke.test.ts

+          return committee !== undefined;
+        },
+        'committee',
+        60 * 60, // wait up to 1 hour, since if the rollup was just deployed there will be no committee for 2 epochs


We should parameterize timeouts based on the rollup settings

spalladino · 2025-09-02T17:40:18Z

yarn-project/ethereum/src/deploy_l1_contracts.ts

        },
        {
-          gasLimit: 45_000_000n,
+          gasLimit: 32_000_000n,


Why this change?

Ah! Because I didn't realize the block gas limit was raised to 45M!

spalladino · 2025-09-02T17:45:18Z

spartan/aztec-node/values.yaml

+  slash:
+    minPenaltyPercentage: 0.5
+    maxPenaltyPercentage: 2.0
+    inactivityTargetPercentage: 0.7
+    inactivityPenalty: 0.0
+    prunePenalty: 0.0
+    dataWithholdingPenalty: 0.0
+    proposeInvalidAttestationsPenalty: 0.0
+    attestDescendantOfInvalidPenalty: 0.0
+    unknownPenalty: 0.0
+    invalidBlockPenalty: 0.0
+    offenseExpirationRounds: 8
+    maxPayloadSize: 50


I had set all slash to empty values, so we'd use the defaults defined in the node and we don't have multiple defaults floating around. Any reason for bringing them back?

aztec-packages/spartan/aztec-network/values.yaml

Lines 111 to 131 in 395632f

# All slashing settings are empty so we rely on the defaults set on ts-land

slash:

# Penalty percentages for slashing offenses

minPenaltyPercentage: ""

maxPenaltyPercentage: ""

# Validator allowlists/denylists

validatorsAlways: []

validatorsNever: []

# Penalty amounts for different offense types

prunePenalty: ""

dataWithholdingPenalty: ""

inactivityPenalty: ""

inactivityTargetPercentage: ""

invalidBlockPenalty: ""

proposeInvalidAttestationsPenalty: ""

attestDescendantOfInvalidPenalty: ""

unknownPenalty: ""

# Slasher behavior configuration

gracePeriodL2Slots: ""

offenseExpirationRounds: ""

maxPayloadSize: ""

Good call. Thanks.

spalladino · 2025-09-02T17:45:48Z

spartan/scripts/deploy_network.sh

+AZTEC_SLASHING_QUORUM=${AZTEC_SLASHING_QUORUM:-17}
+AZTEC_SLASHING_ROUND_SIZE=${AZTEC_SLASHING_ROUND_SIZE:-32}
+AZTEC_SLASHING_ROUND_SIZE_IN_EPOCHS=${AZTEC_SLASHING_ROUND_SIZE_IN_EPOCHS:-4}
+AZTEC_SLASHING_LIFETIME_IN_ROUNDS=${AZTEC_SLASHING_LIFETIME_IN_ROUNDS:-4}
+AZTEC_SLASHING_EXECUTION_DELAY_IN_ROUNDS=${AZTEC_SLASHING_EXECUTION_DELAY_IN_ROUNDS:-0}
+AZTEC_SLASHING_VETOER=${AZTEC_SLASHING_VETOER:-0x0000000000000000000000000000000000000000}
+AZTEC_SLASHING_OFFSET_IN_ROUNDS=${AZTEC_SLASHING_OFFSET_IN_ROUNDS:-2}
+AZTEC_SLASH_AMOUNT_SMALL=${AZTEC_SLASH_AMOUNT_SMALL:-10000000000000000000}
+AZTEC_SLASH_AMOUNT_MEDIUM=${AZTEC_SLASH_AMOUNT_MEDIUM:-20000000000000000000}
+AZTEC_SLASH_AMOUNT_LARGE=${AZTEC_SLASH_AMOUNT_LARGE:-50000000000000000000}
+AZTEC_SLASHER_FLAVOR=${AZTEC_SLASHER_FLAVOR:-tally}


Same comment as above on duplicate defaults

spalladino · 2025-09-02T17:46:40Z

spartan/scripts/deploy_network.sh

+cat > "${DEPLOY_ROLLUP_CONTRACTS_DIR}/terraform.tfvars" << EOF
+K8S_CLUSTER_CONTEXT = "${K8S_CLUSTER_CONTEXT}"
+NAMESPACE = "${NAMESPACE}"
+AZTEC_DOCKER_IMAGE = "${AZTEC_DOCKER_IMAGE}"
+L1_RPC_URLS = "${CSV_RPC_URLS}"
+MNEMONIC = "${LABS_INFRA_MNEMONIC}"
+L1_CHAIN_ID = "${ETHEREUM_CHAIN_ID}"
+SALT = "${SALT}"
+VALIDATORS = "${VALIDATOR_ADDRESSES}"
+SPONSORED_FPC = ${SPONSORED_FPC}
+REAL_VERIFIER = ${REAL_VERIFIER}
+AZTEC_SLOT_DURATION = ${AZTEC_SLOT_DURATION}
+AZTEC_EPOCH_DURATION = ${AZTEC_EPOCH_DURATION}
+AZTEC_TARGET_COMMITTEE_SIZE = ${AZTEC_TARGET_COMMITTEE_SIZE}
+AZTEC_PROOF_SUBMISSION_EPOCHS = ${AZTEC_PROOF_SUBMISSION_EPOCHS}
+AZTEC_ACTIVATION_THRESHOLD = ${AZTEC_ACTIVATION_THRESHOLD}
+AZTEC_EJECTION_THRESHOLD = ${AZTEC_EJECTION_THRESHOLD}
+AZTEC_SLASHING_QUORUM = ${AZTEC_SLASHING_QUORUM}
+AZTEC_SLASHING_ROUND_SIZE = ${AZTEC_SLASHING_ROUND_SIZE}
+AZTEC_SLASHING_ROUND_SIZE_IN_EPOCHS = ${AZTEC_SLASHING_ROUND_SIZE_IN_EPOCHS}
+AZTEC_SLASHING_LIFETIME_IN_ROUNDS = ${AZTEC_SLASHING_LIFETIME_IN_ROUNDS}
+AZTEC_SLASHING_EXECUTION_DELAY_IN_ROUNDS = ${AZTEC_SLASHING_EXECUTION_DELAY_IN_ROUNDS}
+AZTEC_SLASHING_VETOER = "${AZTEC_SLASHING_VETOER}"
+AZTEC_SLASHING_OFFSET_IN_ROUNDS = ${AZTEC_SLASHING_OFFSET_IN_ROUNDS}
+AZTEC_SLASH_AMOUNT_SMALL = ${AZTEC_SLASH_AMOUNT_SMALL}
+AZTEC_SLASH_AMOUNT_MEDIUM = ${AZTEC_SLASH_AMOUNT_MEDIUM}
+AZTEC_SLASH_AMOUNT_LARGE = ${AZTEC_SLASH_AMOUNT_LARGE}
+AZTEC_SLASHER_FLAVOR = "${AZTEC_SLASHER_FLAVOR}"
+AZTEC_GOVERNANCE_PROPOSER_QUORUM = ${AZTEC_GOVERNANCE_PROPOSER_QUORUM}
+AZTEC_GOVERNANCE_PROPOSER_ROUND_SIZE = ${AZTEC_GOVERNANCE_PROPOSER_ROUND_SIZE}
+AZTEC_MANA_TARGET = ${AZTEC_MANA_TARGET}
+AZTEC_PROVING_COST_PER_MANA = ${AZTEC_PROVING_COST_PER_MANA}
+JOB_NAME = "deploy-rollup-contracts"
+JOB_BACKOFF_LIMIT = 3
+JOB_TTL_SECONDS_AFTER_FINISHED = 3600
+EOF


Should we instead dump all aztec-related env vars here? We should be able to source the list of all vars from env-vars.ts.

Hm. I think we could. I guess there are a few outside env-vars.ts that we'd want to set.

spalladino · 2025-09-02T17:46:53Z

spartan/scripts/deploy_network.sh

+DEPLOY_AZTEC_INFRA_DIR="${SCRIPT_DIR}/../terraform/deploy-aztec-infra"
+"${SCRIPT_DIR}/override_terraform_backend.sh" "${DEPLOY_AZTEC_INFRA_DIR}" "${CLUSTER}" "${BASE_STATE_PATH}/deploy-aztec-infra/${SALT}"
+
+cat > "${DEPLOY_AZTEC_INFRA_DIR}/terraform.tfvars" << EOF


Same comment as above on dumping env vars

spalladino · 2025-09-02T17:47:45Z

spartan/terraform/deploy-aztec-infra/variables.tf

+variable "SLASH_MIN_PENALTY_PERCENTAGE" {
+  description = "The slash min penalty percentage"
+  type        = string
+  default     = 0.5
+}


Same comment as above on not duplicating default values

It's a great call. I'll remove all the defaults from terraform. No need to add layers here.

spalladino · 2025-09-02T17:55:25Z

spartan/aztec-node/templates/_pod-template.yaml

+        - name: SENTINEL_ENABLED
+          value: "{{ .Values.node.sentinel.enabled }}"
+        - name: SLASH_MIN_PENALTY_PERCENTAGE
+          value: "{{ .Values.node.slash.minPenaltyPercentage }}"
+        - name: SLASH_MAX_PENALTY_PERCENTAGE
+          value: "{{ .Values.node.slash.maxPenaltyPercentage }}"
+        - name: SLASH_INACTIVITY_TARGET_PERCENTAGE
+          value: "{{ .Values.node.slash.inactivityTargetPercentage }}"
+        - name: SLASH_INACTIVITY_PENALTY
+          value: "{{ .Values.node.slash.inactivityPenalty }}"
+        - name: SLASH_PRUNE_PENALTY
+          value: "{{ .Values.node.slash.prunePenalty }}"
+        - name: SLASH_DATA_WITHHOLDING_PENALTY
+          value: "{{ .Values.node.slash.dataWithholdingPenalty }}"
+        - name: SLASH_PROPOSE_INVALID_ATTESTATIONS_PENALTY
+          value: "{{ .Values.node.slash.proposeInvalidAttestationsPenalty }}"
+        - name: SLASH_ATTEST_DESCENDANT_OF_INVALID_PENALTY
+          value: "{{ .Values.node.slash.attestDescendantOfInvalidPenalty }}"
+        - name: SLASH_UNKNOWN_PENALTY
+          value: "{{ .Values.node.slash.unknownPenalty }}"
+        - name: SLASH_INVALID_BLOCK_PENALTY
+          value: "{{ .Values.node.slash.invalidBlockPenalty }}"
+        - name: SLASH_OFFENSE_EXPIRATION_ROUNDS
+          value: "{{ .Values.node.slash.offenseExpirationRounds }}"
+        - name: SLASH_MAX_PAYLOAD_SIZE
+          value: "{{ .Values.node.slash.maxPayloadSize }}"


I had injected these in the validator.yaml template, should we remove them from either of the two?

aztec-packages/spartan/aztec-network/templates/validator.yaml

Lines 194 to 253 in 395632f

{{- if .Values.aztec.slash.minPenaltyPercentage }}

- name: SLASH_MIN_PENALTY_PERCENTAGE

value: {{ .Values.aztec.slash.minPenaltyPercentage | quote }}

{{- end }}

{{- if .Values.aztec.slash.maxPenaltyPercentage }}

- name: SLASH_MAX_PENALTY_PERCENTAGE

value: {{ .Values.aztec.slash.maxPenaltyPercentage | quote }}

{{- end }}

{{- if .Values.aztec.slash.validatorsAlways }}

- name: SLASH_VALIDATORS_ALWAYS

value: {{ join "," .Values.aztec.slash.validatorsAlways | quote }}

{{- end }}

{{- if .Values.aztec.slash.validatorsNever }}

- name: SLASH_VALIDATORS_NEVER

value: {{ join "," .Values.aztec.slash.validatorsNever | quote }}

{{- end }}

{{- if .Values.aztec.slash.prunePenalty }}

- name: SLASH_PRUNE_PENALTY

value: {{ .Values.aztec.slash.prunePenalty | quote }}

{{- end }}

{{- if .Values.aztec.slash.dataWithholdingPenalty }}

- name: SLASH_DATA_WITHHOLDING_PENALTY

value: {{ .Values.aztec.slash.dataWithholdingPenalty | quote }}

{{- end }}

{{- if .Values.aztec.slash.inactivityPenalty }}

- name: SLASH_INACTIVITY_PENALTY

value: {{ .Values.aztec.slash.inactivityPenalty | quote }}

{{- end }}

{{- if .Values.aztec.slash.inactivityTargetPercentage }}

- name: SLASH_INACTIVITY_TARGET_PERCENTAGE

value: {{ .Values.aztec.slash.inactivityTargetPercentage | quote }}

{{- end }}

{{- if .Values.aztec.slash.invalidBlockPenalty }}

- name: SLASH_INVALID_BLOCK_PENALTY

value: {{ .Values.aztec.slash.invalidBlockPenalty | quote }}

{{- end }}

{{- if .Values.aztec.slash.proposeInvalidAttestationsPenalty }}

- name: SLASH_PROPOSE_INVALID_ATTESTATIONS_PENALTY

value: {{ .Values.aztec.slash.proposeInvalidAttestationsPenalty | quote }}

{{- end }}

{{- if .Values.aztec.slash.attestDescendantOfInvalidPenalty }}

- name: SLASH_ATTEST_DESCENDANT_OF_INVALID_PENALTY

value: {{ .Values.aztec.slash.attestDescendantOfInvalidPenalty | quote }}

{{- end }}

{{- if .Values.aztec.slash.unknownPenalty }}

- name: SLASH_UNKNOWN_PENALTY

value: {{ .Values.aztec.slash.unknownPenalty | quote }}

{{- end }}

{{- if .Values.aztec.slash.gracePeriodL2Slots }}

- name: SLASH_GRACE_PERIOD_L2_SLOTS

value: {{ .Values.aztec.slash.gracePeriodL2Slots | quote }}

{{- end }}

{{- if .Values.aztec.slash.offenseExpirationRounds }}

- name: SLASH_OFFENSE_EXPIRATION_ROUNDS

value: {{ .Values.aztec.slash.offenseExpirationRounds | quote }}

{{- end }}

{{- if .Values.aztec.slash.maxPayloadSize }}

- name: SLASH_MAX_PAYLOAD_SIZE

value: {{ .Values.aztec.slash.maxPayloadSize | quote }}

{{- end }}

Ah nice. I've used what you have. Very soon I think we will remove the aztec-network chart.

just-mitch · 2025-09-03T00:55:56Z

Approving since this is something we definitely want, but I'm worried about the complexity of configuration. If I managed to follow the flow correctly, what happens with a config value is:

Gets defined in an environments/scenario.env file

Gets loaded into scripts/deploy-network.sh (which has its set of defaults)

Gets written into a tfvars file for terraform to pick up

Gets picked up by terraform from a variables.tf file (which has its set of defaults)

Gets passed onto custom_settings for a helm release resource in a tf definition

Gets loaded into helm based on a values.yaml file (which has its set of defaults)

Gets injected as an env var from a template such as validator.yaml (or _pod-template.yaml?)

Gets loaded by the node (which has its set of defaults)

Also, it seems there are now duplicate configurations for slashing in helm. I added comments to point to them.

You're absolutely right in the current flow, and its unnecessary complexity. I removed the defaults out of deploy-network.sh, and the variables.tf, and the helm values yaml. Now if nothing is set, it just uses the default values in TS.

The flow you've described is still correct, but removing all the defaults makes it much easier to reason about.

This was referenced Aug 28, 2025

feat: deploy-eth-devnet.yml github action #16538

Merged

feat: create deploy-rollup-contracts.yml #16549

Merged

feat: scaffold deploy-scenario-network.yml #16553

Merged

feat: create deploy-aztec-infra.yml #16580

Merged

just-mitch mentioned this pull request Aug 28, 2025

feat: create test-network-scenarios.yml #16595

Merged

just-mitch changed the title ~~mitch/tmnt-225-create-guide-to-run-local-network-tests~~ chore: -create-guide-to-run-local-network-tests Aug 28, 2025

just-mitch changed the title ~~chore: -create-guide-to-run-local-network-tests~~ chore: create guide to run local network tests Aug 28, 2025

just-mitch marked this pull request as ready for review August 28, 2025 17:39

just-mitch requested a review from charlielye as a code owner August 28, 2025 17:39

just-mitch force-pushed the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch from 476ef9d to c43de5b Compare August 28, 2025 17:54

just-mitch commented Aug 28, 2025

View reviewed changes

spartan/scripts/install_deps.sh

Copy link

Collaborator Author

just-mitch Aug 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was persistently asking me for sudo when I was running locally.

just-mitch force-pushed the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch from c43de5b to fc886cb Compare August 28, 2025 18:40

just-mitch force-pushed the 08-26-mitch_tmnt-168-create-test-network-scenariosyml branch 2 times, most recently from a2635c3 to ccd7efa Compare August 29, 2025 00:54

just-mitch force-pushed the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch from fc886cb to b33289f Compare August 29, 2025 00:54

just-mitch mentioned this pull request Aug 29, 2025

refactor: bootstrap network workflows #16648

Merged

just-mitch force-pushed the 08-26-mitch_tmnt-168-create-test-network-scenariosyml branch from ccd7efa to 886fc52 Compare August 29, 2025 01:06

just-mitch force-pushed the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch 2 times, most recently from 0e62e56 to 1554f42 Compare August 29, 2025 10:31

just-mitch force-pushed the 08-26-mitch_tmnt-168-create-test-network-scenariosyml branch from 886fc52 to 8a36504 Compare August 29, 2025 10:31

Base automatically changed from 08-26-mitch_tmnt-168-create-test-network-scenariosyml to next August 29, 2025 11:34

just-mitch force-pushed the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch 2 times, most recently from 66a34d9 to eab9c8a Compare August 29, 2025 12:21

just-mitch enabled auto-merge August 29, 2025 12:24

just-mitch force-pushed the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch from eab9c8a to d28ea7b Compare August 30, 2025 16:39

just-mitch changed the title ~~chore: create guide to run local network tests~~ feat: spartan/bootstrap.sh network_deploy Aug 31, 2025

just-mitch force-pushed the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch from c54ea41 to af1d837 Compare August 31, 2025 17:18

just-mitch commented Aug 31, 2025

View reviewed changes

just-mitch mentioned this pull request Aug 31, 2025

feat: add release automation for v2 packages #16681

Merged

just-mitch force-pushed the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch 2 times, most recently from bb1295e to 09b9452 Compare September 2, 2025 16:33

spalladino approved these changes Sep 2, 2025

View reviewed changes

just-mitch added this pull request to the merge queue Sep 2, 2025

just-mitch removed this pull request from the merge queue due to a manual request Sep 2, 2025

just-mitch force-pushed the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch from 09b9452 to 3714c57 Compare September 3, 2025 00:50

just-mitch enabled auto-merge September 3, 2025 00:56

just-mitch force-pushed the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch from 3714c57 to 0232f6a Compare September 3, 2025 02:38

just-mitch disabled auto-merge September 3, 2025 02:43

just-mitch requested a review from spalladino September 3, 2025 02:43

just-mitch enabled auto-merge September 3, 2025 02:43

just-mitch force-pushed the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch from 0232f6a to e0433ce Compare September 3, 2025 02:55

feat: spartan/bootstrap.sh network_deploy

97d52ef

just-mitch force-pushed the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch from e0433ce to 97d52ef Compare September 3, 2025 03:18

just-mitch added this pull request to the merge queue Sep 3, 2025

Merged via the queue into next with commit b52194c Sep 3, 2025
15 checks passed

just-mitch deleted the 08-28-mitch_tmnt-225-create-guide-to-run-local-network-tests branch September 3, 2025 04:20

ludamad pushed a commit that referenced this pull request Dec 16, 2025

feat: spartan/bootstrap.sh network_deploy (#16639)

b322a7a

	./spartan/bootstrap.sh test_single scenario.local.env spartan/smoke.test.ts
	./spartan/bootstrap.sh single_test scenario.local.env spartan/smoke.test.ts

	# All slashing settings are empty so we rely on the defaults set on ts-land
	slash:
	# Penalty percentages for slashing offenses
	minPenaltyPercentage: ""
	maxPenaltyPercentage: ""
	# Validator allowlists/denylists
	validatorsAlways: []
	validatorsNever: []
	# Penalty amounts for different offense types
	prunePenalty: ""
	dataWithholdingPenalty: ""
	inactivityPenalty: ""
	inactivityTargetPercentage: ""
	invalidBlockPenalty: ""
	proposeInvalidAttestationsPenalty: ""
	attestDescendantOfInvalidPenalty: ""
	unknownPenalty: ""
	# Slasher behavior configuration
	gracePeriodL2Slots: ""
	offenseExpirationRounds: ""
	maxPayloadSize: ""

	{{- if .Values.aztec.slash.minPenaltyPercentage }}
	- name: SLASH_MIN_PENALTY_PERCENTAGE
	value: {{ .Values.aztec.slash.minPenaltyPercentage \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.maxPenaltyPercentage }}
	- name: SLASH_MAX_PENALTY_PERCENTAGE
	value: {{ .Values.aztec.slash.maxPenaltyPercentage \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.validatorsAlways }}
	- name: SLASH_VALIDATORS_ALWAYS
	value: {{ join "," .Values.aztec.slash.validatorsAlways \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.validatorsNever }}
	- name: SLASH_VALIDATORS_NEVER
	value: {{ join "," .Values.aztec.slash.validatorsNever \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.prunePenalty }}
	- name: SLASH_PRUNE_PENALTY
	value: {{ .Values.aztec.slash.prunePenalty \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.dataWithholdingPenalty }}
	- name: SLASH_DATA_WITHHOLDING_PENALTY
	value: {{ .Values.aztec.slash.dataWithholdingPenalty \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.inactivityPenalty }}
	- name: SLASH_INACTIVITY_PENALTY
	value: {{ .Values.aztec.slash.inactivityPenalty \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.inactivityTargetPercentage }}
	- name: SLASH_INACTIVITY_TARGET_PERCENTAGE
	value: {{ .Values.aztec.slash.inactivityTargetPercentage \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.invalidBlockPenalty }}
	- name: SLASH_INVALID_BLOCK_PENALTY
	value: {{ .Values.aztec.slash.invalidBlockPenalty \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.proposeInvalidAttestationsPenalty }}
	- name: SLASH_PROPOSE_INVALID_ATTESTATIONS_PENALTY
	value: {{ .Values.aztec.slash.proposeInvalidAttestationsPenalty \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.attestDescendantOfInvalidPenalty }}
	- name: SLASH_ATTEST_DESCENDANT_OF_INVALID_PENALTY
	value: {{ .Values.aztec.slash.attestDescendantOfInvalidPenalty \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.unknownPenalty }}
	- name: SLASH_UNKNOWN_PENALTY
	value: {{ .Values.aztec.slash.unknownPenalty \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.gracePeriodL2Slots }}
	- name: SLASH_GRACE_PERIOD_L2_SLOTS
	value: {{ .Values.aztec.slash.gracePeriodL2Slots \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.offenseExpirationRounds }}
	- name: SLASH_OFFENSE_EXPIRATION_ROUNDS
	value: {{ .Values.aztec.slash.offenseExpirationRounds \| quote }}
	{{- end }}
	{{- if .Values.aztec.slash.maxPayloadSize }}
	- name: SLASH_MAX_PAYLOAD_SIZE
	value: {{ .Values.aztec.slash.maxPayloadSize \| quote }}
	{{- end }}

feat: spartan/bootstrap.sh network_deploy #16639

feat: spartan/bootstrap.sh network_deploy #16639

Uh oh!

Conversation

just-mitch commented Aug 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

just-mitch commented Aug 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

graphite-app bot commented Sep 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merge activity

Uh oh!

spalladino left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

just-mitch commented Sep 3, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

just-mitch commented Aug 28, 2025 •

edited

Loading

just-mitch commented Aug 28, 2025 •

edited

Loading

graphite-app bot commented Sep 1, 2025 •

edited

Loading

spalladino left a comment •

edited

Loading