
gakonst
@gakonst
135 Following
168279 Followers
25 replies
6 recasts
117 reactions
1 reply
0 recast
4 reactions
0 reply
0 recast
1 reaction
0 reply
0 recast
0 reaction
10 replies
45 recasts
176 reactions
56 replies
115 recasts
671 reactions
0 reply
2 recasts
16 reactions
10 replies
14 recasts
84 reactions
0 reply
0 recast
4 reactions
19 replies
38 recasts
276 reactions
5 replies
11 recasts
82 reactions
1 reply
5 recasts
16 reactions
0 reply
60 recasts
67 reactions
1 reply
0 recast
0 reaction
2 replies
0 recast
0 reaction
1 reply
0 recast
0 reaction
0 reply
0 recast
2 reactions
1 reply
1 recast
5 reactions
- not necessarily, you can forget the key and just replay the auth sig across chains, delegate to proxy and use the contract to handle upgrades. alternatively can store the privkey in cloud etc encrypted w enclave, nbd imho.
- unclear it matters, the ui will give you a preview over x-origin iframe, and your contract will have enough safety checks to ensure you don't get rugged. check secure payment confirmation web api if you really care about doing it non blind.
- granted but not deal breaker, your contract can have multiple signers, need to be thoughtful about it but navigable, plus passkeys being pushed top down.
- session keys app/account interface is important to get right, see our work in porto for more: https://www.ithaca.xyz/updates/porto, and our WIP session key api which is still evolving: https://github.com/ithacaxyz/porto/tree/next?tab=readme-ov-file#keys 3 replies
1 recast
9 reactions
1 reply
14 recasts
72 reactions