Skip to content

chore(deps): bump sei-config to v0.0.13#181

Merged
bdchatham merged 1 commit intomainfrom
chore/bump-sei-config-v0.0.13
May 5, 2026
Merged

chore(deps): bump sei-config to v0.0.13#181
bdchatham merged 1 commit intomainfrom
chore/bump-sei-config-v0.0.13

Conversation

@bdchatham
Copy link
Copy Markdown
Collaborator

Summary

Picks up sei-config v0.0.13, which adds the new [receipt-store] config section and archive zero-pruning defaults (sei-protocol/sei-config#11).

What this enables

When the controller's sidecar emits app.toml for archive SeiNode resources, it now writes:

[receipt-store]
backend = "pebbledb"
db-directory = ""
async-write-buffer = 100
keep-recent = 0
prune-interval-seconds = 0
tx-index-backend = "pebbledb"

The retention semantics are documented in sei-config#11 — min-retain-blocks=0 is the load-bearing knob on post-#3237 sei-chain; the receipt-store keys are emitted to self-document intent.

Note: this PR alone does not change runtime behavior — the controller's sidecar image pin (internal/platform/platform.go) still points at a pre-#3237 seictl/seid build. A subsequent sidecar bump is needed to pick up post-#3237 sei-chain semantics where min-retain-blocks becomes the only load-bearing knob.

Test plan

  • Hand-edited go.mod / go.sum to v0.0.13 (avoiding go mod tidy cleanup of workspace-induced indirect deps; keeps the diff to 3 lines)
  • GOWORK=off go build ./... clean
  • GOWORK=off go test ./... clean across node, nodedeployment, noderesource, planner, task

🤖 Generated with Claude Code

Picks up the new [receipt-store] config section and archive zero-pruning
defaults landed in sei-config#11. No reconcile-loop changes needed —
the receipt-store fields land via baseDefaults and applyArchiveOverrides;
existing controller config emission paths consume the unified SeiConfig
unchanged.
@bdchatham bdchatham merged commit 536f69e into main May 5, 2026
2 checks passed
bdchatham added a commit that referenced this pull request May 6, 2026
Pulls in PR #185 — reverts the fork-genesis pipeline (#169, #170,
#173, #174, #179, #183) after research surfaced two chain-won't-start
blockers in the cosmos-sdk export/init round-trip (F1 bonded-pool
retention, F2 sei-cosmos streaming exit-code) that can't be resolved
in the near term. Also picks up #177 (.status.endpoints), #181
(sei-config v0.0.13).

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant