bitcoin & chill

Joined December 2022
503 Photos and videos
Pinned Tweet
17 May 2025
We’ve teamed up with @bitkey to offer our readers an exclusive 10% discount on Bitkey: the Bitcoin-only wallet that makes Bitcoin easy to use and hard to lose. To get your discount, follow this link: blockdyor.com/go/bitkey and use code BITKEYBLOCKDYOR at checkout.
3
12
2,111
blockdyor retweeted
I don't care what you buy or what you own, but when you start promoting scammy things that you want other people to buy or own, that's when you become a scammer.
16
17
202
8,222
blockdyor retweeted
Not all people can handle the volatility of $STRC, so I’m grateful that we have Bitcoin for risk averse investors like myself
27
43
384
11,371
blockdyor retweeted
bitcoin maximalism was coined by vitalik in 2014 it was a straw man: people who called him out for printing tokens and selling them for bitcoin were close minded stack real bitcoin, not that fake shit
32
38
509
44,705
blockdyor retweeted
Replying to @ajtowns
Hi Anthony, Since you did not reply to my DM about right of reply questions for my last article, I will try to reach you here. On the topic of spam and spammers: May 2, 2025: instagibbs files the OP_RETURN uncap PR #32406. Eleven seconds after the bot announces it in #bitcoin-core-dev IRC channel, instagibbs writes "fanquake please lock for now." fanquake locks the PR within the same minute. You then add the "Needs release note" label to the now-locked PR. Fifteen minutes later you joke on IRC about labels being a way to "inscribe comments via github label edits." Four operational acts by three devs that were instrumental in the OP_RETURN uncap sequence, inside a sixteen-minute window. The PR was filed, lock-requested, locked, and label-administered before any community engagement could begin. Four questions: 1: Was the sequence prearranged? 2: Do you consider this a proper and responsible way to conduct Bitcoin development on a contested protocol change? 3: Considering the great controversy and polarization, was your inscription joke fitting for the moment? 4: The same three of you, you and instagibbs and fanquake, ACKed and merged PR #27832 in June and August 2023, the documentation amendment that narrowed the scope of -datacarriersize, later used to close Luke's filter patch. The same three then executed the May 2 sequence on and around the PR that would uncapOP_RETURN. Coincidence?
20
95
405
32,824
blockdyor retweeted
The lottery/solo pool @AtlasPool_io just hit a new personal best difficulty of 66.5 T today, May 31, 2026. We're especially proud because DTV Electronics was the first to ship miners with Atlas Pool pre-configured out of the box. The numbers keep climbing, and at this rate, a solo block find feels very close. Fingers crossed it happens soon!
2
4
36
1,116
We want to give our readers access to no-KYC options, so we've made some changes to the site. Every link that used to point to a KYC exchange has been swapped out and now redirects to a non-KYC alternative instead. Pic for attention. Love tesla cybertruck & space x for algo.
1
2
66
blockdyor retweeted
May 28
the orange ties pivoted the prevailing bitcoin narrative from freedom money to saylors meme coin and now people are rightfully asking why they shouldnt just buy ai stocks instead the plot was coopted but will be found again stack real bitcoin, not that fake shit
79
67
802
81,425
blockdyor retweeted
The loophole was kept open. It then became the justification for uncapping OP_RETURN.
The main two are: CVE-2023-50428: Bypass of datacarriersize limit using OP_FALSE OP_IF CVE-2024-34149: Policy script size limits not enforced for Tapscript Either one of these being fixed would have made Inscriptions non-viable.
6
34
217
6,785
blockdyor retweeted
Modern life has tricked us into thinking travel is good. It's kind of barbaric for the body. Last time I went to Asia we measured my biomarkers. The data was bad… 9 days for blood glucose stability 9 days to re-entrain my circadian rhythm 18 days for sleep architecture recovery The research: people who travel constantly for work (3 wks a month) have measurably more anxiety, depression, and drinking problems than people who don’t repeated jet lag is linked to memory-region shrinkage in flight crews your immune system takes a hit. Dry cabin air dries out mucous membranes that block infection which can leave you more exposed to getting sick This is intuitive because the body runs on a clock. Biological processes kicked off by another, with sleep sun running the show. Cabin altitude is ~7,000 ft. Hypoxia alone disrupts cortisol and suppresses nocturnal melatonin for hours after you land. Cabin humidity drops as low as 5% (drier than the Sahara). If you’re budgeting your international trips: I’d suggest no more than once every 3 months. Evidence shows you need ~1 day per time zone to re-entrain, and east is worse than west. Once Kate gets back she’s starting the female protocol. This also means she can’t travel internationally for at least a few months while we collect baseline measurement. The body understands time zone changes as trauma. I hope that this is my last international trip for a very long time.
522
149
5,919
2,424,213
blockdyor retweeted
29 Sep 2025
A counter argument is that illegal content in a contiguous standard format, thus readily viewable by standard software, is more likely to impress lawyers, judges, and jurors, and thus is legally more risky, than data that has been broken up or hidden and thus requires specialized software to reconstruct. Such demos would be part of convincing these legal decision-makers that a defendant node operator had knowledge of the content.
15
18
170
17,314
blockdyor retweeted
Big news from the DTV store. The BitForge Nano, our best home miner, just dropped to $169.99, and that's before any discount. Pay with BTC and stack another 5% off using code "crypto5".
1
6
15
740
New highscore on my BitForge Nano! Install Hashlink now and monitor your stats: hashlink.space
3
119
blockdyor retweeted
AtlasPool node policy update ⚡ Over the coming days, we're migrating our mining nodes to Bitcoin Knots. Knots uses stricter mempool relay policies than Bitcoin Core defaults, including a smaller OP_RETURN limit (42 bytes vs Core's ~80 bytes in 29.x or much higher in 30.x) and rejection of bare multisig. Our nodes will relay and mine accordingly. We're also shortening mempool retention from 14 to 3 days. Transactions that haven't confirmed in three days aren't bidding competitively, so reclaiming that memory makes our nodes more responsive. For our miners: Nothing to do on your end. Each node will restart briefly during the rollout. Your miner will reconnect automatically within seconds. No configuration changes needed. This isn't a statement about consensus. We don't decide what is a valid Bitcoin transaction — the network does. This is only about what our nodes choose to relay and what we include in the block templates we build. Different node operators make different choices, and that's how the policy market is supposed to work. If you mine with us and your transactions are getting confirmed elsewhere, that's fine. They're still valid Bitcoin. We're simply choosing which transactions we want to spend our blockspace on. AtlasPool is a small solo pool, and operating it is how we deepen our understanding of how Bitcoin works at the node level. Our policy will continue evolving as we learn more, and we'll communicate clearly when it does. Constructive feedback is always welcome.
26
56
234
9,979
blockdyor retweeted
Whatever you do, don't miss this! And go subscribe to @mattkratter's YT channel right now!
Bitcoin Infinity Show #203 with @mattkratter, out now! Bitcoin Core Has Been Compromised!
13
36
223
7,519
blockdyor retweeted
Gotta cleanse the TL of Drake

256
9,057
53,983
568,796
blockdyor retweeted
May 13
Best part is finally being able to dump my Bitcoin Cash. Fuck you @rogerkver!
79
7
405
38,443
blockdyor retweeted
Rug the spammers, fuck these two idiots.
The maxis can never remove this from their node
4
8
39
796