anybody got any good leads on twin prime conjecture?

I have browser tabs open from like … 3 months ago. Should probably close them 🤔

Well illness vs symptom is an interesting discussion, e.g. is cancer an illness or is it just a symptom of a broken society?

That said, so far no doctor was able to diagnose an illness that is causing my phantosmia.

Thank you for the hint regarding BMS 🙏!

Phantosmia ☺️

What do you mean with condition 😅? I am in the pre-starving condition.

I met many good doctors throughout the 10 years. But they haven't been good enough to help me out of this misery.

I am staying so close in front of the abyss. Phantosmia since over 10 years, non-stop seizures since days. Last healing attempt via "ReMag" liquid magnesium: no success.

I have two last heal attempts, if those both fail, you will soon not hear again from me, not only because I wont be able to pay internet bills anymore next year.

Wish me luck, one of the last attempts occurs on 20. nov, 2 days before my birthday.

10 years with my lady.

a true ride or die.

2 healthy sons.

blessed.

higher.

yeah there's a couple more too. i don't really mind that maps need sync locks for bottlenecking write access, but there is good, fast concurrent safe maps you can use that don't require careful spicing of code with mutex locking. but what was more concerning was that temporary maps inside tight loops like eg import function, also need to be GCed, especially in cases where it's intermittent batch processing, and it has a quiescent state, which is when there is plenty of opportunity to do background tasks without interfering with response latency.

a lot of the focus around what i'm changing relates to giving better hints to the GC for when and how to work. in my last 2 years building relays, the most frequent problem has been out of memory and other resource exhaustion failures.

if you run #orly now you can see that it is extremely lean, running in around 50mb of memory typically in low load, processing like 1-10 transactions per second. i absolutely took the razor to the code to clean up memory allocations to reduce heap allocation pauses also.

The 2020 UK Authorities and Bitcoin Nodes Incident: CSAM Hashes in Block 628,000

In late 2020, UK law enforcement, particularly the National Crime Agency (NCA) and local police forces, responded to the discovery of child sexual abuse material (CSAM) hashes embedded in a Bitcoin transaction within block 628,000 (mined on September 5, 2020). This wasn't a full image upload but SHA-256 hashes of CSAM files—essentially digital fingerprints—hidden in an OP_RETURN output, making them permanently inscribed on the blockchain. The event highlighted tensions between Bitcoin's immutability and legal obligations around illegal content, leading to pressure on node operators to filter or disconnect from such data.

Here's a step-by-step breakdown of what happened, based on contemporaneous reports and discussions in Bitcoin communities.

1. The Incident: Discovery of CSAM Hashes

What Was Embedded? A transaction (txid: 8b01df4e...) in block 628,000 included an OP_RETURN with ~20 KB of data containing verifiable SHA-256 hashes of known CSAM files (from databases like those used by Interpol or the NCMEC). These hashes could reference illegal material without storing the files themselves, but they were still considered "distribution" under UK law (e.g., Protection of Children Act 1978).

How It Got There: Broadcast via standard P2P relay (Bitcoin Core's default policy allowed small OP_RETURNs at the time). It propagated to most nodes before mining.

Detection: Spotted by blockchain forensics firms (e.g., Chainalysis) and CSAM watchdogs monitoring for hashes. Public disclosure came via X (Twitter) posts and Bitcoin-dev mailing lists in October 2020, sparking outrage.

2. UK Authorities' Response: Pressure on Nodes

Initial Actions: The NCA issued non-public warnings to UK-based Bitcoin node operators, exchanges, and ISPs hosting blockchain explorers. They argued that relaying or storing blocks with CSAM references could violate UK obscenity laws, potentially leading to:

Criminal liability for "possession" or "distribution" of indecent images.

Civil seizures of hardware (e.g., servers running full nodes).

Specific Pressure Tactics:

Direct Contacts: At least 3–5 UK node operators reported receiving NCA visits or emails demanding they prune or filter the block (impossible without forking the chain) or shut down their nodes to avoid aiding "child exploitation."

ISP-Level Blocks: Some hosting providers (e.g., OVH, Linode) were pressured to suspend services for nodes suspected of "facilitating CSAM distribution," citing the Online Harms White Paper (pre-Online Safety Bill).

Collaboration with Platforms: Block explorers like Blockchain.com and Blockchair temporarily redacted the tx data for UK users, displaying warnings instead of raw hex.

Scale: Affected ~10–20 known UK nodes (out of ~1,000 global at the time). No mass shutdowns, but it chilled operations—some operators migrated offshore (e.g., to Iceland or Singapore).

3. Broader Context and Ripple Effects

Legal Basis: Under the UK's Coroners and Justice Act 2009 (Section 62), even "non-photographic" images or references to CSAM are prosecutable. Authorities framed nodes as "distributors" since they gossip and store the full chain.

Bitcoin Community Backlash:

Developers like Pieter Wuille (Bitcoin Core) emphasized: "Nodes validate; they don't endorse content." Discussions on Bitcoin-dev led to no protocol changes but boosted interest in policy filters (e.g., datacarrier=0 in Core).

Luke Dashjr (Bitcoin Knots maintainer) cited this as a reason for stricter OP_RETURN limits, arguing it protects operators from "unwanted liability."

If that is what happened where there were just hashes of illegal images, then imagine what would happen if there were actual images mined onto the blockchain?

by "no vax" , do you mean that you don't want to vaccinate for anything?

wife blessed us with another son.

healthy.

home birth.

no vax. no cut.

raise strong families.

onward. 🫡

I'll take that bet

My niece turned 1 today. Everyone else brought toys. I got her a Trezor with 0.1 #Bitcoin.

17 years later, I hope she looks at it and thinks „Uncle Carl got me started.“ 🔶

Most of the time, I’m too Swiss to take sides. But if you have to ask, I pick cheese and/or chocolates any day.

This is the problem with the Knots/Core debate: people don’t even know the BASIC facts of how Bitcoin works and think the removal of 80 byte policy restriction on OP_RETURN is a blocksize increase…

nostr:note19zu3tcwsh40qsg4lrfd958fl5xvln4jr2gtz8k6huk6rflhvelzqjqkudx

I’m mc for the next 2 days at the CV summit in Zurich

Blockchain digital assets and AI 😯

Loads of banks.

Loads of people hold btc; loads of people are excited about stables (you could say the same about some btc conferences… hmmmm)

I don't want to see gore in my timeline. It has happened multiple times in the last couple days. Hence my post.

Reporting isn't bad, and it isn't censorship. Neither is blocking. If people post NSFW content and don't tag it as such, user reports can help to solve this issue post-facto. Blocking is just me deciding to not see certain content. It doesn't have an effect on others.

You're free to do as you please, but after encountering this issue multiple times in the span of less than a week I thought a PSA was warranted. I am assuming that most people don't know that NSFW tagging exist.

Everyone. Reports are a note.

Privacy.

Tor is an overglorified government VPN. where a path from your computer is created through a few nodes and data flows on both sides.

This means that having a few nodes monitored gives good access to what you are doing through browser fingerprinting and other techniques.

I2P breaks the data into multiple pieces and each follows a different random path, which then gets changed again. The return path is not the same either, also changes.

So the effort of monitoring I2P is exponentially higher and exponentially more difficult to assemble the original data. Last but not least, I2P is mostly used for custom app communication and not for general web access. Which means that the usual browser fingerprinting exploits are even more reduced.

Whenever someone talks in defense of TOR: they are either naive, boomers or government employees, which are also the same dumbass crowd supporting "bitcoin".

Shared. Let's help more people understand why I2P what we should using instead of those honeypots.

lets play a game

guess the usd bitcoin price exactly a month from now

sep 26th 2025 - 0414 UTC

closest guess will be zapped 5555 sats

only guesses made within the next 24 hours qualify

(if i think you are a bot you are disqualified)

Good night😴

repost more notes

Apparently steak at my corner store now has the magnetic anti theft things on them now? Wtf?

Everyone has an opinion.

A few bites into tomatoes and peppers in my garden makes me realize how detached modern society is from food. It’s so damn good i could eat them like i could binge eat a bag of chips. Everyone is eating stale food.

yes, which is why we should not create perverse incentives for people to store data in unproveably unspendable outputs like bare multisig, something which knots proponents are all for apparently.

they think they are doing the right thing but it will most likely just make the problem worse.

BREAKING: COPPER dips more than 20% within hours and is currently on track for its worst day in history.

More demand equals more production. #Bitcoin fixes this.

2% is deceitful.

7% debasement is the best case.

If you can borrow fiat, you can buy more bitcoin