Загрузка видео...

Не удалось загрузить видео

На главную

Nothing in Bitcoin works without decentralization. If Bitcoin continues to grow towards centralization, its value as a MoV/SoV decreases. Nodes are the last firewall left. The Implimantation is perdominatly centralizied. The Mining has continued to grow more centralized. The biggest attack are the nodes. This is why I am...

34,896 просмотров • 1 год назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Did Epstein influence Bitcoin core development? Short answer: No. This is not how Bitcoin works. Here’s what happened: Epstein donated to MIT Media Lab…who in turn supported MIT Digital Currency Initiative…which in turn funded Bitcoin developers. These devs used to be funded by The Bitcoin Foundation (which I used to run as volunteer Executive Director) there are many devs and no dev or team had power or control over Bitcoin. Under MIT’s patronage the devs had the same deal they had with us at The Bitcoin Foundation: that they could work on the code and not have direction from the org. More importantly — how Bitcoin works is that *even if* a dev was compromised then the nodes and miners would still have to run that code to make it included in Bitcoin. So for example if I had somehow asked the devs paid by Bitcoin Foundation to “add 1000 coins for Bruce” 1) they wouldn’t have done this / it would have been counter to our agreement 2) no miners would run that code & no nodes would recognize it. It would be a laughing stock and completely rejected. Does this mean code dev is not an attack vector? No. It’s still a risk. Particularly with nation state style actors and very careful efforts to co-opt which are much more sophisticated than “give Bruce coins” or something. This is one reason I’m cautious of Bitcoin core funding - especially from actors who’ve had bad judgment in the past. I think we should be cautious of who does the dev and view it as an attack vector. Bitcoin code is transparent and has lots of eyes on it. So in this case especially there isn’t even a solid accusation, let alone evidence that MIT directed nefarious code changes. If that was an allegation the first question should be: well what code specifically did MIT direct and what proof is there and how was it harmful? I think claims around this would collapse. There’s obviously plenty to criticize about Epstein and MIT working with him — and when it comes to digital assets MIT’s work with Gensler and especially its work on CBDCs is much more suspect than the chance that malicious code was pushed through on Bitcoin. Be cautious but this is a nothing burger

Bruce Fenton

231,982 просмотров • 7 месяцев назад

.Erik Voorhees: It’s actually good, from the Trojan horse perspective, that Bitcoin was traceable enough for traditional institutions to tolerate it. “When Bitcoin came out, everyone called it private, thought of it as private. It was referred to as anonymous in every news story. And in some ways, it is very private and very anonymous. But the truth is that it’s also extremely trackable and traceable. It is not private in reality. And the question is, should it have been from the start? And at first I thought, yes, it should have been more private. And that was a mistake in its design. However, I think if Bitcoin had been anonymous truly from the start, like a Zcash or a Monero, it would have had such antagonism from the state. I don’t know that the state could have snuffed it out, but they would have tried much harder. And I think it’s actually good, from the Trojan horse metaphor perspective, that it was traceable enough that the traditional institutions could tolerate it. They’ve never liked it, but they could at least tolerate it because there is some traceability. And that has allowed Bitcoin to grow. And I think in its shadow, that other crypto assets are actually anonymous is very healthy. The strength of cryptocurrency as a concept in society, I think, is served best when Bitcoin itself is not perfectly private, but other assets are. That is a very difficult thing, I think, for the state to combat. And that decentralization of attributes is really, really crucial. So, yeah, I’m very glad that there are other coins that are private. I want there to be more of them, and I want them to be more popular. And I think it’s okay that Bitcoin itself is not.”

Arjun Khemani

23,056 просмотров • 2 месяцев назад

🔁 REPOST, recorded June 2024. Everything Luke Dashjr warned about is happening right now. Luke Dashjr - Is Bitcoin In A Civil War? Three or four entities decide what goes into every Bitcoin block. Most "miners" don't even know what they're mining. And if too few of us run nodes, Bitcoin quietly becomes a CBDC. The Bitcoin Core developer who caught the accidental 2013 hard fork before it broke the network came on to explain why mining is dangerously centralized, why the spam wave is a coordinated attack, and why he built a pool to fight back. Luke Dashjr, Bitcoin Core developer with 200+ contributions and maintainer of the BIPs, founder and CTO of Ocean, and the man who detected and helped stop the 2013 chain split, joins me to lay out the fight over Bitcoin's future in plain English: the difference between a real miner and a "hasher" who just sells compute, how three or four pools (really Bitmain) control what goes in every block, the invisible tax hiding inside FPPS, why he calls the spam wave a funded attack to destroy Bitcoin, why Bitcoin becomes a CBDC if too few of us run our own nodes, whether we are already in a civil war, and how Ocean is trying to hand block construction back to miners. Send this to anyone who thinks Bitcoin mining is decentralized. TIMESTAMPS: 00:00 Intro 01:50 Who is Luke Dashjr 04:09 The rabbit hole: his first patch in 2011 06:06 When Bitcoin became essential (there's no plan B) 10:09 Eligius: the first non-custodial mining pool 12:13 Why he started Ocean 13:50 The real consequences of pool centralization 16:34 Hasher vs miner: who actually mines? 18:36 How FPPS pays you, and what it hides 20:05 Why big pools become proxies for Bitmain 22:35 The launch, and why "censorship" became the word 24:49 What Bitcoin is actually built for 26:40 How to define spam 33:06 "The people behind the spam are out to destroy Bitcoin" 34:47 How the attack gets funded by gamifying it 37:13 Is this an existential threat? 38:48 Run a node, or Bitcoin becomes a CBDC 40:09 Bootstrapping a mining pool from zero 45:40 What non-miners can actually do to help 46:31 Should Bitcoin ossify, or keep upgrading? 49:24 How censorship-resistant is Bitcoin today? 50:00 Is Bitcoin already in a civil war? 51:10 Would the good guys still win a block size war today? 55:53 Ocean's roadmap: decentralizing block construction 1:00:07 How Ocean got its name (Jack Dorsey's nudge) 1:01:53 Do we have a problem in Bitcoin culture? 1:03:22 What Bitcoin means to Luke 1:07:11 The clause: Ocean can do no harm to Bitcoin 1:08:10 Where to find Luke + OCEAN 🎧 Then watch the sequel with Hardfork Kratter, The The Bitcoin Matrix Podcast ⚡️ #279: "Bitcoin Core Has Gone Rogue." 🎧

Cedric Youngelman ⚡️

20,425 просмотров • 1 месяц назад