-
Notifications
You must be signed in to change notification settings - Fork 21
Redact Private Key from CreateWallet API Response #521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Sankara-Jefferson
wants to merge
43
commits into
main
Choose a base branch
from
pr-517
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
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
Co-authored-by: web3-bot <[email protected]>
There seem to have been some manual releases which leaves version file inconsistent with what the latest release is.
This is the version for MVP milestone
New version includes retrieval optimization.
- update go-libp2p to v0.39.1 - enable HTTP(S)_PROXY and TCP_PROXY
- Add init function to create full current schema on brand new clean databases and run missing migrations on any databases using old auto-migrate strategy with existing data. - Add CLI commands to migrate up, down, or to a specified version by ID - Add utility functions to get list of migration IDs ran on current database, check if migration has run by ID, etc.
Fix struct tag ordering in handler/storage/types_gen.go to match the current code generator output. This resolves CI failures where go generate was detecting differences between committed and generated files.
Merging this now — all tests have passed.
ianconsolata
approved these changes
Jul 29, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, though it seems like there are some merge conflicts to resolve
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR redacts the
PrivateKey
field from the response of the/wallet/create
API endpoint to prevent accidental key exposure.What Was Done
CreateHandler
: removedPrivateKey
from response payload by explicitly clearing the field before return.CreateWallet_privateKeyShouldBeRedacted
to assert thatPrivateKey
is empty in the response.go test ./api -v
.Rationale
Previously, the
PrivateKey
was included in plaintext in API responses. While this endpoint is useful for testing, returning secrets by default is a major security risk. This patch minimizes attack surface and sets groundwork for further key safety improvements.Follow-ups (to be tracked)
wallet export
)Status
Ready for merge after CI passes.