hodlonaut

#Bitcoin Taco pleb. Hodling. Always looking to learn. Speaking my mind. Editing http://citadel21.com

Public Key

npub1cjw49ftnxene9wdxujz3tp7zspp0kf862cjud4nm3j2usag6eg2smwj2rh

NIP-05 Address

Profile Code

nprofile1qqsvf82j54enveujhxnwfpg4slpgqshmyna9vfwx6eace9wgw5dv59gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsc4r7my

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1cjw49ftnxene9wdxujz3tp7zspp0kf862cjud4nm3j2usag6eg2smwj2rh

Show more details

Last Notes

2026-03-13 16:11:53 UTC

- reply

How Bitcoin Core's developer selection, developer funding, and developer moderation were consolidated under a single informal architecture
#naddr1qq…8qzn

2026-03-12 07:41:45 UTC

Human nature insures there will never be a time when Bitcoin does not need to be defended and fought for.
Complacency is an attack vector.
Eternal vigilance is the price of liberty.

2026-03-11 07:29:47 UTC

By repeatedly adjusting default mempool policy to match what miners will accept anyway (large OP_RETURN uncapped because “they’ll just mine it via bypasses like Libre Relay, or direct APIs”), we are implicitly conceding that miner greed + economic incentives are the ultimate rule-setter, not node-enforced principles.
Meaning a (cleverly hidden) capitulation of Bitcoin as a decentralized project.
You could say that the “CENSORSHIP!” argument from Core and their supporters on the concept of nodes filtering is a roundabout way of critizing decentralization itself.
Nodes were always supposed to be the sovereign check, they decide what they accapt and relay.
When we keep loosening policy to align with whatever is the current grift “use case”, and by extension what is short term profitable for miners, it trains the entire ecosystem to treat restrictive node behavior as pointless theater.
Over time this hollows out node sovereignty: running a full node becomes more about passively observing the chain that miners + L2s + data-spammers have already decided on, rather than actively enforcing a monetary-first standard.
As a cuck bonus it also leads to higher resource costs for every honest node (bandwidth, RAM, storage) à fewer independent verifiers in practice
Decentralization starts looking like a performance act. Miners produce the blocks, a handful of relays and L2 sequencers steer the flow, and nodes just… validate after the fact.
It’s not a hard-fork capitulation (consensus rules haven’t changed), but it is a cultural, philosophical and operational one. The most profound capitulation in practice.
The philosophy flips from “Bitcoin should resist non-monetary garbage even if it costs us some short-term fee revenue” to “whatever pays miners gets standardized because resistance is futile.”
Once you accept “miners will do it anyway” as the justification for policy, you’ve already handed the character of Bitcoin over to the highest bidder. Nodes stop being the immune system and start becoming just a polite audience.
The OP_RETURN uncap looks a lot like another quiet step toward a two-tier network (miners + insiders set the tone, everyone else just watches. Keep doing this and running a node risks becoming a branding exercise instead of the actual source and guarantee of Bitcoin’s decentralization.

2026-03-10 12:58:34 UTC

- reply

Yes

2026-03-10 11:32:58 UTC

- reply

Spent some time researching this
#naddr1qq…3g0q

2026-03-05 16:26:50 UTC

In July 2023 and September 2023, two pull requests hit the Bitcoin Core repository.
One tried to tighten data limits. One tried to remove them entirely.
They were moving in opposite directions. The people behind them knew what they were doing.
***
PR #28130, July 2023: Peter Todd files to remove the OP_RETURN mempool limit entirely.
PR #28408, September 2023: Luke Dashjr files to extend -datacarriersize to cover the SegWit/Taproot inscription loophole.
Luke tightening. Todd eliminating. Both active at the same time.
***
Todd NACKs Luke's PR, calling it censorship.
PR #28408 is killed. PR #28130 is closed without adoption — but it has done its job: established the position publicly and seeded the argument for next time.
Kill the defence. Advance the attack. The pincer has two arms.
***
What Todd does not disclose when NACKing Luke's patch: he operates Libre Relay.
Libre Relay is a direct-to-miner relay service routing non-standard transactions — including inscription-heavy ones — to miners, bypassing mempool policy entirely.
***
Todd's argument: filters are ineffective because miners include non-standard transactions anyway.
Libre Relay is part of the infrastructure that makes this self-fulfilling.
He built the bypass. Then cited the bypass as proof limits don't work.
***
April 2025: Todd files PR #32359 to remove the limit.
He later admits on Stacker News:
"This pull-req wasn't my idea. I was asked to open it by an active Core dev because entities like Citrea are using unprunable outputs instead of OP_Return."
***
Citrea: a VC-funded ZK-rollup whose business model needed more on-chain data storage.
The PR was not an organic expression of Todd's technical views.
It was a brief, handed to him by an unnamed active Core developer, to solve a corporate client's problem.
***
Samson Mow calls it "PR laundering" — routing through Todd to produce the appearance of independent initiative.
Antoine Poinsot (Chaincode Labs) connected to early discussions.
The same Poinsot who disputed Luke's CVE in October 2024. Both ends of the sequence.
***
Jameson Lopp publicly advocates for the PR.
He does not disclose he is an investor in Citrea — the same company whose data needs triggered the PR.
***
The PR draws 423 thumbs-down against 105 thumbs-up.
Ava Chow had stated publicly in December 2023: "If it is controversial, then we don't touch it."
June 9, 2025: Gloria Zhao merges it anyway.
***
PR #32406 does something beyond uncapping OP_RETURN.
It removes -datacarrier and marks -datacarriersize as deprecated — the switches letting node operators filter data-carrying transactions from their mempools.
Luke Dashjr authored those options in 2014.
***
The justification: the flag is "obsolete" and a "footgun."
Gloria's announcement tweet confirmed the deprecation explicitly.
The escape hatch was being closed behind the change.
***
Under sustained pressure, Core maintainer Ava Chow reversed the deprecation via PR #33453 — merged hours before the v30 release window in October 2025.
User configurability preserved — for now.
The 100KB default was not reversed.
***
Thirty-one Bitcoin Core contributors sign an open letter supporting the merge.
The letter uses the word "censorship" to describe any opposition.
***
Gloria's public statement on X:
"Demanding that Bitcoin Core prevent certain transactions from being mined reflects a misunderstanding of the relationship between open source software users and developers."
She deletes the account on May 15, 2025.
***
The community response is the largest organised opposition to a Core change since the 2017 block size wars.
Bitcoin Knots — Luke's alternative implementation — surges from ~2% of the network to over 21%.
5,114 Knots nodes at time of v30 release. BitRef data confirmed.
***
Dennis Porter, who had raised over $200,000 for Core developers:
"My faith in their work is now broken. I will no longer be financially supporting Core development."
***
Nick Szabo — pioneer cryptographer, silent on social media for five years — returns for v30.
"I strongly recommend not upgrading to Core v30."
He also flags criminal liability for node operators storing illegal content they can no longer remove.
***
Bitcoin Core v30 ships October 11, 2025.
Within weeks, downloads are pulled. The release contains a bug capable of deleting Satoshi-era wallet.dat files during migration — potentially destroying funds held by early holders who had not backed up separately.
***
A release delayed for weeks due to governance controversy shipped with the most serious wallet safety bug in years.
Knots supporters noted the contrast immediately.
***
One supporter's statement is worth preserving.
Ark Labs Ecosystem Lead Alex Bergeron stated publicly he intends "to use all of the additional OP_Return space and WILL use it to make Bitcoin more like Ethereum, except better."
A proponent confirming what critics warned.
***
2023: reject Luke's patch. 2025: merge the uncap using the open loophole as excuse.
2021: try to remove Dashjr as BIP editor. 2025: mute him on the OP_RETURN PR.
2014: Luke builds the configuration option. 2025: try to deprecate it in the same merge.
Not a series of independent events.

2026-03-05 16:22:09 UTC

VC money is a helluva drug.
Symptoms include:
- sudden inability to define the word "spam", previously straightforward concept, now philosophically complex
- the word "censorship" begins to apply to things that were previously called "node policy"
- previously held view that "arbitrary data does not belong on a monetary ledger" becomes "who are we to say what belongs?"
- strongly held technical positions develop a mysterious flexibility

2026-03-05 09:42:35 UTC

In 2025 Bitcoin Core removed a decade-old mempool policy default — a configurable limit on how much non-financial data nodes would relay. OP_RETURN was effectively uncapped.
Not a consensus rule. A default setting. But defaults govern what most of the network does. Which governs what miners see. Which governs what gets mined.
The justification: it wasn’t working anyway, data was getting in through a loophole.
What wasn’t disclosed: that loophole had been deliberately kept open.
Here’s the documented sequence:
2014: Luke Dashjr creates the -datacarriersize configuration option.
Its description: "Maximum size of data in data carrier transactions we relay and mine."
Broad by design. Covers all transaction components. That's the operative text for ~10 years.
***
Late 2023: Developer Marco Falke changes the -datacarriersize description in v26.0.
New wording inserts "scriptPubKey" — outputs only.
Inscriptions use the input/witness section.
That single word change surgically excluded inscription spam from the option's scope.
***
That change was not a typo fix.
AJ Towns ACKed it.
The diff is documented. The before/after screenshot exists.
The configuration option Luke built to protect the network had its scope quietly narrowed — while he was still maintaining the project.
***
Sept 2023: Luke submits PR #28408.
Purpose: extend -datacarriersize to cover the SegWit/Taproot witness loophole inscriptions were using to bypass existing limits.
A direct fix. Using the exact configuration option he built. Nine years earlier.
***
Gloria Zhao rejects it.
On-record comment: "History of this config option suggests datacarriersize is meant to limit the size of data in OP_RETURN outputs, so this statement is untrue."
She cites curated historical PRs to support the narrowed reading.
***
She does not mention that the operative description in the codebase had been changed in v26.0 by Marco Falke.
AJ Towns — who ACKed that documentation change — then gives an Approach NACK on Luke's patch.
The same man enabled the rejection and then ratified it.
***
Peter Todd also NACKs. Calls Luke's patch "censoring" transactions.
He does not disclose he operates Libre Relay — a direct-to-miner relay that routes inscription transactions around mempool policy.
He built the bypass. Then called closing it censorship.
***
PR #28408 closes. 11 Concept NACKs vs 9 Concept ACKs.
The loophole remains open.
Jan 5, 2024: Luke opens Issue #29187 and formally designates the bypass as a security vulnerability: CVE-2023-50428.
"Active exploitation... very harmful to Bitcoin even today."
***
Oct 2024: Contributor darosior disputes the CVE.
"The large majority of contributors disagree this is a security vulnerability. I believe the CVE system is being abused."
Next day, achow101 closes the issue.
The vulnerability is officially declared not a vulnerability.
***
April 2025: Peter Todd files PR #32359 to remove the OP_RETURN limit entirely.
He later admits: "This pull-req wasn't my idea. I was asked to open it by an active Core dev because entities like Citrea are using unprunable outputs instead of OP_Return."
***
Citrea: a VC-funded ZK-rollup whose business model needed more on-chain data storage.
Jameson Lopp publicly advocates for the PR.
He is an investor in Citrea.
This was not disclosed.
***
Samson Mow calls it "PR laundering" — routing through Todd to fake independent initiative.
Antoine Poinsot (Chaincode Labs) connected to early discussions.
The same Poinsot who disputed Luke's CVE in October 2024.
He sits at both ends of the sequence.
***
June 9, 2025: Gloria Zhao merges the uncapped OP_RETURN change.
The primary public justification: inscription data via the witness loophole is less prunable, so OP_RETURN should be uncapped to redirect it.
The harm reduction argument.
***
That argument is entirely dependent on the witness loophole remaining open.
If PR #28408 had been merged in 2023, the loophole would be closed.
The harm reduction argument would not exist.
It would have had nothing to reduce harm from.
***
The person who rejected the patch that would have closed the loophole is the same person who merged the change that used the open loophole as its justification.
That is not a coincidence.
That is a sequence.
***
The last entry in Luke's closed CVE issue reads:
"glozow mentioned this on Jun 9, 2025 — policy: uncap datacarrier by default #32406"
The issue opened to fix the vulnerability referenced from the PR that exploited the unfixed vulnerability.
GitHub closes the loop.
***
Every step is documented:
→ Docs narrowed (v26.0, ACK: Towns)
→ Patch rejected using narrowed docs (Zhao, Chow)
→ CVE designated (Luke, Jan 2024)
→ CVE closed (darosior, achow101, Oct 2024)
→ Removal PR commissioned (Todd)
→ Uncap merged (Zhao, Jun 9 2025)
***
Adam Back claimed the narrowed definition "was always the original intent."
The original 2014 text has no mention of OP_RETURN, scriptPubKey, or outputs.
That restriction was introduced in v26.0.
He treated an amendment as original intent.
***
The PR had 423 thumbs-down against 105 thumbs-up.
Ava Chow had said publicly in Dec 2023: "If it is controversial, then we don't touch it."
It was merged anyway.
Luke Dashjr was muted on the PR. Bitcoin Mechanic was muted on the PR.
***
Bitcoin Core's response:
→ 31 devs sign a letter calling opposition "censorship"
→ GitHub moderators mute the loudest critics
And:
→ Nick Szabo breaks 5-year silence: "run Knots"
→ 22% of the network switches to alternative software
***
The documentation was rewritten.
The patch was rejected using the rewrite.
The loophole was kept open.
The open loophole became the justification.
The justification enabled the uncap.
The person who rejected the patch merged the uncap.
All on the public record.

2026-02-25 21:39:57 UTC

“So then, the (21M) cap is irrelevant when Jane Street can fabricate unlimited synthetic supply through undisclosed derivatives stacked on top of its own ETF inventory.”
Now we know the answer to the price mystery. And color me not surprised.
Paper bitcoin…
https://x.com/1914ad/status/2026757796390449382?s=46&t=DG1JEc-EXQnoc72Rmx9dOA

2026-02-24 18:37:17 UTC

The main justification from Core for the OP_RETURN uncap is “harm reduction”.
The argument is that inscriptions done via the segwit/taproot hack have potential to do more damage than inscriptions via OP_RETURN.
Thing is, LukeDashjr made a PR in 2023 to fix the vulnerability introduced by taproot.
PR #28408
It would “effectively limit arbitrary data carried via newer methods (including SegWit witness data and Taproot scripts), which inscriptions/Ordinals were using to bypass the existing OP_RETURN-based limits and embed larger payloads.”
If that had been merged, the current harm reduction narrative wouldn’t even be there.
It wasn’t merged. Core didn’t want it.
Peter Todd was among those who Nacked it with this rationale:
“The transactions targeted by this pull-req are a very significant source of fee revenue for miners. It is very unlikely that minres will give up that source of revenue. Censoring those transactions would simply encourage the development of private mempools - harmful to small miners - while making fee estimation less reliable.”
Note the use of the word “censoring” to describe fixing a very recently introduced vulnerability that opened up for ordinals.
Self inflicted wound, willingly not patched up, used as rationale for a new self inflicted wound.
https://blossom.primal.net/8d8e4fac15dff2a096f76f085bfe8896123140592f4c0986b1b56a0dd44db04a.jpg
https://blossom.primal.net/53248fc0e9f32cbb552e594dffe933cec62bd994238636739b8cfc516b41cece.jpg
https://blossom.primal.net/4d0d1f2b17c55c4d2df2520bab7dfec3267868d144e81e7a56db93e6546bf111.jpg
https://blossom.primal.net/05bdf3aeb67290ba180744d593fb9a0de5752bb0aedfd27a51ab383125e0bc6f.jpg

2026-02-24 11:11:13 UTC

- reply

You fail to understand the difference between x and 1200x? And cook that down to a lie about me being ignorant about the existence of op_return’s existence since inception?
Great jobb mRhOdL 👍
And yes, users can change the default, but very few will.

2026-02-24 10:48:11 UTC

- reply

Working on it.

2026-02-24 10:42:09 UTC

https://blossom.primal.net/5c68d995201ae84d0731c4c50d836cb9b63d861e8450712c097c8df94a7e7572.jpg

2026-02-22 10:16:13 UTC

Please, can someone explain to me how these two things can be logically compatible:
- the uncap (100kb) of op_return “doesn’t really matter”, and its value could basically just be decided by “tossing a dice”. It’s a nothingburger and in no way a philosophical pivot.
and
- the uncap being so important that it had to be forced through despite great opposition and controversy, predictably creating a civil war. And now the heels are being dug in harder than I’ve ever seen and people calling it out are labeled as “attacking bitcoin”.
https://blossom.primal.net/b123f8489c5b001370639cfbb4e0e1e94549d7247c39d76a7ad4875588059c1e.jpg

2026-02-22 10:03:20 UTC

- reply

The “pressure” as you call it, was there long before they decided to merge the op_return uncap. From developers on GitHub. And from the Bitcoin community as a whole.
A small contingent of core devs decided to arrogantly push it through anyways.

2026-02-21 14:29:12 UTC

- reply

Thanks. I agree

2026-02-21 11:36:33 UTC

- reply

If it really was irrelevant, that would make Core’s insistence on uncapping it, and predictably creating this chaos for no reason, even HARDER to explain

2026-02-11 09:54:05 UTC

Independent minded people who don’t bend to peer pressure used to be considered a feature, not a bug.
Core v30 changed that for some reason.
https://blossom.primal.net/b182bd6259653d16ad01225c6ba868dad9ded0989985a4f6c041ed3b5719527f.jpg

2026-02-10 16:51:13 UTC

A) I think v30, the rationale, the haste, the circumstances, the philosophical implications, the arrogance, the handwaving, the disdain for broad community outrage and more, shows beyond doubt that something is very wrong with Bitcoin Core and/or how it works right now.
B) That means I am taking a stand against it
C) This DOES NOT necessarily mean that I know for a fact BIP-110 is the best countermove, but it DOES MEAN that I think some form of strong action has to be mustered against it, if Core shows no willingness to accept they have acted recklessly and unwise, and start working to remedy the situation and heal the social fracture.
D) As of now I support BIP-110

2026-02-08 22:29:31 UTC

- reply

Solid argument there

2026-02-08 22:04:12 UTC

Is one of the main arguments against bip-110 that not enough people support it?
Would some of the “reckless” and “dangerous” criticism go away if support was much higher? And would that criticism then deservedly go towards Core and v30 instead?

2026-02-07 06:43:20 UTC

- reply

Why are you so retarded?

2026-01-28 21:39:59 UTC

What is even spam, they say. 🚩
The Bitcoin plebs never mattered, they say. 🚩
You’re not technical enough, they say. 🚩
There is market demand, they say. 🚩
You are still living with a 2011 to 2014 mindset, they say. 🚩
This is ALL FAQ stuff which has been rehashed, they say. 🚩
Principles is pleb slop, they say 🚩
There has been no philosophical shift in Core, they say. 🚩
https://blossom.primal.net/d0d6e430c8e0c352e8ef342a56860da7385dde19075cf0596054c201108dca3f.jpg

2025-10-01 19:42:38 UTC

What’s the sentiment on bitcoin nostr?
Core v30 or knots?
Or core v29 or older?

2025-08-08 21:13:51 UTC

My fiancé is making jewelry, and she’s pretty good at it.
https://www.instagram.com/reel/DMyDcPjtXAb/?igsh=anY2NWtnNXNseDB5

2024-11-16 21:34:10 UTC

I haven’t been this bullish and excited about the future in a long time.

2024-11-13 16:21:58 UTC

You didn’t get lucky.
You were smarter, had more conviction and bigger balls.
You earned this.

2024-11-03 20:51:03 UTC

I agree with Graham Hancock that humanity is a species with amnesia.
I will add that it seems like we’re also a species with dementia, since we manage to forget so quickly that communism and erosion of freedom is a very bad idea.

2024-11-03 20:23:30 UTC

- reply

Why is that edgy?

2024-11-02 15:06:24 UTC

I really like non-insane people!

2024-10-23 11:02:04 UTC

- reply

Absolutely not. Why would the elite consider him an enemy and viciously attack him if he was part of them?

2024-10-23 10:43:12 UTC

- reply

Conviction that Elon Musk is somehow a grave threat to the world, despite being its foremost defender of free speech and being responsible for some of humanity’s greatest tech advances.
Based not on facts, but propaganda.

2024-10-21 11:43:07 UTC

I checked the bitcoin price so you don’t have to.
No change.
Still between 50k and 70k.

2024-10-19 10:22:27 UTC

https://m.primal.net/LarR.jpg

2024-10-18 08:18:22 UTC

- reply

You should see the signs very clearly then

2024-10-17 20:19:46 UTC

We need to talk about state spending.

2024-10-17 14:18:08 UTC

I hate to break it to you, but a communist totalitarian future will bring worse horrors than a presidential candidate shitcoining.
Zoom out. Look at the whole picture in front of you.

2024-10-11 16:00:51 UTC

Craig Wright is a fraud.

2024-10-11 15:57:25 UTC

Faketoshi back to suing developers it seems…
Lock this man up.
https://m.primal.net/LScn.jpg

2024-10-11 10:55:03 UTC

- reply

Speaking of… about to pick up another batch today 🔥

2024-10-06 09:42:50 UTC

The hodl meme transcends Bitcoin. It’s about conviction in the face of adversity. Following through. Being the rock that the waves keep crashing over.
Hodl on to the truths that resonate with you. Ignore the crowd. Stay the path.

2024-10-05 20:08:00 UTC

There will soon come a time where everyone pretends they were always bitcoin maxis.
Because bitcoin maxis were right, are right and will continue to be right.

2024-10-05 20:04:30 UTC

A small workout is better than no workout. A small stack is better than no stack. Small steps in the right direction are better than no progress.

2024-10-03 19:09:42 UTC

HBO should be taking notes
https://m.primal.net/LKJb.jpg

2024-10-02 20:22:57 UTC

If you believe no manipulation or shenanigans can happen because something is reGulaTed
https://m.primal.net/LIyG.jpg

2024-09-28 18:18:15 UTC

- reply

True :)

2024-09-26 12:27:39 UTC

On the same day, as part of the new city budget, it’s announced that
- Oslo will spend 9.5bn NOK (close to $1bn) on carbon capture
- local taxes will increase 63% over next 3 years
Hard to believe, but this is where we’re at. People being made poor on the “green” altar.
https://m.primal.net/LCiH.jpg
https://m.primal.net/LCiI.jpg

2024-09-24 11:54:12 UTC

- reply

🙏

2024-09-23 19:44:47 UTC

Forgot I had a smoothie in my bag through security check in Manchester airport. Serious faces, questioning, sample taken from smoothie and tested.
UK doesn’t look kindly on free speech and smoothies these days. 🤷‍♂️

2024-09-20 19:39:09 UTC

Polish food in Oslo again. Polskie Jadło.
Refreshing to find real, based food for a decent price. 🤤💪
https://m.primal.net/KvyI.jpg

2024-09-19 10:36:40 UTC

How and why did I have such rock solid conviction that I SHOULD buy bitcoin and that i SHOULDN'T take the mRNA jab?
Because I didn't blindly follow the herd, but did my own research and critical thinking instead.
Highly recommend this approach.

2024-09-18 18:29:13 UTC

High time preference speculation on the ultimate low time preference asset 🤦‍♂️

2024-09-13 13:52:38 UTC

At this rate, Saylor is going to ruin $58k for all of us.
Egoistic buying and hodling with no regard for the people wanting more cheap sats.

2024-09-10 19:43:35 UTC

Thankful for all the people contributing code to further the bitcoin and nostr mission.
Thank you! 🧡💜

2024-09-10 11:41:56 UTC

This changes everything.
https://m.primal.net/Klqc.jpg

2024-09-09 20:10:28 UTC

- reply

Well said, I agree

2024-09-07 16:38:44 UTC

Our experienced reality is largely a projection of our own mind.
Don’t let the psyops dictate it.

2024-09-07 10:02:19 UTC

GM
Coffee tastes best from bitcoin cups!
https://m.primal.net/Khto.jpg

2024-09-05 18:14:49 UTC

Propaganda exists on all sides.
You can’t find truth while cucked by power, regardless of which leaders you simp for.

2024-09-01 16:49:20 UTC

Commies hate zaps

2024-09-01 14:44:05 UTC

Absolute scarcity cannot be engineered in the open. It needs to sneak up on us. Grow roots in obscurity.
Organic decentralization.
Its true power and promise slowly unveiled. Until all of a sudden it is apparent. Non negotiable.
We had one shot, and it worked.

2024-08-31 12:24:20 UTC

So...
Brazil is hunting down people who wants to share information on X now?
That's a tad dystopian, no?

2024-08-28 16:02:12 UTC

Low transaction fees are great.
Cat jpegs onchain didn’t catch on I guess.
But..
It is also indicative of many people using custodial services instead of being sovereign key-holding bitcoiners.
Which enables fractional reserves, paper bitcoin and price manipulation.
https://m.primal.net/KRvA.jpg

2024-08-27 11:38:45 UTC

- reply

Same as with nodes. Run your own if needed. They can play whack a mole ad much as they want

2024-08-27 07:32:35 UTC

Nostr is having a growth spurt right now.
As censorship and state violence against freedom of speech increases, nostr will grow faster and faster.

2024-08-26 20:55:26 UTC

This is not going to end well.
https://m.primal.net/KOWS.jpg
https://m.primal.net/KOWT.jpg

2024-08-24 12:18:10 UTC

Fiat food maxis think this ingredient list is fine and normal.
25 E-additives 👀💀💩
https://m.primal.net/KKje.jpg

2024-08-24 11:30:17 UTC

I don’t know where we are heading as a world. Sometimes a good outcome seems impossible.
But there are many good outcomes along the road we travel. Tons of meaning and joy. Endless opportunities to focus on good and appreciate it.
And in the end maybe that’s all there is to it. To craft our own small lives with intention and bringing good into our world by focusing on it.

2024-08-23 11:34:59 UTC

Whenever I want to feel bad, demoralized and pissed off, I log on to X.
Nostr hits differently.
I hope it stays like that.

2024-08-22 18:32:36 UTC

Over the last years I’ve gradually pretty much eliminated seed oils from my diet.
It’s become so prevalent in all kinds of processed foods, that many people get tons of it without realizing.
Low hanging fruit for better health is to eat less processed stuff.

2024-08-11 10:32:11 UTC

The first thing UK citizens see after posting wrongthink on Facebook, and the last thing they see before being put in the dungeon.
https://m.primal.net/JvwM.jpg

2024-08-08 21:27:54 UTC

Ok, hear me out…
Alcohol is a shitcoin

2024-08-07 09:28:23 UTC

- reply

He really is a king among clowns

2024-08-06 14:35:22 UTC

- reply

His slack

2024-08-05 09:36:46 UTC

GM
What a great day to be alive!

2024-07-16 16:35:48 UTC

Loving Craig’s website right now.
And it stays like this for 3 months.
https://craigwright.net/
https://m.primal.net/JSxk.jpg

2024-07-16 16:24:46 UTC

- reply

Cool, would’ve liked to hear that radio report

2024-07-13 14:55:56 UTC

Spent the day in the sun.
Didn’t put harmful chemicals on my skin.
Because the sun is my friend.

2024-07-13 09:16:17 UTC

- reply

Yup, weird is fine.
Why the need for extra labels like non-binary and neurodiverse though?
Human should do.

2024-07-06 21:51:24 UTC

Ribbing on the Hardanger Fjord 🇳🇴
https://m.primal.net/JJfh.mov

2024-07-02 09:52:35 UTC

If we’re friends and I don’t follow you here, please let me know

2024-05-03 21:05:47 UTC

- reply

Thanks!

2024-05-03 21:03:48 UTC

- reply

Thanks :)
Yeah, real chance he goes to jail

2024-03-24 13:46:42 UTC

- reply

Torn, flipped and protruding meniscus

2024-03-14 13:14:39 UTC

The judge just ruled from the bench.
CRAIG WRIGHT IS NOT SATOSHI NAKAMOTO
Further findings of fraud etc will come in the written judgment.
Welcome to law.

2024-02-08 11:29:46 UTC

A weird thing is happening as I sit in court watching Craig make up ever more ridiculous stories.
It’s like my brain has developed its own augmented reality filter. Whenever I look at Craig, a big red clown nose appears on his face.
Not sure why this is happening 🤷‍♂️

2024-02-08 10:50:16 UTC

Day 4 of COPA vs Wright.
Rainy day in London, sauna as usual in the court room.
Looking forward to another full day of Craig being confronted with his forgeries. https://image.nostr.build/adbd538c5b4de902b039a389b7d5f229c0261318f932fa04ca5de8f0e41fcf1c.jpg

2024-02-07 14:02:24 UTC

Craig is getting crucified on the stand. Forgery after forgery presented and he can do nothing but keep repeating that the expert witnesses, including his own, are incompetent.
He has tried a couple of times to appeal to the judge with stuff like “you will understand m’lord as a learned engineer” when he attacks the experts. The judge only seems annoyed with it.
Still 4.5 days left of cross examination. This is a train wreck playing out.

2024-02-06 09:24:49 UTC

Getting ready to watch day two of COPA vs Wright.
On day 1, it came out that Craig had "found" a FOURTH tranche of evidence in the eleventh hour, after the three previous ones had been found to be forgeries, and now wanted to rely on those.
Today, the witness statement of COPA lawyer Philip Nathan Sherrell was made public, and it shows that the latest batch of evidence is unsurprisingly of the same quality as the previous three.
Most hilariously, Craig has submitted photos of a computer screen, supposedly sent to him by a mysterious lawyer "Mr Makaya".
Unfortunately for Wright, the photos show (among many other things) a google chrome icon with what seems to be Craig's picture, showing him as logged in.
Read the full witness statement here:
https://bitcoindefense.org/wp-content/uploads/2024/02/Twentieth-Witness-Statement-of-Phil-Nathan-Sherrell.pdf
It really tells the story of how absurd this has gotten. I'm surprised the Judge allowed this latest batch of "evidence", and can only surmise it's to avoid any opening for an appeal.https://m.primal.net/HawB.jpg https://m.primal.net/HawC.jpg https://m.primal.net/HawD.jpg

2024-02-05 13:47:48 UTC

I've been reluctant to use the Doctor title for Craig Wright, but with the sheer amount of his doctored evidence being unveiled by COPA, I'm about to change my mind. He earned it!

2024-02-04 16:50:27 UTC

- reply

Craig doesn’t have any assets

2024-02-04 15:51:09 UTC

- reply

I didn’t let it break me at all. I’m stronger and happier than I was when this all started. Thank you for the support!

2024-02-04 14:57:18 UTC

- reply

Maybe, if he had one single non-forgery as evidence

2024-02-04 13:47:42 UTC

- reply

Looking forward to that

2024-02-04 13:25:45 UTC

For context re: Craig Wright and Calvin Ayre and why there should be no mercy.
My life changed completely on March 29th, 2019. Almost five years ago now.
I had made several tweets, warning people about Craig Wright, and making my opinion about him clear. A matter of very public interest.
I was sent a legal letter on twitter DM, where it was made clear that I either had to apologize and acknowledge Craig as Satoshi, or they would file a libel case against me in UK.
When I didn't comply, Craig and Calvin put a public $5000 bounty on my identity and then firmly doxxed me after finding out who I was.
They proceeded to put private intelligence surveillance on me, that have tried to gain access to my social circle, both online and physically. Presence in 100s of groups. Monitoring my house. Producing regular, detailed reports on all my activity. Travelled where I travelled and so on. And god knows what else. This is still going on today.
I have been continuosly smeared and lied about on social media and in Coingeek, the publication owned by Calvin.
Threatened directly/personally with bankruptcy and worse by Calvin and his followers on twitter, with my real name, on countless occasions.
Anonymous phone calls with indirect threats.
My dad was fighting against cancer when this all started. I was dealing with constant legal pressure and threats throughout his fight. When he finally died late 2020, the legal pressure was at a peak and my funding situation was uncertain.
I've had to give up tons of private communication in discovery, to prove I had not been behind "an organized and vicious campaign against Craig."
I've had to turn down professional opportunities, since a good percentage of my bandwidth has been continuously occupied with defending myself legally. The amount of legal letters, hearings, appeals, judgments etc are beyond belief.
I've lived since 2019, with the constant knowledge that my house and belongings are on the line, and Craig's stated goal of bankrupting his enemies would be reality if I lost.
All the while I've tried to, and largely managed, to shield my child and family as well as possible, but I know all of this has put stress on them as well.
No mercy for these people.
Only Welcome to Law.

2024-02-04 12:00:55 UTC

The COPA vs Craig Wright trial begins tomorrow.
Finally, after all these years, a UK judge will rule on whether or not Craig is Satoshi and whether or not he is a fraud.
Quite absurd that it’s taken this long to legally establish something so glaringly obvious.
Welcome to law.

2023-12-17 11:01:56 UTC

- reply

Only L1 will have pristine and uncompromising soundness. We will have to accept trade-offs in scaling, and there’s nothing wrong with that.

2023-12-05 13:04:21 UTC

- reply

I’m late day two. No muscle or strength loss yet. (At the gym now) Didn’t notice it during other 3 day fasts either

2023-12-05 08:12:15 UTC

- reply

Flat teaspoon of table salt every day

2023-12-05 08:07:31 UTC

- reply

GM
Chipper bad. Bitcoin good.