<unnamed>

Public Key

npub100mahqlhxg50thmt5dyynu40nl25hat9kkkknzk8pqjfkvgq0xsqtdfyy5

Profile Code

nprofile1qqs8ha7ms0mny284ma46xjzf72hel42t74jmtttf3trssfymxyq8ngqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds9qx7d6

Publishing to

relay.damus.io

nos.lol

Last Notes

2026-02-12 01:21:11 CET

- reply

In general I don't believe idiots and scammers need any special help getting relieved of their coins sooner or later.

2026-02-12 00:41:59 CET

- reply

I have better uses for my sats than engaging with friendly bets with scammy shitcoiner VCs. For instance renting hashrate for my DATUM gateway.

2026-02-09 02:28:07 CET

- reply

Off the top of my head: LukeDashjr, Jason Hughes, Chris Guida, SuperTestnet, Hunter Beast. Probably missing a handful.
Wanker.

2026-02-09 00:58:21 CET

- reply

As I said on X, BIP-110 is as much a signal that Bitcoin is money as a slap in the face of the careless developer class.
Of course they're gathered 'round and decided that bitcoiners slapping them in the face is retarded.

2026-02-08 11:51:24 CET

- reply

BIP-110 spec: https://github.com/bitcoin/bips/blob/master/bip-0110.mediawiki
Informational site: https://bip110.org/

2026-01-28 18:14:34 CET

- reply

So what if I do that, too.

2026-01-28 17:52:02 CET

- reply

It's not a question, it's an errand 😂
But he won't respond. He blocked me after I told him this.

2026-01-18 23:59:34 CET

- reply

I see. A fellow man of culture. https://blossom.primal.net/4cb86bc40466594f58846b033d9c7fc51b653d58cac63a6a8789ae65b3cfc005.jpg

2026-01-16 22:52:43 CET

- reply

Congrats!

2026-01-16 22:49:54 CET

- reply

I've been daily driving either XUbuntu (Ubuntu with XFCE) or Debian (with XFCE) for the last decade without any memorable "peak Linux" issues coming to mind.

2026-01-16 01:17:06 CET

- reply

Hope so, my police record was pathetic. I was pretty underwhelmed, tbh.
https://blossom.primal.net/5e27c7bedd3871a4597365218449b47fc784ee79b793cc2c96c31bb4e73928e0.png

2026-01-16 01:11:12 CET

Nostr, give me my Semantic_Contextual_Scoring_OHI_V3 field.
https://blossom.primal.net/92efdd963d3ee62c8c72e873a8e4f27a43f0f890749b4739afb549334a1e92dd.gif

2026-01-10 00:41:58 CET

- reply

Right, I had NWC set up but I didn't have an LN address on my profile. This should do it I think!

2026-01-10 00:39:14 CET

- reply

Really? I can zap, though 🤔

2026-01-10 00:33:59 CET

- reply

Hey! Caught you red handed!

2025-11-11 01:21:24 CET

Apparently there's no way for me to see these messages. Pretty ghey for a censorship resistant protocol, if you ask me.
https://blossom.primal.net/9c372c96779bfd05e91300acdc209df5df5e90b76aa888ca8430cca002618abb.png

2025-11-11 01:16:59 CET

- reply

No. Orange-washed commies can GFT ✌️

2025-11-11 00:33:51 CET

- reply

I verified both the X thread and the linked issue from the Bitcoin repository, and he didn't dox himself in 2023.
He was actually complaining about Marco Falke doxing him in a comment of said issue. A comment that since then has been scrubbed from GitHub (his link is now partially broken).
Verdict: 🤡 🤡 🤡 🤡 🤡

2025-11-07 20:25:55 CET

- reply

I don't work for you. And apparently Mechanic saw fit to give you a second chance so it's also an irrelevant request now.
If it was up to me you'd still be banned, that's all anyone needs to know.

2025-11-06 23:59:15 CET

- reply

BTW I'm an admin in the Knots and Fork Talk group now.
Learn to behave like a normal person or I'll kick you out of Fork Talk, too.

2025-11-06 23:52:05 CET

- reply

Lol. Kindly get fucked.

2025-11-05 19:13:11 CET

- reply

A normal soft fork is designed to wipe out the old chain. It can start as a chainsplit if it's contentious (.e.g a UASF situation), but it will heal the split on activation.

2025-10-27 23:31:44 CET

- reply

No lies detected.

2025-10-17 00:10:32 CEST

- reply

There we go.
7 signers (so far) for Knots v29.2.knots20251010.
https://github.com/bitcoinknots/guix.sigs/tree/knots/29.2.knots20251010

2025-10-13 20:08:03 CEST

- reply

Good times.

2025-10-13 19:48:54 CEST

- reply

I attested all Knots releases since v25.1. knots20231115.
Haven't attested v29.2.knots20251010 yet because it just came out. Thanks for the reminder.

2025-10-06 23:50:37 CEST

- reply

This is business as usual. https://blossom.primal.net/77a30fff244c87ffc5d77b3453ba51a2402edd3772b17cbcd00a225a7b103337.mp4

2025-10-05 23:25:45 CEST

@nprofile…wqxt de vez en cuanto firmo eventos de Nostr con mi clave privada y los retransmito, luego existo.

2025-09-17 20:23:28 CEST

- reply

Thanks!
My only interest in FPPS is that it seemed easier to implement than PPLNS and especially TIDES, with its payouts to miners directly from the coinbase tx.
But now I've realized you could send all the rewards from the coinbase tx to a pool operator's address and still implement PPLNS payouts.

2025-09-17 00:00:46 CEST

- reply

What kind of database do you think would appropriate to store and efficiently access this kind of information?
Also do you think it would be too difficult to evolve this PoC into a realistic FPPS DATUM pool?

2025-09-09 00:39:22 CEST

- reply

fukin' based

2025-08-28 20:22:29 CEST

- reply

But the scammers are there :')

2025-07-29 12:40:59 CEST

- reply

Yes: https://ocean.xyz/dashboard

2025-07-29 12:32:03 CEST

- reply

Reminder: banning VPNs amounts to banning the Linux kernel in the UK, as it contains the source code of Wireguard and its full functionality.
For those who don't know Wireguard, it is arguably the best VPN software written to date.
#nevent1q…wkrp

2025-06-15 00:49:29 CEST

- reply

Holy fuck!

2025-06-14 23:59:59 CEST

- reply

They're even crypto haters in the broad sense (who can really blame them?): https://forums.eveonline.com/t/isk-for-bitcoin/481662
Primed to be disrupted.

2025-06-14 23:58:35 CEST

- reply

https://media.tenor.com/BLZmDf-dyK8AAAAM/exactly-meme.gif

2025-06-14 23:50:00 CEST

Today a friend showed me the EVE Online rabbit hole and I can't believe no one is working on a Bitcoin version of this game (at least that I know?). To sum up the idea:
An MMORPG with Nostr-based accounts and Lightning Network integration to make sats the base currency of the game. And make it realistic enough so that an anarchic in-game economy can flourish.
https://www.youtube.com/watch?v=CrH6jyZ5j7g

2025-06-10 22:42:55 CEST

- reply

Fug, how do I get back into the cryogenic time capsule? https://blossom.primal.net/2728ff5c6c4bb805fddb641e9aa7fb4918e2272420dafb5fa27d16c7b4e73bb2.gif

2025-06-10 21:00:10 CEST

- reply

Don't y'all go praising me behind my back 😠

2025-06-10 20:58:31 CEST

- reply

https://blossom.primal.net/39c770216bc92c956bf8d790c7054ccc531ad0989b6f043724116b410ddb03ab.jpg

2024-07-22 08:49:47 CEST

- reply

Make your own signet. I've got you covered:
https://github.com/BcnBitcoinOnly/signet-playground

2024-07-18 20:18:42 CEST

- reply

Mandatory xkcd strip. https://image.nostr.build/c7ec200f7ff6f556991cb85714a226863bb5a91f9f5c83554eb3aa5857312644.jpg

2024-07-14 00:26:28 CEST

- reply

That doesn't really sound like a zap anymore.
I don't think I'd interact with any mint to retrieve any tiny IOUs that random people give me. But LN sats I'd still take.

2024-04-24 23:45:00 CEST

Privacy is not a crime, and neither is writing code.
Free Samourai.

2024-04-03 21:39:35 CEST

Dockerized Custom Signet network
https://github.com/BcnBitcoinOnly/signet-playground

2024-03-21 20:58:07 CET

- reply

Dioooos que guapo!
Tienes LNURL? Quiero enviarte unos sats pero por ahora no puedo zapear en Nostr.

2024-01-27 17:22:39 CET

- reply

Back in 2017 a few of the spam filters from Core that apply to legacy TXs were not adapted for SegWit.
Fixing this inconsistency in Core would go a long way in mitigating the problem, but the current maintainers don't seem willing to make this fix (they recently closed a Pull Request that did just that).
Running Bitcoin Core with the ordisrespector filter, running Bitcoin Knots (@lukedashjr's version of Core with extra features and adequate filters), or pointing your hashrate to Ocean if you are a miner are the things that are in the hands of individual Bitcoiners.

2024-01-27 16:09:17 CET

GM ☕
2017 vs 2024.
You either die a hero or live long enough to become a clown, or something along those lines.
https://m.primal.net/HZVj.png
https://m.primal.net/HZVk.jpg

2024-01-13 11:01:42 CET

- reply

1maa/bitcoin:v25.1.knots20231115
https://github.com/BcnBitcoinOnly/docker-knots/tree/master

2023-08-20 23:58:19 CEST

- reply

Bliss. Unfortunately Bitcoin itself ain't that popular.
https://bitnodes.io/

2023-08-20 23:34:05 CEST

- reply

Few.
https://media.tenor.com/FBHnbOSeimwAAAAM/patapon-pon.gif

2023-03-21 17:44:25 CET

- reply

I didn't expect to get schooled today. Thanks for these insights.

2023-03-21 17:32:21 CET

- reply

Do you happen to know if LND, Core Lightning and Eclair's onchain wallets support RBF?

2023-03-21 14:59:55 CET

- reply

(I meant on Raspiblitz, obviously)

2023-03-21 14:52:32 CET

- reply

Fair point. I didn't thought about that and it's the first time someone brings it up to me.
I concede that an operator of a LN node backed by an Ordisrespector Bitcoin Core has to pay extra attention to both mempools if he wants to close a channel (for now).

2023-03-21 14:15:49 CET

- reply

run a (spammy) node if you want that shit, lol

2023-03-21 14:13:38 CET

- reply

I built the #[11] precisely for that. Though it sources the data from the mempool.space websocket API, not estimatesmartfee.

2023-03-21 14:07:29 CET

- reply

Fair enough. I'll see if I can do that PR myself.

2023-03-21 13:35:04 CET

- reply

The thing is I believe we're in a catch-22 situation where an actual supermajority of node runners want to filter inscriptions from their mempools but they don't know how to do it (because BC devs and most node distros aren't making it easy), or they don't even realize they can do it. If I'm right and the situation ends resolving this way the patch will be no more and no less effective than minrelaytxfee. There are 0-fee txs from time to time but they aren't half of the mempool space.
Regarding other Bitcoin Script opcode sequences to embed arbitrary bytes in tx: I don't think they even need to be patched. If the network coordinates to reject this first kind of txs it should discourage spammers from trying much further. Detecting these patterns and patching them out is orders of magnitude easier than finding them, then it's just a matter of how fast most nodes patch them out.
I won't tell you what to do with Raspiblitz. But your users are sovereign to filter inscriptions, and some of them want to do it. They placed their trust in you, and you can either respect that sovereignty or you can try to get in the way of it. That's just the way it is.

2023-03-21 12:06:41 CET

- reply

And I'm not criticising it, my node also does that. What I'm doing is pointing out the contradiction of calling inscription filtering "censorship", but not 0-fee tx filtering. Both are done in exactly the same way, and neither are an act of censorship.
Both inscribers and 0-fee transactors can tweak their node configs and mine themselves, or strike their deals with miners. An Ordisrespector node doesn't get in the way of any of that.

2023-03-21 11:51:09 CET

- reply

Calling that censorship is disingenuous and not constructive to debate. You also "censor" unless you've explicitly set minrelaytxfee=0, or you've never run with blocksonly=1.

2023-03-21 11:41:23 CET

- reply

There is no such thing as an "accurate fee estimation" as each node runner has full control over mempool policy, so each mempool can be different (and actually is in practice).
My incentive as a bitcoin user is to pay less fees when I transact, not more. And as a node runner my incentive is to prevent my node from relaying spam* so that the blockchain doesn't bloat, and operating the node doesn't become more expensive than necessary, leading to more pruned nodes and centralization.
*Each node runner decides what he considers spam, it follows from the fact that he controls mempool policy.

2023-03-21 11:34:03 CET

- reply

BTW, in a couple of days (tops) you'll be able to trigger the #[11] with a zap to get an instant comparison.

2023-03-21 11:32:10 CET

- reply

Node runners should not cater to miner incentives but their own ones. While the situation doesn't resolve, if I want another estimation I can get it with a few keystrokes.

2023-03-20 23:31:11 CET

- reply

I don't know. The only ones who have added that option to their UI (that I know of) are the folks at #[9]
https://twitter.com/mynodebtc/status/1636827688471019538

2023-03-16 13:31:02 CET

- reply

Tagging #[5], I forgot to search for your npub.

2023-03-16 13:22:52 CET

- reply

https://twitter.com/oomahq/status/1621899295342329856
https://twitter.com/oomahq/status/1625164770037927938

2023-03-16 13:21:55 CET

- reply

I do believe that, yes.

2023-03-16 13:20:33 CET

- reply

It's time.

2023-03-16 12:32:27 CET

#[0] seems more interested in catering to exploiters and malicious developers rather than providing the tools that solve the Inscriptions mess to their own user base of node runners. They are trying to keep them as hostages of @rodarmor
https://twitter.com/umbrel/status/1636068336101621760
Not that it matters one bit. If you're an #[0] node runner looking to prevent spam from entering your mempool @AntePurgatorio wrote an #ordisrespector patching guide for you.
https://github.com/printer-jam/umbrel-ordisrespector
If you're on the market for a new node software provider that respect your choices I can recommend @mynodebtc. They actually acknowledge and care about their user base sovereignty.
https://twitter.com/mynodebtc/status/1626242552776265730
And if you think you're ready to become a truly sovereign bitcoiner with full control over your own DIY node check out #[1] MiniBolt guide or #[2] tutorials on YouTube. Don't let them psyop you into nonaction.
https://www.youtube.com/watch?v=_Hrnls92TxQ
https://minibolt.info/guide/bonus/bitcoin/ordisrespector.html