The problem TxShield solves

Web3 users routinely approve wallet transactions without understanding what they're signing. Raw hex calldata is unreadable to most people, making it trivially easy for malicious dApps to trick users into approving unlimited token allowances, draining funds, or interacting with dangerous contracts.

TxShield solves this by acting as a security layer before the wallet popup appears. It intercepts every Ethereum signing request, decodes the raw calldata into plain English, resolves ENS names, scores the transaction risk on a 0–100 scale, and displays AI-generated safety warnings giving users the information they need to make an informed decision before any funds leave their wallet.

Key capabilities:

• Pre-wallet transaction interception via window.ethereum proxy (Manifest V3)
• Hex calldata decoding with ABI parameter extraction
• ENS name resolution with reverse-record verification to prevent spoofing
• Risk scoring engine: LOW / MEDIUM / HIGH / CRITICAL with weighted factors
• AI-generated plain-English explanations and safety recommendations (AWS Bedrock, Claude 3 Haiku)
• On-chain verified contract registry on Base Sepolia
• Multi-wallet support (MetaMask, Rabby, Phantom) via EIP-6963
• Decentralized transaction history via Fileverse
• Multi-language support (EN, HI, MR, TA, TE, BN)

Designed for Web3 users who interact with dApps and may not understand unlimited token approvals, contract interactions, or raw calldata giving them transparency and safety before they approve.

Challenges we ran into

Multilingual Support : We faced issues implementing multilingual support and to maintain its accuracy overall with graceful fallbacks using claude haiku 4.5.

API Call Timing : Initially the API calling used to take 12-15secs , to reduce its latency we used parallel chunked API calling.

UX : To keep the user experience very beginner friendly and self explanatory.

no more issues cuz we goated