28
Phi Am I
28a9404d6e6f4f94a77a30bc23cb1a130cc44bc35acf38bcdf3f1348c7c4b16d

Yes, absolutely. Keep at least 3. Balance sats out amongst them. Use mints that have contact details so when there's problems, you can contact them. 👍

The mint's connection to its LND node is not working. LND nodes get restarted fairly regularly, mostly because of updates.

Try your mint again in a few of hours.

Tree cat.

He likes the view. He's an indoor kitty but he loves to climb this tree whenever someone leaves the door open and he escapes. He'll come in at dinner time.

#cats #catstr

Ginger Snaps!

#Catstr

Cute little Blue Tongue Lizard in the yard today.

https://cryptodnes.bg/en/coinbase-otnovo-srina-sled-kato-bitcoin-dostigna-70-000/

Coinbase does not have your BTC.

You have been warned.

Get your corn of the exchanges.

nostr:npub12nrr09tnly4mw63ekcute7jey2l5v6hrmy20ef5wrzu88qhxem2ql8m9uc

Any plan to pull MSTR's corn before you get rugged by Brian Weakdick?

Magically their system crashes everytime there is a blue sky break out?

Wonder why? You should.

It's because they are trying to crash price before the roof blows and they are caught with their pants down.

Hope this works.

HELP

Building a new node, planning to run latest Bitcoin Core (25.0) - never read any code from bitcoin core until now.

Looks like a massive codebase. I have rudimentary knowledge of C language. I'm clicking through a few pages of the code, wondering how can I trust a codebase I don't fully know. I guess trust is inevitable? Even in a "trustless" system?

Just the fact that it is open source, and *someone* would be double checking the DEVS?

Because what if an organization paid off all the Devs at simultaneously to plant a malicious code line deep in the code, that intelligently sabotages the security or efficacy in some intelligent, genius way, to critically or catastrophically damage the network? This is massively more practical and dangerous than the classic, infeasible "51% sustained attack".

On github it looks like literally only a handful of contributors doing the Lion's share of commits. Isn't this the most practical potential weakness of bitcoin? How can we mitigate as plebs? Is the only way to dedicate ourselves personally to reading the full code and grokking it entirely, as well as every release?

Or just run the release on my node and "trust"? Fuck, man. Is it more important to have a full node running asap (now) to be "sovereign and decentralized", and move on with other important projects, despite not having the months/years of firsthand code verification to really know it is free from potential malicious lines?

Like who has actually read the full code and understood it to gauge the integrity, besides those full-time devs on github?

Any thoughts appreciated...

How to cheat and get free Bitcoin by changing the code.

Step 1. Change the code to give you free Bitcoin.

Step 2. Convince 51 percent of Bitcoin miners to use your version of the code that gives you free Bitcoin, and makes their Bitcoin now worthless.

It has been done before. The Bitcoin Cash fork is what happens when you change the code. Bitcoin Gold, Bitcoin SV, are all results of changes to the code, done by people that thought their version of Bitcoin was better.

By the way, it's written in Go, not C.