As the title suggests, the SafeWebAuthnSharedSigner was not included in the original audit, but is being used by the SDK in its passkey implementation, so we need to do a proper audit (as just the audit competition did not give us enough confidence for releasing this contract).
Additionally, we can ask the auditor to do an incremental audit on the changes done to the other passkey contracts since 0.2.0 (see CHANGELOG, as well as potentially merging #451).
Expected Outcome
Coordinate with the auditors for an audit of the contract, as well as the incremental audit on the changes done to the rest of the passkey contracts since 0.2.0.
Implement any required fixes for the contracts.
Adding the audit report for these contracts to the docs/ subdirectory.
As the title suggests, the
SafeWebAuthnSharedSignerwas not included in the original audit, but is being used by the SDK in its passkey implementation, so we need to do a proper audit (as just the audit competition did not give us enough confidence for releasing this contract).Additionally, we can ask the auditor to do an incremental audit on the changes done to the other passkey contracts since 0.2.0 (see
CHANGELOG, as well as potentially merging #451).Expected Outcome
docs/subdirectory.