Update shield wordings#2953
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
AyushBherwani1998
approved these changes
Jun 9, 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.
Update shield according to marketing wordings
Note
Low Risk
Documentation and Cursor rules only; no product code or runtime behavior changes.
Overview
Aligns Agent Wallet docs with updated marketing terminology by separating threat scanning from Transaction Shield and Transaction Protection.
The onchain security pipeline step that was labeled Transaction Shield / “security checks” is now threat scanning (Blockaid, auto-bounce for malicious txs, approval for flagged ones). Transaction Protection is described as optional loss coverage (up to $10,000/month for eligible safe txs), not a scanning feature. Transaction Shield is reframed as the MetaMask subscription that bundles Transaction Protection with priority support—not as threat scanning.
Trading modes (Guard/Beast) and the server-wallet async flow now refer to threat scanning instead of “security check.” The same definitions are added to
.cursor/rules/product-agent-wallet.mdcfor consistent future authoring.Reviewed by Cursor Bugbot for commit 79d0bf0. Bugbot is set up for automated code reviews on this repo. Configure here.