BrightSats (@BrightSats) header
BrightSats (@BrightSats) profile picture
Joined July 2008
Photo by BrightSats (@BrightSats)Photo by BrightSats (@BrightSats)Photo by BrightSats (@BrightSats)Photo by BrightSats (@BrightSats)Photo by BrightSats (@BrightSats)Photo by BrightSats (@BrightSats)Photo by BrightSats (@BrightSats)Photo by BrightSats (@BrightSats)Photo by BrightSats (@BrightSats)Photo by BrightSats (@BrightSats)
Aka don’t hesitate to feed the machine generating your social credit score
20
If fees pricing out spam is the better solution, at what point do you say that approach was worth rejecting the changes BIP110 proposed?
1
50
Good info in this chat. Multi vendor multi sig does feels like the sweet spot. There are no solutions only trade offs. It’s not a coincidence that following a decentralised & distributed approach for your keys matches the nature of Bitcoin itself.
We had the chance to speak with @KLoaec this weekend. Kevin was the first person to sound the alarm about the Coldcard exploit last week. He is a security expert who has been working on Bitcoin for over 13 years. We discussed: • What went wrong with Coldcard’s RNG ? • How to generate strong entropy ? • Dice rolls + passphrase vs. multi-vendor multisig • The role of a secure element • What makes a passphrase truly secure • Using @lianabitcoin for inheritance and recovery • Kevin’s take on BIP 110 And much more The conversation was recorded in French, but English auto-dubbing is available on YouTube. Watch this episode of @lebunkerBTC 🔗👇
1
1
292
Bitcoin isn’t for everybody
The odds of me, serious money, a suit, rolling 100 dice is zero in my life time. No serious people are going to do this, most certainly not an institution, and to think i would then diversify across 4 different providers, 400 rolls of dice.....GTFO....This is not scaleable. It is delusional to think people investing millions of dollars are going to roll dice 100 times or anything else so stupid. Secondly; you are a moron at this point to connect or use software or hardware to protect hundreds of millions of dollars built by companies that have never been profitable, have no revenue growth, no path to profitablity, no excess profits to reinvest in security and R&D, and zero sustainable use case or relevance, and a total incapcity to take on millions of customers to scale and service them. At this point Self Custody is a joke, it is not sustainable, and if the only real bitcoin is self custody bitcoin with a punk-small organization is dumb and announces bitcoin's failure as an experiment. The concept of the fascist bitcoiners, who have never run or built sustainable businesses, who are anarchist, not creators, not builders of real businesses, who in their hearts want the entire system to collapse so they the anarchists with no experience to build industries, yets pretent to be experts promoting and advertising self custody I hold 1000 bitcoin on ledger or a casa is the dumbest think I have ever heard.
1
50
Released 8 days ago - the predictions are uncannily accurate youtu.be/wYOnlIGViRs?t=3712 @honestmoneyshow
2
2
267
“Nodes are the visionaries” 🎯@GrassFedBitcoin
1
2
57
The collective nodes = Theoden
11
Education must be taken to the next level. Self custody of private keys is not enough. Knowing that you have knowledge and input into the generation of private keys is the next level of sovereignty to be communicated.
33
Does divide and conquer work on an anti fragile system?
30
Because hashrate and node count are irrelevant 🤦‍♂️
One integrated view of the Bitcoin market and network. The Bitcoin dashboard brings price, performance, liquidity, volatility, valuation, sentiment, adoption, and security into a single framework. Live at Strategy.com.
1
87
🎯
Replying to @Excellion
Come on man. There was a POLICY limit that was, nevertheless, followed strictly for years. There's a difference between changing a default in the reference implementation and a few individuals changing the setting themselves. It's a signal. You know the survivorship bias meme? The one with the plane? There's a similar phenomenon in cybersecurity and networking in general. The defaults of the network shape the messages that flow through it. But the thing is, you don't see the attacks or the network traffic that didn't get sent because the default was in place. It's the same concept as a fence around a facility. Sure, you can hop the fence. Or go to a section that isn't fenced, if you want force the analogy a little further. But it's effort. Effort and friction reduce security incidents. My position is that Core only thought about one perspective with the OP_RETURN limit and didn't recognize that the limit had other functions. Similarly, they didn't recognize that relay policy isn't actually a setting you can just engineer into perfection since we're dealing with humans. You can disagree with 110 supporters over the governance side all you want. You don't need to twist narratives to make your point.
1
61
Core fucked up so hard by merging a contentious policy default change, arrogantly assuming no one would be able to do anything about it
BIP110 supporters are saying that Core blew open OP_RETURN. They didn't. They just removed a sign. Bitcoin's real OP_RETURN limit isn't 83 bytes or even 100KB. Those are policy. You can think of them as speed-limit signs each node chooses to post. The real limit is ~1MB. That's the law of nature, or consensus rules. Think of it as the speed of light, 299,792,458 m/s. A fixed constant. No dev, no miner, no config flag moves it. OP_RETURN data is non-witness data, 4 weight units per byte. Fill a whole block with it: 4,000,000 ÷ 4 = ~1,000,000 bytes. That's the real limit. It was the limit before v30 too. This means the 83-byte cap was never Bitcoin's limit. It was a sign posted in front of a road that was always ~1MB wide. And miners were already driving past it, accepting big non-standard transactions directly, bypassing the mempool entirely. All v30 did was take the sign down. Default datacarrier size went from 83 to 100,000 bytes. Should they have taken the sign down? That's debatable, but it also isn't relevant (outside of angering some people). However, there were zero consensus changes. Not a soft-fork. Not a hard-fork. The set of valid blocks is identical before and after. So when someone says "Core changed Bitcoin," ask them: which consensus rule changed?
2
11
289
testing, testing 123, is this thing on?
78
Bro I know that wasn’t you at your most diplomatic, but damn was it entertaining. That Gary Cardone impression 😂 @GrassFedBitcoin youtu.be/yCKiGzGc_2Q
1
53
C’mon don’t tell me there isn’t something fishy going on
Replying to @Excellion @adam3us
Samson, last fall you told two podcasts (clips attached) that Core had - "a lot of structural problems with the organization itself" - developers with "ulterior motives" doing "conflicted" things - a "laundry list": "backstabbing, internal politics, brigading, canceling people." You also said: "you'll get it eventually. I think it'll come to light." You knew about the issues, but waited for someone else to do the work. I did the work documenting this. Three articles (so far). IRS filings, SEC exhibits, PRs, IRC logs, archives, right of reply. The very structural and governance-related problems, documented line by line. My articles assert none of the motives you asserted. You went further on those podcasts than my articles ever go. And now that this all has come to light, meticulously sourced and documented, your response is: "some individuals doing questionable things," a little "cliques and groupthink", and a retweet of Adam calling the process "uniquely robust to special interest lobbies." This is the exact opposite of your own diagnosis on those podcasts. It's very strange to describe and predict that serious and very problematic dirty laundry will air, then call it a non-issue and join Adam's handwaving and misdirection when someone airs it.
1
48
They sure did turn on the make Twitter work properly switch
28
In my day job I work with tons of data. It piles up resulting in a number of costs. We should not invite these problems to our money ledger.
63
This is exactly what it’s about. Running a full node MUST become affordable for everyday people again. Moores law will sort only half of that deal out. To those dismissing the existential risk framing - how do you think Bitcoin remains decentralised?
Pro BIP110 argument that I like
59
Who on earth would want to enforce a rule that stops (relatively) large amounts of data being relayed then stored forever on Bitcoin?!
38
Being a free market, fee rates are dynamic. The stupidity of taking a snapshot in time and saying everything is fine is the same as saying Bitcoin is dead because of it’s current price in fiat.
After a decade of blockspace fears and non-monetary-use panics, Bitcoin still has no spam problem. Fees are 1 sat/vB: anyone can move any amount globally with immediate processing for ~$0.30. The free market has always solved Bitcoin’s blockspace challenges. $BTC
1
7
506