This seems like perhaps the worst time to launch a custodial wallet on iOS without regulatory considerations so let’s hope there’s more info to come here. 

 I think this is an overreaction if you’re using it for zaps. You shouldn’t keep large amounts of bitcoin on it and I can’t believe that’s the intent. 

 I think perhaps you’re misunderstanding my concern. We are discussing the regulatory compliance aspect to running a custodial wallet (particularly in the US/EU). 

Users trusting their funds (in whatever size) to a custodian is a separate discussion and an individual decision. 

 I understand that and in fact it is very important to other stakeholders for instance people concerned about the legal framework, jurisdiction, etc. Regarding code and the use of Apple Secure Enclave I think it does support EEC algorithms like NIST P-256, P-384, P-521 but not our unique Bitcoin secp256k1. About app code it would probably need OpenSSL or libsodium to integrate into iOS.. 

 Indeed, if am not mistaken others custodial wallets got ban in the US. I wonder if there are some implementation of non custodial wallets (I am just quickly browsing https://github.com/PrimalHQ/primal-ios-app) and I noticed a folder Nostr Tools .. I am not familiar yet.. just wondering if they using Apple Secure Enclave (secure element) https://support.apple.com/en-gb/guide/security/sec59b0b31ff/web 

 No, you can also Zap without a wallet, and Freerse can Zap successfully launched in the Apple App Store two days ago. It was a tough process, and it took more than two months of negotiations, complaints, and revisions, and I can now recite the iOS App Store Review Guidelines backwards 😂. It is estimated that miljian spent a lot of time and effort in passing the review.
nostr:note1y4w4mlsjfkr4p3ke9svh8un5g769zsm6wmmeadp57498am2h3z6snrzqh4