feat(config): wire --bzz-token-address through bee config#592
Merged
Conversation
martinconic
requested review from
acud,
akrem-chabchoub,
gacevicljubisa,
janos and
sbackend123
…590) Bumps [github.com/go-git/go-git/v5](https://github.com/go-git/go-git) from 5.19.0 to 5.19.1. - [Release notes](https://github.com/go-git/go-git/releases) - [Changelog](https://github.com/go-git/go-git/blob/main/HISTORY.md) - [Commits](go-git/go-git@v5.19.0...v5.19.1) --- updated-dependencies: - dependency-name: github.com/go-git/go-git/v5 dependency-version: 5.19.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
martinconic
force-pushed
the
feat/bzz-token-address
branch
from
eef2389 to
6d6ea64
Compare
akrem-chabchoub
approved these changes
May 28, 2026
gacevicljubisa
approved these changes
Jun 6, 2026
gacevicljubisa
left a comment
gacevicljubisa
left a comment
Member
There was a problem hiding this comment.
Changes are ok, merge if ethersphere/bee#5476 is merged
martinconic
force-pushed
the
feat/bzz-token-address
branch
from
1bebf56 to
f5743f0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bee PR #5476 (refactor: add BzzAddress to ChainConfig) makes the BZZ token address strict: known networks resolve it from the static config, unknown networks must supply --bzz-token-address. The local CI chain is neither mainnet nor testnet, so bee refuses to start without it.
Add BzzTokenAddress to orchestration.Config / BeeConfig, render it in the k8s template, and set the bee-localchain BZZ token address in the local-chain cluster configs (already used by beekeeper itself in beekeeper-local.yaml). Bee versions without #5476 ignore the new key (viper silently drops unknown keys), so this lands safely ahead of the bee merge.