Guardian currently vendors its own copy of the OpenZeppelin-for-Miden multisig and guardian auth account components as raw MASM and compiles them locally. We should consume these contracts from the upstream Miden standards / OpenZeppelin Miden contracts package as a versioned dependency, the same way we already consume miden-standards for the underlying signature primitives.
Current state
The multisig/guardian account contracts live as vendored .masm in two byte-identical locations:
- crates/contracts/masm/auth/ and crates/contracts/masm/account_components/auth/ — canonical source
- packages/miden-multisig-client/masm/auth/ and .../account_components/auth/ — a copy mirrored into the TS package (via
packages/miden-multisig-client/scripts/generate-masm.mjs)
Guardian currently vendors its own copy of the OpenZeppelin-for-Miden multisig and guardian auth account components as raw MASM and compiles them locally. We should consume these contracts from the upstream Miden standards / OpenZeppelin Miden contracts package as a versioned dependency, the same way we already consume miden-standards for the underlying signature primitives.
Current state
The multisig/guardian account contracts live as vendored .masm in two byte-identical locations:
packages/miden-multisig-client/scripts/generate-masm.mjs)