All good things in life are hard kid.

All traps set up to make your life worse are made easy.

Do more hard things.

For people who don't care to learn, anything and everything is complex.

But paid help exists https://wizardsardine.com/liana/#partners

Geo-disbursed timelocked multi-sig is a hell of a power trip

Hahaha we know. They made this up to FUD Bitcoin mining so people started launching it at AI because "the economy" or whatever likes AI and now business execs and politicians have to fight our FUD for us lmao

I am in a bubble that does not take popularity into consideration lmao.

So what I was thinking when I wrote that, was more along the lines of, when you go to implement it into your website, you're going to find SDKs and you'll be able to read the code of a few clients that have implemented it into a few different languages.

Whereas LNURL is pretty exclusively NPM.

I mean, I think so, but yeah NIP-07 is also a thing

I'd go with NIP-46 these days over LNURL anyway.

There's just a lot better support for it.

Oh and don't forget that both of these specs are implemented in stacker news which is open source

You should look at the stress tests performed on other metal plate storage systems, think about how yours would hold up.

Cheetahs are better pets.

Cheetahs don't view humans as food because humans can't run very fast. Cheetahs hunt things that run.

However, big cat means expensive feeding and lots of land for when they get the big cat zoomies.

So how long could you keep it? Until you go bankrupt from it eating you out of house and home

A super boomer Bitcoin wallet that lets you make little virtual coins or bills with your UTXOs and/or explains every aspect of Bitcoin through extensive metaphor visually.

Why isn't it made yet? I don't have time to do it unfortunately.

Imagine you work at a steak and shake and through the customers, mopping duty, trash duty and everything else you gotta make time to do, you get a call from your manager "Hey today is (insert remembrance day of thing) can you set the flag to half mast?"

As far as why the percents matter... I could explain it, but it's been explained to death and don't care about it to begin with lol.

If knots forked I would ping Luke with a "What the hell... Why?" (I don't think knots will fork) because a consensus level change is completely unnecessary. This is just a mempool policy that users get to independently decide on.

I am once again asking for Bitcoin nodes to be more modular and less monolithic

"Many people are saying this" type energy lmao

Nice find, but no github link eh?

Sure it can, and giving small miners the knowledge that they should add major miners as direct peers helps. We also have by default 8 two way peers and 2 one way peers. Those 2 one way peers are meant to be the high data transfer peers to help blocks get through the network faster.

However, if you're one of those smaller miners, those 2 one way peers don't exactly help the block that you found get to those bigger miners faster which again puts the smaller miners blocks at higher risk of getting orphaned.

So large mining operations can have high data bandwidth connections to each other, thereby having more time to work on a block than a smaller miner that may be part of a smaller pool say running off a gas generator in South Africa or helping sustain the energy demands vs energy supply inefficiencies of some power grid somewhere remote with much slower internet connectivity.

That direct connection vs node to node gossip to eventually some small miner can mean whole minutes of time that the bigger data center style miners have working on a block that those smaller miners are still hashing on the old block.

BUT when the trade off is preventing sovereign node runners from setting their own mempool policy, it doesn't seem like individuals are going to like that regardless of the downstream effects

Sure, I wish the Bitcoin reference implementation were a little more modular and a little less monolithic.

I wish we had Bitcoin node mods. Little git patches you could apply to compatible versions of the core implementation. We've seen a couple of git patches here and there for things (some of the ones I was most interested in were actually merged) and I think we could see a lot of that. "Hey users are finding this patch quite popular, so let's merge it"

To help bridge a gap here, it would be similar to a Minecraft mod launcher, but because it's C and not Java, it would have to compile your choices, but that would then get you an extra likely often silly little widget that makes playing with your node fun and importantly, but probably less often, something essential that eventually gets merged into the reference implementation anyway.

I believe this makes sense because core developers are already specializing in different aspects of the codebase anyway, so if those aspects were modular components, the workflow wouldn't be all too different from what it already is. I also believe it might result in less developer burnout, because instead of yelling at a dev, users could just patch the undesirable on their own system and then maybe theres a dashboard somewhere that informs everyone of what patches are popular.

Hehehehe: https://grapevine.my/ https://github.com/Pretty-Good-Freedom-Tech/graperank-nodejs