safety

Enforce safety UX patterns for Ethereum dApp address, token, and transaction inputs.

7|3|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/konopkja/ethux-design --skill safety-konopkja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: safety
Source: https://github.com/konopkja/ethux-design/tree/main/skills/safety
Command: npx skills add https://github.com/konopkja/ethux-design --skill safety-konopkja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safety and security UX patterns for Ethereum dApps: risk-differentiated warnings (info/caution/danger tiers), ENS name resolution, ERC-55 address checksum validation, spam token filtering, and safe max-send calculations. Use this skill whenever building or reviewing ANY address input, warning system, risk indicator, token filtering, ENS display, send-max feature, or phishing protection — even if the user just mentions 'safety', 'security', 'warnings', 'address validation', 'ENS', 'spam tokens', or 'send max'.

Core Features & Use Cases

  • Risk-differentiated warnings with info, caution, and danger tiers to differentiate risk levels and reduce warning fatigue.
  • ENS name resolution and display alongside checksummed addresses to improve accuracy and clarity.
  • ERC-55 address checksum validation for all user-entered or pasted addresses.
  • Spam token filtering to hide suspicious or unverified tokens, with a dedicated hidden/unverified view and warnings.
  • Safe max-send calculations that account for gas, fees, and network conditions, including L2/L1 data considerations.
  • Cross-references to related UX and security patterns for broader integration.

Quick Start

Integrate these safety patterns into your dApp by validating addresses with ERC-55, resolving ENS names, applying risk-tiered warnings, filtering tokens, and calculating safe max-send amounts.

Frequently Asked Questions about safety

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

FAQPage Schema
How do I validate Ethereum addresses in my dApp using ERC-55 checksums?

Ethereum address validation uses ERC-55 checksum validation to verify user-entered or pasted addresses, ensuring input accuracy and preventing funds from being sent to malformed addresses. It specifies concrete front-end validation rules and fallback behaviors for invalid inputs.

How do I implement risk-differentiated warnings for Ethereum dApp security?

Risk-differentiated warnings use info, caution, and danger tiers to differentiate risk levels and reduce warning fatigue in Ethereum dApps. This approach provides concrete UI patterns to clearly communicate security threats without overwhelming the user with excessive alerts.

What is the best way to filter spam tokens in a Web3 wallet interface?

Spam token filtering hides suspicious or unverified tokens by applying dedicated UI patterns, including a hidden or unverified token view with specific warnings. This prevents users from interacting with potentially malicious assets while maintaining interface cleanliness.

How do I calculate safe max-send amounts for Ethereum transactions including gas and L2 fees?

Safe max-send calculations account for gas, fees, and network conditions, including L2 and L1 data considerations, to determine the maximum sendable token amount. This prevents failed transactions caused by insufficient gas reserves.

How does ENS name resolution improve address input UX in dApps?

ENS name resolution improves address input UX by resolving readable names and displaying them alongside checksummed addresses. This enhances accuracy and clarity for users sending transactions to complex hexadecimal Ethereum addresses.