Skip to content

Fix: use on-chain config in vault plugin - #19458

Merged
cedric-cordenier merged 4 commits into
developfrom
PRIV-135-fix-vault-config
Sep 23, 2025
Merged

cedric-cordenier merged 4 commits into
developfrom
PRIV-135-fix-vault-config

Conversation

@vreff

@vreff vreff commented Sep 22, 2025 •

Copy link
Copy Markdown
Contributor

Currently, the on-chain config used by the vault plugin is empty. This results in the number of encrypted decryption shares being produced always being 1 (since 2*0+1 = 1).

This PR uses the on-chain config to fix this.

@github-actions

Copy link
Copy Markdown
Contributor

I see you added a changeset file but it does not contain a tag. Please edit the text include at least one of the following tags:

  • #added For any new functionality added.
  • #breaking_change For any functionality that requires manual action for the node to boot.
  • #bugfix For bug fixes.
  • #changed For any change to the existing functionality.
  • #db_update For any feature that introduces updates to database schema.
  • #deprecation_notice For any upcoming deprecation functionality.
  • #internal For changesets that need to be excluded from the final changelog.
  • #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
  • #removed For any functionality/config that is removed.
  • #updated For any functionality that is updated.
  • #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

@cl-sonarqube-production

Copy link
Copy Markdown

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.

4 participants