Skip to content

feat: security utilities#75

Draft
Robert-MacWha wants to merge 2 commits intoethereum:masterfrom
Robert-MacWha:blocklist
Draft

feat: security utilities#75
Robert-MacWha wants to merge 2 commits intoethereum:masterfrom
Robert-MacWha:blocklist

Conversation

@Robert-MacWha
Copy link
Contributor

@Robert-MacWha Robert-MacWha commented Mar 9, 2026

Introduce security utilities for Kohaku common.

Currently Includes:

  • Standard blocklist interface for seal / scamsniffer / metamask
  • Address poisoning detector utility

@Robert-MacWha
Copy link
Contributor Author

Open conversation for what should be in/out of scope. I'm generally following features raised in walletbeat's security features, the 1ts wallet security discussion, and the 1ts wallet security standard.

As a general rule, features should be in-scope if:

  • Publicly-sourced (or from-chain). Wouldn't rely on a company's API, or wallet-internal state.
  • Platform-agnostic
  • Wallet-agnostic

And out-of scope if:

  • UX-coupled (IMPORTANT)
  • Informs wallet architecture decisions
  • Requires persistent infrastructure (IE nodes, maintaining indexers, or hosting APIs).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant