C1: Demote sensitive data logs from Information to Debug#910
Merged
Conversation
Prevent sensitive data (private keys, public keys, transaction hex, WitScript content, recovery keys) from appearing in production logs. All LogInformation calls that included cryptographic material or transaction data are demoted to LogDebug with structured message templates that exclude sensitive values. Files: FounderTransactionActions, InvestorTransactionActions, SeederTransactionActions, DerivationOperations
dangershony
approved these changes
Jul 4, 2026
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
2 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.
Summary
Demote all sensitive data logs from
LogInformationtoLogDebugto prevent cryptographic material from appearing in production log output.Changes
What was exposed before
Testing
All 154 shared tests pass.