erc4337-privacy-wallet

Implement privacy-preserving ERC-4337 wallets using bytes32 commitments and CREATE2 deployment.

1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/eyepyon/car --skill erc4337-privacy-wallet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: erc4337-privacy-wallet
Source: https://github.com/eyepyon/car/tree/main/.claude/skills/erc4337-privacy-wallet-dev
Command: npx skills add https://github.com/eyepyon/car --skill erc4337-privacy-wallet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Privacy-preserving ERC-4337 wallets for vehicle identity data, protecting sensitive information by storing only commitments on-chain and enabling off-chain verification.

Core Features & Use Cases

  • Commitment-based privacy: uses bytes32 commitments (keccak256) to hide sensitive data like license plates or biometrics.
  • Deterministic deployment: CREATE2-based account factory enables predictable wallet addresses across networks.
  • ZK-proof integration: optional zero-knowledge proofs for on-chain verification without revealing data.
  • Vehicle registry flows: supports mapping commitments to wallets, updates, and authorized verifications for fleet use cases.
  • Testing & security tooling: includes privacy validation script and security checklists to guide audits.

Quick Start

Copy, customize, and deploy templates; compute commitments off-chain, deploy accounts via AccountFactory, and submit UserOperation to EntryPoint using the provided scripts and tests.

Frequently Asked Questions about erc4337-privacy-wallet

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

FAQPage Schema
How do I build an ERC-4337 wallet that keeps vehicle license plate data private on-chain?

Build a privacy-preserving ERC-4337 wallet by storing only keccak256 bytes32 commitments on-chain while calculating and verifying sensitive vehicle identifiers off-chain. This protects license plate data by ensuring the actual information never leaves the off-chain environment.

What is the best way to achieve deterministic addresses for vehicle smart wallets across networks?

Use a CREATE2-based account factory to achieve deterministic addresses for vehicle smart wallets. This method enables predictable wallet generation across multiple networks while mapping commitments to wallets for fleet registry use cases.

Can I use zero-knowledge proofs for on-chain verification without revealing vehicle biometric data?

Yes, you can use optional ZK-proof integration for on-chain verification of vehicle biometric data. This enables verification without revealing the underlying sensitive information, keeping all original identifiers off-chain.

How do I deploy and submit UserOperations for an ERC-4337 commitment-based privacy wallet?

Compute commitments off-chain, deploy accounts via AccountFactory, and submit UserOperation to EntryPoint using provided scripts. This workflow handles updates and authorized verifications for vehicle registry flows.

What are the limitations of storing only commitments on-chain for vehicle identity management?

Storing only commitments on-chain requires off-chain calculation and verification infrastructure. While it protects sensitive data, you must manage off-chain commitment mapping and consider optional ZK-proof integration for enhanced privacy validation.

Do I need Solidity contracts to implement account abstraction for vehicle identifiers with commitment schemes?

Yes, implementing privacy-preserving ERC-4337 wallets requires Solidity contracts using bytes32 commitments. You also need CREATE2 deterministic deployment and optional ZK-proof integration to protect vehicle identity data.