Skip to content

feat: add ENS-HCA smart account support#392

Draft
zeroknots wants to merge 1 commit intomainfrom
feat/ens-hca-account
Draft

feat: add ENS-HCA smart account support#392
zeroknots wants to merge 1 commit intomainfrom
feat/ens-hca-account

Conversation

@zeroknots
Copy link
Copy Markdown
Member

@zeroknots zeroknots commented Mar 23, 2026

Description

Adds support for the ENS Hardware-Controlled Account (HCA), a Nexus-based smart account with locked-down module management designed for ENS hardware-backed signers. The HCA blocks installModule/uninstallModule after initialization and uses immutable default validator and executor modules set in the constructor.

Key additions:

  • src/accounts/hca.ts — Full account implementation: factory initData encoding, Solady CREATE3 address derivation, EIP-712 domain, signature packing
  • Wired HCA into all account routing (getDeployArgs, getAddress, getEip712Domain, getEip1271Signature, etc.)
  • Renamed ENS_VALIDATOR_ADDRESS to ENS_HCA_MODULE with updated deployed address (0x432df07B...)
  • 12 unit tests covering deploy args, CREATE3 determinism, install data, and signature packing
  • Deployment integration test for HCA with ENS owners

Note: Contract addresses (HCA implementation, factory, module) are placeholders for now and will be updated once final deployments are ready.

Checklist

  • Changeset

Add support for the ENS Hardware-Controlled Account (HCA), a Nexus-based
smart account with locked-down module management for ENS hardware-backed
signers. Includes factory encoding, CREATE3 address derivation, EIP-712
domain, signature packing, unit tests, and deployment test.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@zeroknots zeroknots marked this pull request as draft March 23, 2026 08:13
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