Yes, there is risk involved. In the paragraph Risk Management I wrote about different types of risk involved in this trade. One of them being exposed to third party risk of the chosen platform, meaning you have to send your bitcoin to the exchange and they hold the keys to the wallet.
I won't express any opinion about the severity of the risk, that's for people to decide for themselves. I always recommend doing your own research.
That said, it's also possible to use USD(t) of Gold (PAXG) as collateral.
If #bitcoin really is going the function as the world reserve asset, there is a need to hedge large positions and thus we need trustworthy exchanges that provide those instruments and make that possible.
Nothing beats self-custody. But for the investors who want to go further out on the risk curve and trying to get yield on their bitcoin, these or examples of how one could do it.
But there are always trade offs and risk involved. No such thing as a free lunch.
Thank you for reading my work!
Thanks for sharing more details to debug. It looks like some situation with my NDK trying to send nutzaps.
I dont have much knowledge on nutzaps. Let me analyze and get back.
However this issue should not happen when sending zaps to anyone who does not have nutzaps configured. They must be able to receive zaps normally.
Yo #Nostr!
How can I get nostr:npub1ex7mdykw786qxvmtuls208uyxmn0hse95rfwsarvfde5yg6wy7jq6qvyt9 running in #Ghana with on/off-ramps via Mobile Money vendors? I’m tired of seeing informal workers putting in fuck tons of #work just to loose their “time and money in an abstracted form” (looking at you nostr:npub1cn4t4cd78nm900qc2hhqte5aa8c9njm6qkfzw95tszufwcwtcnsq7g3vle) to debasement. We need #FreedomMoney !
nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx