pull down to refresh

Appreciate all the hard work and thoughtfulness with the security considerations file. I'm just still unsure that it's wise to be doing this. The attack vector for crypto SGX honeypots are high. At the end of the day, you have to extract the seed in order to present it to the user, and do occasional SGX server migrations which will require this seed again to provision.

Is this all so that you can offer offline receives for consumers? Because this is being worked on as far as the concept of Lightning goes.

Or do you see this as something you get enterprise customers with that already feel confident in the SGX model, whether that is wise or not?

they’re incredibly counter-intuitive for anyone who doesn’t intimately understand cryptography and security, and they make it way too easy for people to make a mistake

it’s a long discussion but there are other ways to handle key management and recovery that don’t require people to manually handle backups

reply

I honestly think I heard one. I didn’t see any though. The fishing down there is second to none!

reply

Uncle Gary did mention you at dinner the other night.

all I know is if it’s called Mutiny they’re probably up to no good
reply

I have a lightning address attached (WoS). It’s been working well all the time. Last one 3 hours ago. In the last hour keeps giving me this error and sats remain in SN.

by "withdraw sats" do you mean auto-withdraw or something else?

Auto withdraw, sorry

reply

I bought a refurbished PC, put linux on it and downloaded their software. Runs smooth. $300.

reply