eip-712

Integrate EIP-712 typed data signing with wagmi and verification with viem.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/involvex/aetheris --skill eip-712-involvex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eip-712
Source: https://github.com/involvex/aetheris/tree/main/.agents/skills/eip-712
Command: npx skills add https://github.com/involvex/aetheris --skill eip-712-involvex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers integrate EIP-712 signing and verification into Scaffold-ETH 2 projects, ensuring typed data is created, signed, and verified in a safe, user-visible way.

Core Features & Use Cases

  • Frontend signing: use wagmi's useSignTypedData to sign typed data with eth_signTypedData_v4.
  • Backend verification: verify signatures with viem's recoverTypedDataAddress in API routes.
  • Guidance: provide shared domain, types, and message patterns to keep signing and verification in sync.
  • Use Case: implement off-chain signing for user actions or on-chain verification via a contract.

Quick Start

Create a shared EIP-712 utility module and wire up signing and verification using wagmi and viem.

Frequently Asked Questions about eip-712

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement EIP-712 typed data signing and verification in Scaffold-ETH 2?

EIP-712 typed data signing and verification in Scaffold-ETH 2 is implemented using wagmi's useSignTypedData on the frontend and viem's recoverTypedDataAddress in backend API routes. A shared module for domain, types, and message construction keeps both flows synchronized.

What is the best way to verify EIP-712 signatures on the backend using viem?

The best way to verify EIP-712 signatures with viem is using the recoverTypedDataAddress function within your API routes. It recovers the signer address from the typed data payload, allowing your backend to cryptographically validate off-chain signatures.

Does wagmi support eth_signTypedData_v4 for frontend EIP-712 signing?

Yes, wagmi supports eth_signTypedData_v4 through the useSignTypedData hook. This allows your Scaffold-ETH 2 frontend to prompt users to sign structured, human-readable typed data securely via their connected wallet.

Why do I need a shared module for EIP-712 domain, types, and message construction?

A shared module for EIP-712 domain, types, and message construction is needed to keep frontend signing and backend verification in sync. Sharing this logic prevents signature verification failures caused by mismatched payload structures across your stack.

Can I use EIP-712 off-chain signing for on-chain contract verification in Scaffold-ETH?

Yes, you can use EIP-712 off-chain signing for on-chain contract verification in Scaffold-ETH. The Skill guides you through creating typed data payloads that can be signed off-chain and later verified by a smart contract using an ecrecover mechanism.