Root: MESSAGE_TYPEHASH in SnowmanAirdrop.sol:49 contains a typo — "addres" instead of "address" — producing an incorrect keccak256 hash.
Impact: All calls to claimSnowman revert with SA__InvalidSignature, making it impossible for anyone (receiver or delegate) to claim Snowman NFTs through the airdrop mechanism.
Recipients or delegates are expected to claim Snowman NFTs by calling SnowmanAirdrop::claimSnowman with a valid EIP-712 signature (v, r, s).
However, MESSAGE_TYPEHASH is defined with a typo — "addres" instead of "address". This causes getMessageHash() to produce a different digest than what standard EIP-712 tools (MetaMask, ethers.js, viem) generate. As a result, _isValidSignature always fails, and claimSnowman reverts for every user — both direct claimers and delegates.
Likelihood:
Every call to claimSnowman passes through _isValidSignature, which uses the buggy typehash to compute the digest. This mismatch occurs on every invocation — no special conditions needed.
Impact:
No one can claim Snowman NFTs through SnowmanAirdrop::claimSnowman, rendering the airdrop contract completely non-functional.
Snow tokens lose their utility — users who purchased or earned Snow tokens cannot exchange them for NFTs, undermining the token economy.
The following tests demonstrate that:
The correct and buggy typehashes produce completely different keccak256 values
A signature created with the correct EIP-712 typehash is rejected by claimSnowman
Fix the typo in MESSAGE_TYPEHASH:
# Root + Impact ## Description * Little typo on `MESSAGE_TYPEHASH` Declaration on `SnowmanAirdrop` contract ```Solidity // src/SnowmanAirdrop.sol 49: bytes32 private constant MESSAGE_TYPEHASH = keccak256("SnowmanClaim(addres receiver, uint256 amount)"); ``` **Impact**: * `function claimSnowman` never be `TRUE` condition ## Proof of Concept Applying this function at the end of /test/TestSnowmanAirdrop.t.sol to know what the correct and wrong digest output HASH. Ran with command: `forge test --match-test testFrontendSignatureVerification -vvvv` ```Solidity function testFrontendSignatureVerification() public { // Setup Alice for the test vm.startPrank(alice); snow.approve(address(airdrop), 1); vm.stopPrank(); // Simulate frontend using the correct format bytes32 FRONTEND_MESSAGE_TYPEHASH = keccak256("SnowmanClaim(address receiver, uint256 amount)"); // Domain separator used by frontend (per EIP-712) bytes32 DOMAIN_SEPARATOR = keccak256( abi.encode( keccak256("EIP712Domain(string name,string version,uint256 chainId,address verifyingContract)"), keccak256("Snowman Airdrop"), keccak256("1"), block.chainid, address(airdrop) ) ); // Get Alice's token amount uint256 amount = snow.balanceOf(alice); // Frontend creates hash using the correct format bytes32 structHash = keccak256( abi.encode( FRONTEND_MESSAGE_TYPEHASH, alice, amount ) ); // Frontend creates the final digest (per EIP-712) bytes32 frontendDigest = keccak256( abi.encodePacked( "\x19\x01", DOMAIN_SEPARATOR, structHash ) ); // Alice signs the digest created by the frontend (uint8 v, bytes32 r, bytes32 s) = vm.sign(alKey, frontendDigest); // Digest created by the contract (with typo) bytes32 contractDigest = airdrop.getMessageHash(alice); // Display both digests for comparison console2.log("Frontend Digest (correct format):"); console2.logBytes32(frontendDigest); console2.log("Contract Digest (with typo):"); console2.logBytes32(contractDigest); // Compare the digests - they should differ due to the typo assertFalse( frontendDigest == contractDigest, "Digests should differ due to typo in MESSAGE_TYPEHASH" ); // Attempt to claim with the signature - should fail vm.prank(satoshi); vm.expectRevert(SnowmanAirdrop.SA__InvalidSignature.selector); airdrop.claimSnowman(alice, AL_PROOF, v, r, s); assertEq(nft.balanceOf(alice), 0); } ``` ## Recommended Mitigation on contract `SnowmanAirdrop` Line 49 applying this: ```diff - bytes32 private constant MESSAGE_TYPEHASH = keccak256("SnowmanClaim(addres receiver, uint256 amount)"); + bytes32 private constant MESSAGE_TYPEHASH = keccak256("SnowmanClaim(address receiver, uint256 amount)"); ```
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.