@johnson86tw
I have a quick idea about ZK password AA validator.
I want to build a signature validation module by implementing a validateSignature function with Circom, which is simply a Poseidon hash (input: secret, output: commitment).
If a smart account installs this module, storing the commitment on-chain during installation, the smart account could then use a user-defined "password" to submit user operations and initiate any transaction.
Is this idea feasible?