[Epic] Implement Passkey support in Flow core protocol

[vishalchangrani]

Why

End-to-end support for Passkey authentication is a frequently requested feature that is becoming table stakes on blockchain. Flow needs this for the user experience and security benefits it offers. This will involve both core protocol changes and changes to the SDKs and wallets. We will track protocol related changes which are required as part of the bigger initiative driven by 4D.

How will we measure success

• Protocol support for passkeys unblocks 4D to build out toolset support, docs and other related to enable passkeys for users
• Passkeys is released to users on mainnet

DACI (for Protocol scope of involvement)

D: TBD
A: @Kay-Zee @janezpodhostnik @tarakby 4D team
C: @dete
I: Product/Marketing

Problem definition

Mainstream users arriving to Flow may not initially desire setting up a wallet and may also not desire using federated logins from big tech. The best alternative is passkeys which provide a more secure authentication method compared to traditional passwords or seed phrases. They simplify the login and wallet recovery process and address a major pain point in crypto wallet management.

Task breakdown

Preview Give feedback

1. Modify Access API to extend the signature field to include the passkey #6531
   Stale +1
2. [FVM] Update signature validation on the EN to support the new signature format #6532
   Stale +1
3. [Unconfirmed] change to Collection node

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tarakby]

The core-protocol work in this stream is mainly FVM work.
It would be good to loop in someone from FVM, specifically Janez, to at least to review PRs, and at most implement the FVM change. I even think Janez should replace Alex in the OKR, there isn't a protocol point that requires @AlexHentschel IMO.

cc @vishalchangrani @franklywatson