security: add registrant signature verification to ValidateIdentityRequest#7
Merged
cyberstorm-daemon merged 3 commits intomainfrom Sep 15, 2025
Merged
security: add registrant signature verification to ValidateIdentityRequest#7cyberstorm-daemon merged 3 commits intomainfrom
cyberstorm-daemon merged 3 commits intomainfrom
Conversation
- Add registrant_signature field to prove registrant controls claimed address - Prevents impersonation attacks where someone claims another's address - Enables cryptographic verification of registrant authorization - Critical security fix for identity validation flow
cyberstorm-daemon
force-pushed
the
fix/chain-id
branch
from
8ea67cb to
f2007d2
Compare
Configure grpc-ecosystem/openapiv2 plugin with json_names_for_fields=false to generate OpenAPI schemas using snake_case field names instead of camelCase. This eliminates the need for field name marshaling overhead in downstream services. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
…ation - Replace separate publish.yml and release.yml with single release-and-publish.yml - Add comprehensive version validation across pyproject.toml, package.json, package-lock.json - Implement bare version input (1.0.5) with automatic 'v' prefix for Git tags - Create progressive workflow: Release → TestPyPI → PyPI with proper dependencies - Preserve optional TestPyPI and PyPI publishing checkboxes - Update README with clear release process documentation
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
1 participant
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
Adds critical security verification to the identity validation process by requiring cryptographic proof of address ownership.
Changes
Security Issue Resolved
Problem: The previous had no mechanism to verify that the claimed address was actually controlled by the requester. This created a vulnerability where:
Solution: The field now requires the requester to provide a cryptographic signature that proves they control the private key associated with the claimed address.
Technical Implementation
Security Benefits
Backward Compatibility
Version Impact
This security enhancement is part of the v1.0.4 release.