@ek204
3,460,945 sats stacked
stacking since: #57444longest cowboy streak: 204 verified stacker.news contributornpub16x07c...2j2s96s89d
100 sats \ 1 reply \ @ek 17h \ parent \ on: Stacker News Live #118: The Money Transmitter Rule with Ek (Zap.Stream) meta
Thank you :)
I only wear this for livestreams though so it's not like I am running around like this lol. Everyone in the lab does know my face. Not sure if that was obvious 🤔
I am not sure what you mean. When we will migrate to fee credits, we will give you time to withdraw your sats before they get converted into fee credits. So you can keep some sats which will then become fee credits.
Does that answer your question?
The withdraw threshold is not configurable currently, it's always 10% above the desired balance. But sounds like that's what you would like to configure and not how much should stay on SN (desired balance).
Another way to think about this is that the 1 trillion dollar bug bounty will likely be a bad actor, not a good actor
This.
Also, if we solely rely on such bad actors, we will be blind to any kind of vulnerability until it was already exploited and thus too late. Security usually works in layers so relying on "we haven't seen anyone stealing bitcoin via a protocol vulnerability yet" sounds like waiting until all layers are breached before we fix something. It's usually a lot of small details that combined lead to catastrophic failure.1
We should already be alerted when some assumptions can be broken even if that doesn't immediately results in a severe vulnerability. But we won't notice if bad actors find vulns with low CVSS.
But it's true, everyone in bitcoin should be incentivized to put our due diligence in keeping bitcoin secure but I am not sure if that's as effective as it sounds.
Footnotes
LN address can't be used for sending, it's technically just a way to request an invoice but it doesn't include a way to pay invoices.
That's from @WeAreAllSatoshi 👀
But the concerns about small zaps due to network fees are valid. But on the other hand, lightning was meant to support micropayments.
I personally have a private channel with SN but not sure how many will open one. The good thing is that you can use this private channel also for other things.
Ahh, makes sense. Will fix Alby support today.
I assumed it would be the same if SN could connect with Blink's API?
Yes!
yes, k00b replied here (next to your reply)