Merged
Conversation
- createProofTransfer: creates DB entry with UUID - uploadProof: uploads proof from authenticator - fetchProof: polls for proof by UUID - Type-safe BigInt serialization/deserialization - Error handling with descriptive messages
- Include optional transferId in QR data - Enables online proof transfer alongside QR method - Backward compatible with existing QR-only flow
- Extract transferId from scanned QR data - Pass transferId to transaction request handler - Supports both online and offline proof methods
- Detect transferId in scanned transaction requests - Automatically upload proof after generation - Show upload status and success messages - Maintain QR code display for offline method - Update button labels based on transfer method
- Add 'Online Proof' and 'QR Code' button options - Generate UUID and create DB entry for online method - Implement 2-second polling for proof retrieval - Auto-execute transaction when proof received - Show different UI states for each method - Maintain backward compatibility with QR flow
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 16103040 | Triggered | Generic Password | 1636505 | .github/workflows/ci.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
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.
No description provided.