Smart contracts are blind to who calls them. When a user interacts directly with your smart contract (via Etherscan, a script, or any Web3 wallet), they bypass your frontend entirely, and any fraud detection you've implemented there.
This creates vulnerabilities in:
NFT marketplaces: Wash trading, bot sniping during drops, Sybil attacks for airdrops
DeFi platforms: Multi-account farming, bot-driven arbitrage abuse, reward exploitation
Token sales: Bot purchases, unfair distribution, automated sniping
Web3 gaming: Multi-accounting, automated gameplay, reward farming
DAOs: Sybil attacks on voting, proposal spam, governance manipulation
The Solution: Signature-Based Verification
GuardianStack acts as an identity oracle for your smart contracts. Here's how it works:
User interacts with your frontend
GuardianStack verifies they're a real human (not a bot/script)
Your backend checks the Guardian event and generates a cryptographic signature
User's wallet submits the transaction with the signature
Your smart contract validates the signature before executing
Result: Even if someone calls your contract directly, the transaction fails without a valid Guardian signature.
Implementation Guide
Step 1: Frontend - Collect Guardian Event
Install the Guardian SDK:
Initialize Guardian and get the requestId:
Step 2: Backend - Verify & Generate Signature
Install the Guardian Server SDK:
Create an endpoint that verifies the Guardian event and returns a signature:
Step 3: Frontend - Request Signature & Submit Transaction
Step 4: Smart Contract - Verify Signature
Use Case Examples
NFT Marketplace - Prevent Wash Trading
Problem: Users create multiple wallets to trade with themselves and inflate prices.
Solution: Link all transactions to Guardian's visitorId (persistent device fingerprint).
DeFi - Prevent Reward Farming
Problem: Users create hundreds of accounts to farm airdrops/rewards.
Solution: Rate-limit rewards per device and detect virtualized environments.
Token Sale - Fair Launch
Problem: Bots buy entire supply in milliseconds.
Solution: Require human verification and rate-limit per device.
Advanced: EIP-712 Typed Data Signing
For production applications, use EIP-712 for better UX and security:
Traditional Web3 security focuses on smart contract vulnerabilities: reentrancy attacks, integer overflows, access control bugs. But the biggest threat to your protocol isn't a code exploit; it's systematic abuse by bots and fraudsters.
GuardianStack solves this by bringing identity verification to the blockchain without compromising decentralization. Your smart contracts remain permissionless and trustless, but they gain the ability to distinguish between legitimate users and automated attackers.
✅ Stop bots at the contract level - Not just your frontend
✅ Prevent Sybil attacks - Link wallets to real devices
✅ Fair token distributions - No more bot-dominated launches
✅ Protect protocol economics - Stop multi-account farming
✅ Maintain decentralization - Users still control their keys
The Bottom Line
If your protocol has value, it will be attacked. Bots will farm it. Scripts will exploit it. Bad actors will game it.
GuardianStack gives you the tools to fight back without sacrificing the core principles of Web3.