Oddbean new post about | logout
 Why would Bitcoin core constantly shut itself off during sync and not output anything to debug.log ?

Spent hours on this shit I can't get it going???

So embarrassing but I need halp

Pls can the devs do something?? 
 No sorry the rich guy with the yacht holding his bitcoin with coinbase wants to ossify bitcoin so just gfy 
 Do you actually understand the issues in this debate? 

I’m just wondering if you’re posting Twitter-like hot takes here on nostr for the lulz or if you really do see the world in a simplistic binary of people who hate bitcoin and people who don’t. 

Keep in mind that these ‘takes’ polarize and harm the community and also could result in less support for developers. 
  https://image.nostr.build/bf272356b351fa13bf13332dd8997a76c18afb63500008491f2ae563f42b3fa6.jpg  
 That’s what I thought. Wasn’t sure if you realized this was harmful to the community and devs but it guess you do. 
 Saylor is harmful to Bitcoin development. That’s what I care about. If you’re offended then you can GFY. 
 😂 the world isn’t so simple, is it?

Do you realize that bitcoin core is extremely important but bitcoin’s most centralized point of failure, right?

There is no alternative software version that we can run. We have a choice between core and nothing. 

Maybe you love 4 MB blocks with spam jpegs, but the community fought hard for small 1 MB blocks. What happened? Why was this discovered once nothing could be done? What will stop this from happening again?

Do you really want large corporate interests to fund bitcoin core?

Do you realize that developers are not magical wizards but humans that make mistakes? That lines of code == bugs? And even bug free code can change the network incentives?

Some of us want bitcoin to be there for our descendants and don’t want people to screw it up. 

Can you guarantee that the next software update won’t have another malicious unintended side effect? If not, have a little humility and push for slow and careful progress rather than a fun free-for-all. 
 “Occam's razor is the problem-solving principle that recommends searching for explanations constructed with the smallest possible set of elements.”

Here is a list of projects that lost funding:

https://opensats.org/projects/showcase

These are all projects that could’ve been funded by the ark donation. Bitcoin core is only one of them. This future you want, which I also want, is not going to happen with the tools we currently have. Lightning still fucking sucks. Businesses still don’t accept bitcoin as payment. Do you think this future you want will happen without btc pay server and lightning improvements? 

And if you think that more money going to bitcoin core will break bitcoin or create some type of bug, then it isn’t anti fragile money. Remember that you don’t have to update your node. The bitcoin core team can’t force you to use the version of bitcoin they want. It’s a free market. 
 That sucks, doesn’t it, that he didn’t fund opensats, but that’s a red herring and not the debate. Saylor’s issue is with unrestricted core development. He said as much in Livera’s podcast. ODELL implied that funding was offered but it had “strings attached”. 

Lightning doesn’t suck. It’s just that you want to use it for use cases it likely can’t support with its channel-based architecture. 

I too miss the good ol’ days when fees were low. We all knew that wasn’t going to last. 

It’s clear that Lightning’s destiny is to be used by large institutions and federations. We, the plebs, will be kicked off to higher L3s and federations like Liquid, fedimint and ecash. Those federations will use Lightning to exchange with each other. Don’t blame me or Saylor. Satoshi made those rules when he set in motion fee increases on L1. 

If you think bitcoin should be used as payment by businesses, you need to first understand Gresham’s Law and Thier’s Law. There is a natural progression and you seem to be trying to jump steps. There are no shortcuts. I’m happy to explain more. 

Sure, bitcoin is anti-fragile, but only if we protect the protocol. It has a weak spot which is core. Read up on the blocksize wars to understand how close the battle was. We all came close to living in Craig Wright’s world. 

Don’t gaslight me with the “you don’t have to update your node” bullshit. If you believe that, you don’t understand how software requires continual maintenance just to stay working. If we didn’t update our nodes, those nodes would die in a decade. 

A free market has choice, and there is only one monopoly here, isn’t there?

I can tell your heart is in the right place but you need to start getting into the details. The core network needs to be protected and defended so we and our descendants don’t lose the gift Satoshi gave us. Don’t take its success for granted. 
 I can tell you’re making a lot of assumptions about me. 

Like I said there are projects that would’ve gotten funding through open sats including those layer 3s like cashu. And more funding can help with the maintenance. But if you think core can be corrupted and that will hurt bitcoin, then it inevitably will happen. It’s only a matter of time.  But if bitcoin is anti fragile, then core can’t destroy it. 
 Yes, I am making a lot of assumptions about you. Feel free to correct me when I’m wrong. 

Anti-fragile doesn’t mean invulnerable, right? I don’t get where all this magical thinking comes from. We don’t need to defend the protocol because nothing can hurt it? 

I hear this a lot. It feels like some people are stuck in a fantasy game. No, our lord Satoshi did not speak the magic words and did not imbue the protocol with a magical shield. It’s up to you, me, and the rest of the community to defend it. 

Yes, I want payments too. I want many things. Keep in mind that we’re playing the long game here. We have a low time preference. Who said that we should have payments by now? Maybe your children or grandchildren will finally implement payments on bitcoin. 

People need to stop imposing they mental schedule on bitcoin. Let it develop and take over the world as it will. Just protect what matters so it has that chance. 
 If you’re going to make assumptions and expect me to correct you, then you’re just wasting my time and I’ll mute you. I defend bitcoin by running my own node and opting out of the soft forks that I don’t want. Simple as that. Maybe you need to reread the blocksize war because you seemed to have learned something different from what I did when I read it. Neither the devs nor the miners/corporations were able to change bitcoin during the war. It came down to the nodes. 
 “I defend bitcoin by running my own node and opting out of the soft forks that I don’t want.”

😂 No you don’t. You never have opted out of any soft fork. NAME ONE that you opted out of. 

You run core like everyone else. You trust them and run the soft forks they choose, like everyone else. 

You don’t even know how to permanently opt out. All you know how to do is delay the inevitable. 

Yeah, mute me. Then we’ll all know I was right, that I caught you in another false statement. When you couldn’t prove me wrong, you just ran and hid. 

“Maybe you need to reread the blocksize war because you seemed to have learned something different from what I did when I read it. Neither the devs nor the miners/corporations were able to change bitcoin during the war. It came down to the nodes.”

But the core devs DID change bitcoin during the war, right? They enabled segwit. 

The war was a power struggle between core and the other large holders. Core proposed a soft fork while the large holders proposed hard forks. 

The lesson that the nodes made a choice and won the war is another little lie we tell ourselves. If you go back and carefully look at the blocksize war chronology, you’ll see that the “user activated soft fork” was threatened but never enforced. There was definite visible support for the UASF but we don’t know whether a sufficient number of nodes would have enforced to win a contentious split. The issue was moot by the time the UASF was to activate. The nodes didn’t need to enforce because the miners had already capitulated to core’s segwit change. 

The lesson I learned is that core devs are powerful and that in a war between a soft and hard fork, the soft fork will probably win. Why? Because the soft fork is compatible with all nodes while the hard fork is compatible with only the nodes which decide to upgrade. Many node operators are lazy, busy, or don’t care enough to bother upgrading. 

We can’t ignore the part that core’s software won. This supports why I believe we must be extremely careful with what goes into core. 
 Guys come on life is too short to argue about such things over days ☺️

Pls go listen to a baby laugh or throw a ball for a dog 🐶🐕 
 Good advice. 

I’m also hoping people save their attack memes for people outside the community. 

In here, we should discuss and respectfully debate ideas recognizing that we’re all trying to push bitcoin forward. 
 I'm not a Bitcoin dev. But you could try throwing your computer in the trash and trying again on another one.

Are you running out of resources? 
 Don’t run the system task, don’t run as daemon, and run bitcoind directly from cli w the params you need and you should have your answer 
 God that's so obvious yet I'm too retarded to think of it , ty good sir will try this now 
 Or launch bitcoinQT from the command line and watch the comments in the terminal 
 It was OOM 🫡 fixed now ty 
 Did you check your syslog for errors? Most likely is that your kernel killed bitcoind in order to free up RAM.