pull down to refresh
0 sats \ 0 replies \ @k00b 3h \ parent \ on: Bitcoin Optech Newsletter #348 bitcoin
That's one of life's little tricks. We all feel dumb while we get smarter.
We're squarely in the "find out" phase of tariffs I guess.
I recently ordered some shades for my office. I'm a bit worried the tariffs are going cause some delays.
I know. In all likelihood it doesn't matter, but if it saves one person from losing their life savings, it's worth it.
The big thing here is that we aren't self-hosting, so we can't delete the addresses like I would otherwise.
You need something to do in winter. Heat also has been shown to make it harder to think.
Yes, it's possible for us to do. We have a PR that aims to do it. It hasn't been merged yet because it's trickier than it seems.
They release updates here: https://www.mining.build/
It doesn't look like there have been any product announcements lately.
If you want to be fully self-sovereign, I'd recommend running Start OS on a mini PC and running AlbyHub.
If you want medium self-sovereignty, Alby Cloud will allow you to pay Alby to run a node for you.
If you don't mind storing money with someone else, I'd recommend coinos.
Guides are in the FAQ: https://stacker.news/faq#how-do-i-attach-a-wallet
Do you have to have them on a 24/7/365 server to operate correctly?
To receive 24/7 your wallet needs to be online 24/7.
Would you be able to use up all Cowboy Credits before taking Sats?
That's how it currently works.
Would CCs being given be translated into Sats and sent to the wallet?
CCs do not convert to sats. They're like a gift card that you can't trade-in for money. CCs can only be paid to SN. SN tallies the CCs it earns and chooses to pay the exact same amount out as sats through rewards and territory revenue.
I've been holding off out of fear that it's too much gore and doctor drama, but I like the real time angle.
My aunt is an ER doc and I once asked her what her favorite shift to work is and she said 48 hours continuously lol.
Leading hypothesis is that saunter's attached wallet times out slowly, and because we have network error retry logic on the client, we retry as it times out, then those retries time out, which triggers the retry again, and so on.
I've disabled the retry logic on the client for anything that costs money. We are currently trying to reproduce to confirm this is the exact issue.