Interesting. You think he worked on Bitcoin because someone else paid him?
Discussion
Let me try and dig up the quote…
Perfect timing nostr:npub1qpdufhjpel94srm3ett2azgf49m9dp3n5nm2j0rt0l2mlmc3ux3qza082j can you help answer this? 👆
I'll have to dig around a bit, I'll try to take a look see...
Thought it came up in the newer released Adam Back emails with the Craig Wright case.
I did a quick search with the .txt file of "Kicking" https://hive.blog/bitcoin/@crrdlx/satoshi but came up empty. Those Adam Back emails (only three or so as I recall) were very early, pre-whitepaper. They show up in the pdf version at page 24. I stuck the txt version into Grok and had it search/think, it came up empty as well. See the query: https://grok.com/share/bGVnYWN5_b6ec7d78-9834-408d-90d6-4270c96ae732
Thanks for checking. I’m gonna give it a shot now too.
Ok, sorry it was after the project went live and in emails with Martti Malmi.
Interesting, you were 100% correct. I was kind of thinking Malmo when you mentioned COPA trial because he had like 150 back and forth and figured just by sheer volume that might have been mentioned. Tha KS for finding that.
No but it’s hard to justify working on a project especially full time when you need to pay bills and eat.
So you think there is no risk on the opposite side? Too much funding.
I mean adding too much to Bitcoin and breaking something because people were getting paid to do things so they had to find things to do?
Funding open source developers doesn’t increase risk of breaking things. You can spend billions hard forking the protocol with teams of hundreds.
Bitcoin doesn’t stay “safe” because open source devs scrape by on funding.
I guess that’s why most nodes are not running latest updates
It still makes me nervous tho
It’s pretty normal that the majority doesn’t immediately update to the latest version. Like not buying the v1 of the newest console.
I use my node regularly and I think I’m still on 24 or 26.
Will you update your mempool policy to include the new changes?
Typically I wait and observe for months before updating or making changes to my node if nothing critical is happening.
And the great part is I don’t have to do anything for the foreseeable future if I don’t agree or I could just leave core and run something else.
Im not a “core simp” as you’d call it 😅 but I personally wouldn’t run knots only because I’ve seen Luke do and say many questionable things over the years idc if he’s the rain man of bitcoin code 😂 I don’t trust him.
Short answer, probably eventually.
I’m being retarded with the accusations but I think it proves my point- according to btcframe the *latest* core nodes 29.0.0 are only 5.52% of network. 28.1.0 is higher at 20%
Protest knots are about 5% with 7.3% total now.
So I’m not saying “democracy” I’m saying:
If the update is supposed to achieve a consistent mempool across the whole network- how will that be achieved with the 5-20% of nodes that update to latest core software?
I’d love to see other implementations especially with cooler UX and nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx has made it clear they are welcome to apply with OpenSats.
Maybe a bad analogy but, do the highest paid doctors get lazy and start killing patients? Or do they make the most money because they deliver the best results?
There was a lot of money and hash behind bcash and it failed spectacularly.
There’s obviously a nonzero chance. Even so this appears to be mitigated by how open sats delivers funding. Reviewing the project and voted on by a board.