Skip to content

Consider hashing the public keys within the keys_hash, within the address #15382

Closed as not planned

Description

@iAmMichaelConnor

Very much undecided, but it's a very small tweak to describe. (cc @dbanks12 to tell me how painful this will be to do in avm-land).

Currently, an address derivation includes a keys_hash, and the keys_hash is essentially h(Npk, Ivpk, Ovpk, Tpk).

Instead, this proposal seeks to tweak it to: h(h(Npk), h(Ivpk), h(Ovpk), h(Tpk)).

That's about it.

Aztecnr and KeyValidationRequests would need to be tweaked, but that's easy enough (cc @LeilaWang). The unknown to me is how difficult this is in avm-land.

See https://hackmd.io/KKqUCujxT5GOoekibspthQ#Summary-list-of-recommendations

Activity

  1. added
    S-needs-discussionStatus: Still needs more discussion before work can start.
    A-protocolArea: relates to designing / explaining the protocol
    mike-caresMike wants to remember this issue, and come back to it from time to time.
    on Jun 27, 2025
  2. removed this from the Protocol by Alpha milestone on Dec 8, 2025
  3. removed
    C-protocol-circuitsComponent: Protocol circuits (kernel & rollup)
    S-needs-discussionStatus: Still needs more discussion before work can start.
    A-protocolArea: relates to designing / explaining the protocol
    mike-caresMike wants to remember this issue, and come back to it from time to time.
    on Feb 4, 2026
  4. iAmMichaelConnor commented on Jul 7, 2026

    @iAmMichaelConnor
    ContributorAuthor

    This was actually done as part of an AZIP for v5

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions