Have you noticed that the strike/bitkey integration sends to the same bitkey address? Are you concerned with address reuse?
Yeah it’s kinda comical I figured since I was trying to send all of it to a Bitkey maybe there was a work around but no joy. nostr:nprofile1qqsgydql3q4ka27d9wnlrmus4tvkrnc8ftc4h8h5fgyln54gl0a7dgspxdmhxue69uhkuamr9ec8y6tdv9kzumn9wshkz7tkdfkx26tvd4urqctvxa4ryur3wsergut9vsch5dmp8peszrthwden5te0dehhxtnvdakqtxjx6r any love for a pleb struggling against the 5k a week withdrawal? Feels like a fast lane to Bitkey would be a win. nostr:nprofile1qqsvf646uxlreajhhsv9tms9u6w7nuzeedaqty38z69cpwyhv89ufcqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg6waehxw309ahx7um5wghx7unpdenk2urfd3kzuer9wcct67dg has the auto withdrawal to Bitkey up and running and it works great.
Discussion
I’m not overly concerned. It’s all KYC corn, all routed through strike, my privacy is already shot with this cold storage. Perfect excuse to mess with a Bitkey proper sexy piece of hardware will say. I’m sure at some point I will have to reduce the amount in here and will work to obfuscate the trail then.