id.place: store signed authorization

[frolic]

currently we create an arbitrary EOA and use it to sign the initial setup tx(s) for creating a smart account tied to a passkey then we dispose of the EOA, but that makes it difficult for the passkey smart account to be portable across chains

instead we should store the signed tx(s) somewhere associated with the passkey (porto uses a hosted service for this but it could be onchain too) so that we can replay this on other chains to bootstrap the passkey smart account but without needing the original EOA

[linear]

MUD-12 id.place: store signed authorization

[frolic]

alternatively, could we store this as user data with the passkey so it gets synced together with the passkey across devices instead of a hosted/public data store?