skills.rest
mashharuki
mashharukiCOMMUNITY
Explore all skills by this author →
Website𝕏@haruki_web3GitHub

erc4337-privacy-wallet

Develop privacy-preserving ERC-4337 wallets with commitment schemes and deterministic addresses.

1|Updated Jan 17, 2026
Search Tags:#privacy#zero-knowledge#account-abstraction#ERC-4337#vehicle-identity#commitments
One-click install
npx skills add https://github.com/mashharuki/car --skill erc4337-privacy-wallet-mashharuki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: erc4337-privacy-wallet
Source: https://github.com/mashharuki/car/tree/main/.claude/skills/erc4337-privacy-wallet-dev
Command: npx skills add https://github.com/mashharuki/car --skill erc4337-privacy-wallet-mashharuki

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a privacy-centric ERC-4337 wallet development framework, enabling teams to implement account abstraction wallets that protect vehicle identity and other sensitive data on-chain through commitments and optional zero-knowledge proofs.

Core Features & Use Cases

  • Privacy-protected account templates: PrivacyProtectedAccount, AccountFactory, and VehicleRegistry for secure wallet deployment.
  • Commitment-based privacy: Off-chain generation of commitments (e.g., plate numbers) with on-chain storage of only hashes.
  • Deterministic addresses: CREATE2-based deterministic wallet deployment for cross-network predictability.
  • Privacy validation & security: Automated tooling and checklists to verify privacy, security, and auditing readiness.
  • Integrated testing: Comprehensive test suites (privacy, ERC-4337 compliance, and gas optimization) with end-to-end scenarios.

Quick Start

Use the erc4337-privacy-wallet skill to scaffold a privacy-preserving wallet workflow that stores only commitments on-chain, then verify ownership off-chain and deploy accounts via deterministic addresses.

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 identity private on-chain?▼

Build a privacy-preserving ERC-4337 wallet by generating sensitive data like vehicle plate numbers off-chain and storing only bytes32 commitment hashes on-chain. Use provided Solidity account templates to ensure sensitive vehicle identity data remains protected.

How does commitment-based privacy work for account abstraction wallets?▼

Commitment-based privacy for account abstraction wallets works by generating data off-chain and storing only the resulting hash as a bytes32 commitment on-chain. Ownership is then verified off-chain, preventing sensitive details from being publicly exposed on the blockchain.

How do I deploy ERC-4337 accounts to deterministic addresses across multiple networks?▼

Deploy ERC-4337 accounts to deterministic addresses using a CREATE2-based AccountFactory. This method ensures cross-network address predictability, allowing you to calculate and verify wallet deployment locations before executing the creation transaction.

Can I use zero-knowledge proofs to validate off-chain data for ERC-4337 wallets?▼

Yes, you can integrate zero-knowledge proofs to validate off-chain data for ERC-4337 wallets. The framework includes templates and a Python-based privacy validator to verify ownership off-chain and validate ZK proof integration for sensitive on-chain scenarios.

What testing tools are needed to verify ERC-4337 compliance and privacy for smart contracts?▼

Verify ERC-4337 compliance and privacy using Hardhat test suites and a Python-based privacy validator. The framework provides automated tooling and security checklists to validate compliance, gas optimization, and end-to-end privacy scenarios.

Are there limitations to storing only commitment hashes for vehicle identity on-chain?▼

Storing only commitment hashes for vehicle identity requires off-chain data management to verify original details. You must maintain secure off-chain infrastructure to link hashes back to actual data, as the on-chain contract only validates the commitment.

Related Skills

Explore More Software Engineering Skills→
eyepyoneyepyon
1

erc4337-privacy-wallet

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

Community
Advanced
smartgatorsmartgator
3

smart-accounts-kit

Build and manage ERC-4337 smart accounts with delegated permissions via MetaMask Smart Accounts Kit.

Community
Advanced
LumenWipeLumenWipe
3

zk-proofs

Design zero-knowledge proof verification workflows for Stellar smart contracts.

Official
Advanced
konopkjakonopkja
7

multichain

Coordinate multi-chain UX for Ethereum apps with unified balances and automatic network switching.

Community
Advanced