New 31-of-60 multisig setup.

Hellooooo, Atlanta!

Old friend, new life! My original Specter DIY from 2019, freshly rejuvenated with the most recent firmware!

Really excited that the hardest parts are done and pretty happy with the results!
First time ever working with tiling.

Tfw you're about to spray toxic stuff on your kitchen walls but you have the gear to handle it!

I've been quiet on social media but I've been BUILDING my ass off!
The upcoming @npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl v0.7.0 release is a monumental step forward in so may ways. Amazing, invaluable new contributors. Huge leaps forward in professionalization.
🔥🔥So f'n proud of this progress!! 🔥🔥


I can't wait for @npub17yqgpat6e6ensd78jqhj4c3ef03uq04uqu3z05rhjnlk67lwm8wq9w5269 next week! We have a Builder's Day table for
@npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl and we just proposed a killer workshop + Q&A for our upcoming v0.7.0 release.
But: volunteer dev + travel expenses = 💸💸💸
Please help me cover the costs (4.9m sats)!
Zaps or: https://btcpay.keithmukai.com
Traveling for bitcoin conferences is SO worth it.
BUT, my normie job is billed hourly; I bill zero hours, I get paid $0.
So travel is a double-whammy: I'm spending a lot of money AND forgoing a lot of income.
I'll eat the lost income if I can get enough help w/the expenses.
I can't wait for @npub17yqgpat6e6ensd78jqhj4c3ef03uq04uqu3z05rhjnlk67lwm8wq9w5269 next week! We have a Builder's Day table for
@npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl and we just proposed a killer workshop + Q&A for our upcoming v0.7.0 release.
But: volunteer dev + travel expenses = 💸💸💸
Please help me cover the costs (4.9m sats)!
Zaps or: https://btcpay.keithmukai.com
Temps reached 100°F / 37.8°C but nostr:npub1kumadawgefxjt2c293whsan5sfmdg5tylm0uk39enc6uxxfy5m4scrz2v7 stayed cool in the A/C!

There's a witty take on this juxtaposition just waiting to happen here. But rather than trying to be clever on a hot, humid morning, ima just crowdsource that.

nbd, just racking up merged PRs into more and more FOSS projects!
https://github.com/cculianu/Fulcrum/pull/194
(you non-devs missed out on getting an easy one here!)
The laptop is better than a Raspi4 but obv still closer to that end of the spectrum than a more powerful, new desktop or server. Made some settings tweaks, hoping for a better, faster outcome for Round 2.
8yr old laptop def not as powerful, but not a wimpy Raspi4 either.
I tweaked the bitcoin core rpc settings for more throughput. Hopefully that speeds things up.

I should have reviewed Craig Raw's writeup.

Laptop with battery. Even still, looks like nostr:npub1r7psmkr4zv93xnal8un6d8hvmpsn5jvhfzn3kk38rfcel6awznks7znspg is right: I'm gonna have to learn about proxmox checkpoints.
Two weeks?! 😭😭😭
Aside from IBD and then Fulcrum indexing, the containers aren't asking for much.

That makes sense. My understanding is that fast-sync holds more in memory. So if there's a sudden crash, the current progress has nothing on disk to recover from. I think I only saw about a 20-30% difference with it enabled. Not worth losing more days over.
OMG. Fulcrum, you suck.
Fulcrum docs say btc indexing needs "slightly more" than ~40GB of space. It's been indexing for DAYS @ ~10 blocks/s. But it crashed overnight because it maxed out the 100GB data partition I allocated for it!
Fine. Set up a bigger partition. Restart. And... ARGGHHH!!!

Again: DAYS of indexing... poof.
Truth. Still intermittent fasting. Dinner was a little light last night, def have less fat onboard to burn, maybe slightly kicked out of keto yesterday, too.
A rough, bad 10,000ft view is that Docker gives you virtual OS envs within your computer (ignoring clustering stuff I don't understand) but Proxmox gives you a further layer of abstraction where the real-time hardware your virtual OS is running can be moved around at will with no interruption.
Gotta shut down Server A for some reason but that hosts your production bitcoin node? No prob, just pointy-clicky proxmox stuff (I haven't gotten to this level yet) and move your live node to Server B.
As for Docker, it does occasionally have breaking changes in new versions. Project X is for Docker v.foo but Project Y requires v.bar.