_kami_gawa
su-do

Public Key

npub1j4442yrhl9dfnxe68gk6jefachmmmd6a4e4p4t0s7fvck997r6gqkghe65

Profile Code

nprofile1qqsf2664zpmljk5envar5tdfv57utaaakaw6u6s64hc0ykvtzjlpayqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsvmrqpe

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1j4442yrhl9dfnxe68gk6jefachmmmd6a4e4p4t0s7fvck997r6gqkghe65

Show more details

Last Notes

2026-08-27 13:58:48 CEST

Fact: Lightning isn't going anywhere. It's the only decentralized scaling solution in existence.
It's complex because the problem it solves is extremely hard.

2026-08-24 12:10:17 CEST

You have no idea how secure a 256-bit private key is. You do NOT need multisig.
Influencers told you to use Coldcard. Now they’re telling you to use multisig.
Meanwhile, Satoshi’s coins are still secure in the most insecure address type (P2PK) and were probably generated on a

2026-08-24 11:53:03 CEST

The idea that schools should teach kids how to do taxes or how to make money is the dumbest shit ever.
Schools should teach kids how to think, how to abstract, how to reason through logic problems, how to imagine and dream.
Schools should give kids the instruments to wander.

2026-08-13 16:58:37 CEST

The fact that we do _not_ need an hardware wallet, was the lesson learned from the
@COLDCARD
shitshow.
Today is
@Trezor
, tomorrow it will be someone else.
You do not need an hardware wallet if you are just hodling.

2026-08-13 16:17:13 CEST

I'm sure many of you have seen these two posts side by side in your timelines.
Well, look at them again and cry while you reflect on the thousands of man hours wasted by these larping drama queen #bip110 assholes.
This attack on bitcoin has been no joke.
Learn from it.
I have.
https://blossom.primal.net/162296e8a7b4624f7c6c72a53ced379405e1fe792632289bb053a0e9994c463c.png https://blossom.primal.net/56229bc81babf86cc51141b8ea3772cd2ca64ecffeb031044e825c2ae3a35661.png

2026-08-13 16:13:57 CEST

Those ~70 bits make a real difference.
They push bruteforcing from “trivial” (MK3) into “painful but still theoretically possible.”
The entropy remains weak, just not catastrophic.
Has anyone actually cracked an MK4 using a seed that was generated on the device itself (not imported)?

2026-08-13 15:12:28 CEST

After a full dive into Mk4 today:
Mk4 keys are not enumerable like Mk3 keys at all. Thanks to the reseed, it’s basically impossible to bruteforce them even, if they have weak entropy.
When correctly set up, the private keys are so secure that they remain effectively uncrackable,

2026-08-12 13:59:38 CEST

About the Mk3 draining, attackers can choose different "cones" to look into for wallets to hack.
The weak Yasmarang RNG value is determined by a small state (pad + chip/mixer skip history).
A "cone" is just a hypothesis about that history, e.g: first boot vs later login vs weird PIN session.
Each cone is a slice of skip/space.
Wrong cone → almost no hits.
Right cone → mnemonics become enumerable.
That’s why wallets can still sit unexplored in other cones.
The attack can go on for years and still find utxos

2026-08-11 21:36:24 CEST

I remember Jimmy Song writing, on the first day of Ordinals: “The first one that forks loses, and they (the spammers) will surely fork.”
What I’m witnessing three years later feels like a lysergic experience.
People I once thought were smart now look like completely unhinged madmen.

2026-08-11 16:00:48 CEST

After carefully analysing and testing the
@COLDCARD
rng bug, I am quite sure the attacker(s) knew about the bug already and spent weeks if not months to enumerate some vulnerable wallets. The whole enumeration did not take 3 days (the delta between Kimi K3 release and the attack)

2026-08-09 22:45:31 CEST

Instead of buying dice on Amazon, go to your local boardgames store.
These guys will have amazing choice, dice that FEEL (and look) great, and they don't need to know where you live.
Support your local game store.

2026-08-09 22:42:45 CEST

- reply

retard

2026-08-09 22:41:35 CEST

Taproot Wizards - gone
BIP110ers - gone
Everything is going according to plan.

2026-08-09 11:33:01 CEST

mistakes by 110ers: arguing nodes control protocol changes and miners will capitulate. subtly wrong. the economic users control the protocol, via the market. they transmit their views by transacting with their economic nodes. 1000s of nodes with no economic use have no influence.

2026-08-09 10:21:00 CEST

If you belived that BIP110 was suddenly going to activate, you are retarded 😉 cheers

2026-08-09 10:20:26 CEST

Today was an excellent day for Bitcoin. It demonstrated perfectly that it worked as it supposed to work.

2026-08-06 15:18:49 CEST

The more you learn about Bitcoin security, the more you become a SeedSigner (or more broadly a general-purpose air-gapped computer) maximalist: generate the seed entirely offline with dice or other analog entropy, and ideally never load it onto a device that remembers or stores it.
Even when you spend, use a stateless device so the seed only exists temporarily in RAM and is wiped on power-off. Add a strong dice-generated passphrase and/or a geographically distributed multi-sig quorum, and you have ironclad security for your stack.

2026-08-06 15:18:13 CEST

Single sig. did not fail at all. What failed were pk generated by the wrong function.
The era or device-generated seeds is done.
Long life to human generated entropy.

2026-08-05 15:24:45 CEST

Watching the BIP110 crowd complain about their fork is getting embarrassing.
Lads, nobody cares. Go activate your fork today, switch the PoW as soon as you can, and move on.
Nobody is going to follow you.
The rest of us have more important things to do.

2026-07-31 10:16:33 CEST

I wasn’t around for the Mt. Gox disaster, but what’s happening with
@COLDCARDwallet
today is a catastrophe.
Self custody just took a serious hit.
Wen CTV?

2026-07-31 10:15:51 CEST

I am wondering how a company that makes money securing bitcoins, did not run a stupid LLM against their hardware wallet firmware to look for bugs.
Also, why the hell do ColdCards have a fallback insicure element that generates entropy wtf.

2026-07-30 12:06:20 CEST

#BIP110 people when the image is split into two pieces
https://blossom.primal.net/c2729645b57688c3c7e172b01d1992fd32d178ae32bcc02933d07964273d9db2.mp4

2026-07-30 09:06:20 CEST

50% of the blocks are #BIP54 compatible.
https://blossom.primal.net/5c0ba71294563591ef2f1ad9538872e95b7c9dfb2fd8db14317781d2d64c3014.png
https://bip-54.com

2026-07-29 17:41:44 CEST

#BIP54 (Consensus Cleanup) fixes 4 old Bitcoin consensus bugs:
- timewarp
- poison blocks
- Merkle quirks
- duplicate coinbases
I built a small dashboard + interactive simulator to explain them:
bip-54.com
Do you already know how the consensus cleanup works? #asknostr #bitcoin

2026-07-29 13:51:49 CEST

"The question isn't whether a proposal reduces spam, improves efficiency, or changes OP_RETURN limits. Those are implementation details."
Huge pivot. It literally is about exactly that. You/others argued the technical albeit poorly for months but let emoytios and clouded judgment interfere, and now that they went against you, you're suddenly against "implementation details."
"The real question is: who gets to shape Bitcoin's future?"
No. The real question is whether the network is robust enough to fend off an attack that lacks consensus. The answer is yes. You and every BIP-110 supporter are enemies of the neutral protocol.

2026-07-29 12:19:59 CEST

No bitcoiner cries harder than a former fighter pilot in spaces

2026-07-29 12:19:54 CEST

Strategy buying BTC and adding it to the large pool at Coinbase Custody does absolutely nothing to spread Bitcoin adoption, and actually helps build the honeypot for a future 6102 attack. Real Bitcoin adoption looks like self-custody of real BTC, plebs running nodes, plebs buying

2026-07-29 12:19:42 CEST

Imagine how dangerous it would be for Bitcoin if a minority could impose a fork on everyone.
What makes you think Saylor and Larry won’t try something similar, for example, to ban certain transactions or blacklist addresses?
Pro 110 should consider both sides of the coin.

2026-07-28 19:51:13 CEST

- reply

New one.
https://blossom.primal.net/1f62d274871891a8ae56f437e70042e18a6f14bd4c6c25e1779bb9f328ce6ceb.png

2026-07-27 21:18:11 CEST

Time preference is the most important concept nobody talks about. Hard money lowers time preference. Lower time preference builds civilization.

2026-07-27 21:17:49 CEST

"Big Bitcoin" is just another way of describing the economic majority. And because that economic majority is sufficiently decentralized, it's incredibly difficult to coerce into adopting a contentious fork. That's one of Bitcoin's greatest strengths.

2026-07-27 07:01:16 CEST

- reply

No taproot and cheaper than op return high resolution image
bitcoin-cli getrawtransaction c99ba3723689aa70d548b5188b3417f78c4f41a783f67d437810a209ee53d387|xxd -r -p|tail -c+1073>l.jxl

2026-07-26 14:16:34 CEST

The shitcoin market has been milked so much there isn't a single drop of milk left to drain lmao

2026-07-24 19:28:53 CEST

- reply

*lady

2026-07-24 19:03:39 CEST

- reply

"They are happening every single day now."
You are retarded

2026-07-24 13:30:48 CEST

- reply

Taproot has made it CHEAPER to spam but it's definitely not the center of the spam issue.
Why not disabling P2PK, bare multisig, fake pubkeys?
Also BIP 110 does NOT intend to disable taproot.
You are talking of one issue which is unrelated to the 110 fork proposal.

2026-07-24 13:12:56 CEST

- reply

Let’s imagine we successfully activate BIP110. Currently, the majority of spam comes from tiny OP_RETURN transactions that won’t be filtered out by nodes running BIP110.
So what this fork actually tackles is:
- The `if (false) { ...data }` inscription envelope
- Large OP_RETURN transactions.
Given that large OP_RETURNs are already rare and inscriptions have been mostly dead for the past two years, what happens the "day after" the fork?
We’ll likely see a new wave of inscriptions using a different envelope, paying more or less the same fees as today (since you can still get into a block for 1 sat/vbyte).
What did we actually achieve?
This is what I mean: spam is garbage and spammers are pieces of shit, but we need to reason logically rather than emotionally. What did we achieve other than proving we wasted time while spammers continue to mock us by spamming without any real disruption?

2026-07-24 12:58:39 CEST

- reply

I run Knots, I don't relay big op_return, I don't relay spam.
That's the right way IMO.
Also Ocean and SV2 are the solution to the spam issue and, more broadly, to the centralization of Bitcoin.

2026-07-24 12:56:28 CEST

- reply

You are completely off topic, your answer sweats anger.
Also bip110 is not related to anything you just wrote.

2026-07-24 11:57:36 CEST

- reply

I disagree, sorry.
I've spent years discussing spam. When we first came together (in that huge Twitter group chat), it was clear we did not want to fork. We knew from day one that spam is fought at the policy level, not through consensus.
Chris then came out with this fork proposal, which is flawed on many levels except for signaling disappointment from us, the plebs.
You don’t change a protocol just to express disappointment. As a developer, I’ve never done such a thing.
If you try to look at it without the anger over spam, you’ll realize that 110 is a terrible proposal.

2026-07-24 11:20:01 CEST

Stripping the emotion from the 110 fork debate, the proposal is technically useless.
No protocol should patch one specific issue that can be replicated countless other ways.
We have far bigger problems focus on what actually matters.

2026-07-24 00:17:03 CEST

Average pleb bought BTC in 201*, held, smoked weed, and is up 700%+. Memed hard, wrote “few” like maniacs, and fucked through the pumps.
Saylor & crew spent $60B trying to own the protocol, now down 50%, and still lecture us on what Bitcoin is.
Fucking losers. We shit on you.

2026-07-23 20:15:02 CEST

How to defeat the newly created Bitcoin cartel?
- Keep pushing SV2 & Datum
- Plebs running their own nodes

2026-07-22 19:40:32 CEST

Would you take a vaccine if you knew the virus could still infect you through another route?

2026-07-21 11:01:27 CEST

https://blossom.primal.net/ef1e337c4b1e8e40a94cc8c669f2f17d5efce53f62d96b5efa1e9378ec06bb97.png

2026-07-19 11:12:45 CEST

I appreciate smart people, pro and against 110.
CJChris, MrHodl, Wicked, Luke, Mechanic, Portland are some of those.
Many parasites I disrespect: Livera, Back, Tone, and Samsung (the omega dude).
The former do know stuff; the latter just look for quick bucks. Scammers.

2026-07-18 20:05:20 CEST

- reply

> So Bitcoin without corporate adoption reached $65k in 2021.
Bitcoin with ETFs, Treasuries, Saylor, Andy Back, Bailey in 2026 reached $64k in 2026.
100%

2026-07-18 20:04:30 CEST

Not your keys, not your coins.
Few.

2026-07-18 11:35:57 CEST

https://blossom.primal.net/befa7da2b8664c168c9e09b404689b4402c59fe6b6732a62d481199728c5bec7.png
Real corporate BTC adoption: accept it for goods, hold it, maybe allocate profits to it.
Saylor runs a ponzi (STRC) and you don't even self custody his coins.

2026-07-16 15:53:09 CEST

- reply

Here it is 😉
Let me start off by saying I’m not pro-BIP110, and I’m not anti-BIP110. If it actually succeeds as something that gains true consensus within the network and ends up being enforced by a majority of the network… cool. If so, then we’ll go with it because the network has spoken and accepted it, and all nodes, including non-BIP110 nodes, will be pulled along for the ride.
Unfortunately for proponents of the proposal, that simply isn’t currently the case by any measurable metric, nor does it appear to have a trajectory suggesting that will change, either.
There’s been a lot of misleading information about this whole thing, especially in the context of mining. Few quick key bullet points to briefly counter some hyperbole from proponents:
BIP110 is NOT inevitable. It CAN fail.
BIP110 can and will cause a chain split/fork in a minority hashrate situation.
BIP110 is NOT without risk to miners choosing to adopt it.
Miners not supporting BIP110 are not suddenly mining “invalid” blocks just because a proposal that isn’t yet adopted simply exists.
You’re not a bad person or evil simply because you don’t like or support BIP110.
(The fact that I feel the need to point out that last part is actually kind of sad…)
I was going to write a long post to help keep miners informed about things they need to remain aware of as this all plays out… before realizing I already did so months ago as a document I authored that I had hoped could be put out as a miner education piece at OCEAN. Sadly, it never got published. So I went ahead and updated it, and well, here it is:
https://docs.google.com/document/d/14DfMSVYBHTHIOmW32JTOR6BAP7AITbinvrhl8rJuvvc/edit?usp=sharing
Again, keep in mind this was written months ago, intended to be as agnostic as possible in an effort to make it acceptable as a corporate post. That effort failed, so I'm posting it as a personal document today instead.
As a miner making important decisions about your operations, you need to be aware of all of this without the sugarcoating and frankly outright misleading information coming from some of the BIP110 proponents. You must be vigilant, and decide what’s right for you. While there is certainly some misleading information from the opposition as well, nothing I’ve seen is nearly as egregious as the extremely premature claims of victory and accompanying hyperbole pushed by the BIP110 side.
Summarizing my doc a bit, my personal suggestion to miners is this:
Signal if you support BIP110
Do not signal if you don’t support BIP110 or don’t care
Either way, monitor the network on/around/before block 961632.
If you continue to see non-signaling blocks from major pools you can be reasonably certain they’re not going to suddenly decide later to throw away millions of dollars worth of revenue to backtrack and signal for BIP110.
If they do by some chance start to signal for BIP110, you should monitor that and consider switching as required to stay on the heaviest chain.
Key point being that realistically, only one side can win. It’s either BIP110 succeeds and miners not on the BIP110 side fail, or BIP110 fails and miners on the non-BIP110 side succeed.
Moving on, let’s dive into some small fraction of my rationale.
🟠QUICK FACT: Between 7 and 15% of Bitcoin Nodes are signaling support for BIP110.
Depending on which centralized crawler you look at… no way to know for sure. My personal private crawler puts this number much lower, but that’s a discussion for another day. Suffice it to say, I think it’s logical and correct to say that even 15% is not a majority.
“But Jason! UASF got Segwit activated with fewer nodes!”
Yep, because many miners, merchants, users, etc all actually wanted Segwit. There was tremendous economic and community weight behind it. Without rehashing that whole thing (plenty of resources on the topic from before BIP110 that are worth a read), suffice it to say that BIP110 and Segwit activations are not quite comparable, as many have already pointed out. Segwit, for example, went into its UASF territory with around 1/3rd of the network hashrate already signaling support. With that kind of backing, the UASF to help push the MASF over the tipping point made a lot of sense.
It doesn't make sense here for BIP110.
🟠QUICK FACT: 0.6% of blocks over the past 60 days have signaled support for BIP110.
Pretty stark contrast to even Segwit’s low baseline support. Yes, I know it's increased slightly in the past couple of weeks, but no new entrants. Just more clearly rented hashrate from one of the same small proponants.
Something to keep in mind is that mining BIP110 signaling blocks via DATUM on OCEAN carries virtually no risk to the miner up until the fork point at block 961632. The cost is negligible, as you're effectively guaranteed to recoup rental costs, etc.
It's awesome that the ability to do so exists, and I wouldn't have it any other way... but just something to keep in mind when weighing signaling from such blocks in the grand scheme of things from a risk/reward/money-on-the-table perspective.
“But Jason! Miners have no incentive to signal until the last minute!”
I also see no evidence to suggest that this could be the case. Subjectively, I disagree with the premise, as it’s not in a mining pool’s best interest to destabilize the network in such a way. Part of the reason for early signaling and lock-in periods is to help coordinate upgrades in a smooth fashion. Waiting until the last minute negates that benefit entirely. I see no compelling rationale or upside to doing so.
Continuing on this, as part of my personal node monitoring setup, I specifically monitor nodes known to belong to various entities, such as other mining pools, exchanges, large lightning nodes, merchants, etc. A supermajority of which are monitored with explicit permission and confirmation/coordination.
🟠QUICK FACT: All major mining pools I monitor are currently running some variant of Bitcoin Core v30 or v31 (except OCEAN).
Expanding on that, most have updated their nodes since the proliferation of BIP110’s release, even since the release of Knots 29.3. Additionally, it is known that many mining pools run modified versions of their node software to facilitate various requirements of their specific infrastructure. Such changes would need to be ported to a BIP110 compatible client, tested, evaluated, and deployed ahead of time. I currently see no evidence that this is the case currently.
As far as I can tell, the pools are aware but ignoring.
“But Jason! Miners don’t determine consensus! Nodes do! Otherwise they’ll just cancel halvings!”
This is one of the funniest and most ridiculous arguments I’ve heard from the pro-BIP110 crowd. Comparing a consensus change that can be unilaterally enforced upon the network by miners and accepted by 100% of existing nodes (a soft fork), with a hard fork which no existing node will accept… is disingenuous at best.
Tightening rules (like BIP110): Soft fork, can be enforced by miners if they choose to do so. Loosening rules (like canceling a halving): Hard fork, can not be enforced by miners without effectively 100% buy-in from the entire network……. Which isn’t likely to happen.
Comparing the two is, bluntly, just stupid.
“But Jason! If you don’t upgrade to the latest consensus rules, you’re insecure! You’ll lose funds! You’ll mine invalid blocks! You’ll [insert additional hyperbole here]!”
This would be true of a consensus change that has, well, consensus. While BIP110 has made a valiant effort to gain that consensus, it has yet to have any measurable majority at what is now arguably the 11th hour. Not in nodes, not in hashrate, not in the social layers (consensus.health has a cool visual there where you'll find me in the middle).
If somehow BIP110 gains 51%+ of the network hashrate on/before block 961632… then, alright. It’s enforced, since as a soft fork a majority of miners can unilaterally enforce it in the absence of a fully adopted URSF (effectively a misnomer, as this would kind of be a hard fork).
“But Jason! It can’t gain consensus by already having consensus! You have to give it a chance!”
Firstly… no I don’t, even though I have. Second, it’s a rushed proposal that never had the time to even try and gain real consensus. It’s been 7 months since the release of the first BIP110 client. There’s ~3 weeks to go before “mandatory” signaling starts as of now (less by the time you read this). 90% of the time available has passed with no change in overall sentiment from any relevant players. If it hasn’t gained sufficient adoption in the past 7 months, it’s not likely to do so in the next 3 weeks.
"But Jason! CSAM! CSAM! Pedophiles! CSAM!"
I'll be the first to say, even I personally overstated the risk here early on when Core proposed its OP_RETURN change. I personally expected something particularly egregious to hit the chain almost immediately, and to the best of my knowledge that's not yet happened. Could it still happen? Yeah, I suppose.
But considering from a technical perspective, byte-for-byte the same contiguous arbitrary data can provably end up stored in the current chain or the BIP-110 chain without much issue... this particular argument for BIP-110 falls pretty flat to me at this point.
Do I want CSAM in the chain? Of course not. Am I a pedophile if I don't support BIP110? Also not.
...
I could continue to go on and on and on, but I'll stop here. I've wasted enough time on this. I'm sure I've done plenty to annoy both sides of the BIP110 debate at this point, as I don't adopt either stance. I'm sure I'll catch flack from all angles simply for daring to speak my mind on it.
Overall, I mostly think it was silly to approach addressing a real problem (the OP_RETURN default change in Bitcoin Core) with the maximum anti-spam manifesto based soft fork proposal... which provably cannot stop spam, arbitrary data, etc. 🤦‍♂️ (Yes, I know, proponents will claim it's not about spam... and will also make semantic arguments that it does stop data as well... neither of which appears to be correct.)
I'll close with the concession that I could be wrong. I'm not Nostradamus, and I can't accurately predict the outcome with 100% certainty. I can only go by what the data tells me, and so I give BIP110's success less than a 5% chance of actually succeeding... and I consider that generous.
You can take my opinions on this however you wish, but I highly recommend you don't discount the actual data points, remain vigilant, and do what's best for you and your mining revenue. Don't be gaslit by either side of the debate, and make your own decisions.
Here's a link to the same document linked above for ease of access: https://docs.google.com/document/d/14DfMSVYBHTHIOmW32JTOR6BAP7AITbinvrhl8rJuvvc/edit?usp=sharing

2026-07-16 15:48:03 CEST

- reply

https://x.com/wk057/status/2077444826232955365

2026-07-16 15:28:33 CEST

- reply

Jason published an article on Twitter.
TLDR (with Claude):
TLDR: Jason (the author) is neutral on BIP-110 but wants miners to have accurate info before deciding. Key points:
BIP-110 is not inevitable and could fail — it currently has weak support: only ~7-15% of nodes signal for it, and just ~0.6% of blocks over the last 60 days have signaled support.
This is much weaker than Segwit's UASF had (which started with ~1/3 of hashrate already on board), so comparisons to Segwit's activation don't hold up.
Nearly all major mining pools he monitors are still running non-BIP110 clients (Core v30/v31), with no sign they're preparing to switch.
He pushes back on common pro-BIP110 talking points: that miners have "no incentive to signal early," that opposing it is like trying to cancel a halving (soft fork vs. hard fork — not comparable), that not upgrading makes you "insecure," and that CSAM concerns are a decisive argument (he says arbitrary data can end up on either chain regardless).
His advice: signal only if you genuinely support it, don't signal if you don't/don't care, and closely monitor major pools' behavior around block 961632 to see which chain has the real hashrate — then follow the heaviest chain.
His personal estimate: less than 5% chance BIP-110 succeeds, and he calls that generous.
Bottom line message: don't get pressured by hype from either side — look at the actual data and decide what's best for your own mining operation.
Because of this Mechanic got pissed, and he was removed.

2026-07-16 15:21:22 CEST

Crazy times we live in. By the way, Jason is very much smart and skilled.
People have lost the plot.
https://blossom.primal.net/ed3d3d33896c5f134f543c1bf730a3e41dd8dcfd00069f1518d423bde20ca187.png

2026-07-16 11:59:08 CEST

#Italy: A 72 year old jeweller, after being robbed 6 times, including an incident where a gun was pointed at his daughter, killed two out of 3 burglars. He received a 15 year prison sentence and was ordered to pay €760,000 in compensation to the burglars' families.

2026-07-14 23:14:22 CEST

- reply

You can run the custom client on your machine with the command below.
Open Docker then:
curl -fsSLO https://raw.githubusercontent.com/dani69654/hchat/main/docker-compose.yml
docker compose --profile tor up
#nevent1q…s67j

2026-07-14 23:13:35 CEST

- reply

You can run the custom client on your machine (under tor) with this command.
Open Docker then:
```
curl -fsSLO https://raw.githubusercontent.com/dani69654/hchat/main/docker-compose.yml
docker compose --profile tor up
```

2026-07-14 15:00:16 CEST

Bitcoin is a peer to peer electronic cash system.
Its best use case has been buying drugs online.
Bitcoin is not "digital capital" whatever that means, in Italy we call that a "supercazzola" (a string of fancy words meant to sound smart while saying nothing)
https://blossom.primal.net/9ce0053cb772d6e3450b56fdc6a82cdec1f5973e8673a193003bffb795f91be7.png

2026-07-14 14:16:04 CEST

Saylor does master the "buy high, sell low" strategy. I thought that was just a meme.

2026-07-11 18:29:58 CEST

- reply

Disagree. bitcoiners and infightings are what keeps Bitcoin alive

2026-07-10 21:56:25 CEST

- reply

No, it's completely different.
1. It proves when the block was created.
2. It proves the block wasn't precomputed.
3. It's a "coinbase message", which Bitcoin explicitly allows.
The third point is the key. We still use coinbase messages today. They're a protocol feature, not a hack.
Satoshi used the coinbase field for its intended purpose. Inscriptions, by contrast, store arbitrary data using a different mechanism that was never designed as a general message field.

2026-07-10 14:26:21 CEST

- reply

Bitcoin spam is any data embedded in a transaction that isn't required for the locking/unlocking scripts to execute. By that definition, embedding multimedia files in Bitcoin transactions is spam.

2026-07-10 11:42:45 CEST

A #Bitaxe Gamma mined a block 6h ago <3 congratz you lucky bastard!
https://
web.public-pool.io/#/app/bc1q0pp7
4ghs25vpn2ah6auz4vkehvzy8z8ddyzts7
…

2026-07-10 11:06:38 CEST

Immigration can't be stopped, but it can be mitigated.
Pollution can't be stopped, but it can be mitigated.
Spam on Bitcoin can't be stopped, but it can be mitigated.

2026-07-10 00:43:39 CEST

- reply

Fair criticism, v1 was RSA-2048-OAEP directly on the plaintext, no hybrid. I've just replaced hchat's weak RSA encryption with X25519/Ed25519 + AES-256-GCM

2026-07-10 00:20:18 CEST

- reply

would u help share?
any help is welcome, many devs follow u :)
https://primal.net/e/nevent1qqsy66v8rqg7mjk5kqg6nzvqvp3q9m8jfeq34fc44qvednsezcp89zq4ewp9s

2026-07-10 00:18:50 CEST

- reply

Unfortunately it's impossible to hide that user A is talking to user B, because the convos inevitably go through WA servers. What we can do is to encrypt client side, so that whatsapp does not see the content of the msgs

2026-07-09 22:29:17 CEST

- reply

That’s correct

2026-07-09 20:49:18 CEST

- reply

Right, it's not a custom app talking to their servers.
It piggybacks on the official WhatsApp Web client whatsapp-web.js runs web.whatsapp.com in headless Chromium and automates it, linked as a companion device via the standard QR flow.
WA Web has no device attestation so as far as Meta sees it's a normal linked-device session. hchat just RSA-encrypts the plaintext before it enters that session, so WhatsApp only ever carries ciphertext.

2026-07-09 20:34:10 CEST

- reply

No.
Apps such as WhatsApp are going to implement backdoors that can be used by the police to decrypt your messages.
By using this custom WhatsApp client, you will encrypt your messages locally in your browser, which means that whatsapp will only see your messages encrypted, and won't be able to decode them since the private keys is stored in your browser only

2026-07-09 20:24:40 CEST

Binance CEO Richard Teng says 70% of EU user withdrawals went to self-hosted wallets instead of MiCA-regulated platforms. 🫡

2026-07-09 20:11:36 CEST

- reply

Doing gym without stressing out too much is good so that you can live longer and spent time with your loved ones.

2026-07-09 19:54:20 CEST

- reply

E' una web app, quindi funziona con Android e iOS.
Potrei fare un'app nativa per mobile ma non credo che Apple Store o Google play l'approverebbero.

2026-07-09 19:38:23 CEST

- reply

#asknostr
#nevent1q…s67j

2026-07-09 19:30:04 CEST

Built a WhatsApp client that fucks #ChatControl.
It layers RSA E2E encryption on top of WhatsApp itself your messages are encrypted before they ever hit the wire.
In few days will share a url, for now you can run it locally.
Supports Tor as well.
https://github.com/dani69654/hchat
https://blossom.primal.net/4fc65fe70379614682b47c08e5447abebc5373f3c333dc21748a8b5933e9cdf8.png

2026-07-05 22:54:25 CEST

Building #neo: https://github.com/dani69654/neo
A tiny AI that anyone can run locally.
The fun part? It learns new skills.
Want to contribute? Open a PR and add one 🫡
#asknostr #code #ai

2026-06-25 15:52:05 CEST

https://blossom.primal.net/6f9c66339aea7019a43c72f69957c9c1e2d545870b9183aaa51a37ccae2124d4.mp4
🫡

2026-06-19 12:14:53 CEST

Shit hits the fan when the bitty is trying to hang tight above the 200MA.
I have no clue that it's going to happen but if we resist this period and somehow we recover we go to 500k

2026-06-17 08:30:04 CEST

Receipts
https://blossom.primal.net/c57e9951e88bed387e372a06df7ac898d22f507c8ee133ec071b1a235bd30615.png

2026-06-12 15:52:47 CEST

- reply

non si capisce che roba e', manda le repo

2026-06-11 10:51:33 CEST

They panic when I say "sell a little coin just to prove the whole market doesn't break or get destroyed"
https://blossom.primal.net/b05cb1e88e853c96e671fbf6aee002a708c6bc3ceea59f491a6c1cc82f88c336.png

2026-06-10 18:09:36 CEST

Long term holders are at an all-time high
https://blossom.primal.net/519ce4e1e6dc6329cd89d894f27f5efe8ccf8b6127df39d3e190d74d01ac3b00.png

2026-06-06 19:11:21 CEST

- reply

Cool but what's the use case?

2026-06-06 17:09:58 CEST

- reply

Faggot

2026-06-06 14:56:11 CEST

- reply

He is right.
The worst ones are those commenting, "leftists blah blah blah," because they still don't get that this isn't about left vs. right. It's not a football match.
We were supposed to carry out a peaceful revolution through Bitcoin. This is the endgame: a quiet exit from a wicked system.
#nevent1q…m0r5

2026-06-06 14:53:12 CEST

- reply

The worse ones are those commenting "leftists bla bla bla" as they still don't get it's not left vs right, it's not a footaball game.

2026-06-06 14:40:06 CEST

- reply

Leech

2026-06-06 11:45:41 CEST

- reply

Welcome to whatever EU country you are in right now, fellow Canadian friend 😄

2026-06-06 11:44:48 CEST

- reply

Given how many exploits Floppy keeps finding in your software, maybe running your own isn't such a great idea.

2026-06-05 23:55:11 CEST

Goodnight lads. Enjoy the weekend, spend your time doing things you love, far away from the computer

2026-06-05 21:26:27 CEST

The flippening
https://blossom.primal.net/e2a43682a2c38ce95bcdc20ae1ac7fb69497bf4cac0e927ce66df430c4b7d33b.png

2026-06-05 16:28:01 CEST

- reply

I don't think you can name 10 people that use miniscript for real purposes.

2026-06-05 15:49:12 CEST

- reply

I believe you can write this script using 2 leafs thus avoding the need for OP_IF. I could be wrong I am not a script wizard but something similar to the below one should work.
After all, multiple script paths are one of the biggest taproot selling point.
Leaf A
<pubkey1_A> OP_CHECKSIG
<pubkey2_A> OP_CHECKSIGADD
<pubkey3_A> OP_CHECKSIGADD
OP_PUSHNUM_2
OP_NUMEQUAL
Leaf B
OP_PUSHBYTES_2 6432
OP_CSV
OP_DROP
<pubkey1_B> OP_CHECKSIG
<pubkey2_B> OP_CHECKSIGADD
<pubkey3_B> OP_CHECKSIGADD
OP_PUSHNUM_2
OP_NUMEQUAL

2026-06-05 14:15:49 CEST

Real Bitcoiners care about node decentralization, self custody, and merchant adoption.
Not some billionaire scamming retail investors to accumulate more fiat and stack paper bitcoins on a centralized exchange.

2026-06-05 10:58:53 CEST

Community is healing, memes are back
https://blossom.primal.net/18c232880a9615d5e45bae3fac1e4507c3a98a59589d00319e0f4914f945f4e9.png

2026-06-05 10:02:54 CEST

🤣 🤣 🤣 https://blossom.primal.net/eb5b6d64a78de1f00e0efb0d1c657255af7b31668282d6f315c49776ebf8f351.mp4

2026-06-04 15:42:05 CEST

Citrea shitcoin is live, the post got 50 likes and 30 comments, 27 of which are insults 😂
Cirea had to buy comments to cover up how nullish they are.
https://blossom.primal.net/713a5b528c2754b699cec100ec4c038efbe23fd27b0ce01a61ce913fb20595ac.png

2026-06-04 15:26:27 CEST

- reply

follow me or u'r missing out

2026-06-04 14:47:29 CEST

- reply

Share the repo 🫡

2026-06-04 13:52:37 CEST

When Saylor started buying paper coins, the focus shifted to hoping that Wall Street and the government would start doing things for us.
How fun is that?
Of course, everything started to break. If we're going to survive, we need to rebuild, starting with our mentality.
Wall Street will never do anything for us. They're our enemies, for fuck's sake.

2026-06-04 07:07:19 CEST

Saylor accumulated lots of bitcoins just by selling MSTR shares years ago.
He got in trouble for saying "If you push me too far, I lost it, it’s gone, sorry. Tax that!!"
Then decided to play greedy shitcoin games with a strategy suggested by ChatGPT.
Stay humble people, stack sats. https://blossom.primal.net/88f662d24f179e06689dadc26bb6a4ba0dea9ae990f1cda0a1caf2489f1c2e92.mp4