fiatjaf

https://stuff.fiatjaf.com/

Public Key

npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

NIP-05 Address

Profile Code

nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdakszxthwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mgqz5704

Publishing to

Author Public Key

npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

Show more details

Last Notes

2026-08-07 19:24:55 CEST

- reply

This wasn't supposed to be published!
I was just testing the flow for #nevent1q…mxsd

2026-08-07 19:23:39 CEST

- reply

It's too cumbersome, why not use the CLI?

2026-08-07 19:22:53 CEST

- reply

The odds are low but we'll keep trying anyway.

2026-08-07 19:19:11 CEST

hello from the nostr army knife

2026-08-07 19:18:34 CEST

- reply

Someone used it, @npub10yn…495k, your efforts were not in vain!

2026-08-07 18:56:41 CEST

- reply

We also need people like you, so thank you.

2026-08-07 18:56:02 CEST

- reply

No, once it is running send the URL and I'll test it and recommend it to clients to put it in their list of default signers.

2026-08-07 18:52:26 CEST

- reply

The whole point is to get everybody into Nostr, not just some dozen abrasive guys.
For every boomer from Facebook that comes to Nostr the world is saved a little bit.

2026-08-07 18:49:36 CEST

- reply

This is the least shaky NIP-46 I ever used, if that counts for anything.

2026-08-07 14:46:26 CEST

- reply

It's optional.
What do you think is better:
- to have a Google login to Nostr that doesn't surrender your keys and allows you to exit later; or
- to have a Google login to X, Instagram and TikTok and be imprisioned there forever (or until they kick you out)?
Or is there no difference between these alternatives?

2026-08-07 14:43:31 CEST

- reply

Yes, please do it!
Plaza is looking good, by the way.
If you're going for the customizable client approach I think it would work better to have just one binary that supports multiple "modes", instead of the webapp approach that has all the variants deployed to multiple domains.
These modes could be instantiated from a URL, or an event, shared by some community leader, something like that.

2026-08-07 14:36:04 CEST

- reply

By the way, if you are security-minded you can also modify or rewrite the operator software to allow users to configure more fine-grained permissions for it, prompt the user with an SMS message, implement rate-limits, disable ECDH key sharing with the central server, allow or block certain types of users, implement an easy kill switch that users (or friends of users) can push to disable signing in case they lose their phone or access to their phone and their Google account and other stuff.
The central server does support some types of restrictions already, and could support more, but for some cases or some people people it might make sense to do these on a layer below, at the operator level.

2026-08-07 14:20:43 CEST

If anyone has some public reputation and likes to run servers and is planning on doing so for the long haul, please consider running a public Pomegranate operator, i.e. someone that holds pieces of people's secret keys and does some math in order to allow them to sign.
The software should be very lean to run and is available in the repository below. https://github.com/fiatjaf/pyramid relay also includes a Pomegranate operator module that you can turn on.
#nevent1q…rhn6

2026-08-07 00:42:38 CEST

- reply

What site your privacy doesn't allow? https://viewsource.win/, my humble hand-coded NIP-34 viewer? Why?

2026-08-07 00:39:57 CEST

- reply

It will be good to test the flow with a different coordinator (central) if we do the thing in which a user publishes an event with their address and pointing to what central server they're using, so they can login using their own even if an app defaults to one specific central server.
Are you also going to run a signer (operator), because it would be nice to have another one to rely on.

2026-08-07 00:37:02 CEST

- reply

Actually you do have to create the private key in your app if the user hasn't registered any yet.
I'll look into implementing a decentralized key generation algorithm into this.

2026-08-06 16:38:28 CEST

This is a good idea that you should show to your dumb friends who love AI and don't care about Bitcoin or Nostr: #nevent1q…39tl

2026-08-06 16:19:41 CEST

- reply

I could also say that other OAuth providers can be (or are) supported, or even pure email or SMS (although this is more annoying), but for now I think we should stick to Google for simplicity and compatibility.

2026-08-06 16:16:03 CEST

- reply

What do you mean?

2026-08-06 14:10:42 CEST

- reply

If you are curious, it works basically like #nevent1q…p7fz
But the architecture now is much simpler so it has less bugs and fails much less often. I've been using it for months now without any hiccups.
And now it has this external identity concept, which makes it possible for the user to not store their secret key (although they probably should) and recover it later by talking to the signers (operators), which was impossible before. It's also easier to ask the operators to forget about you and do all the things that require authenticating yourself.

2026-08-06 13:50:14 CEST

How to add Google login to your app without having private keys in your app or handing them to Google: https://viewsource.win/fiatjaf.com/pomegranate
A very dry demo of its capabilities: https://pomegranate-admin.netlify.app/
At its core it's a bunker powered by FROST threshold signatures. Supported now in https://nostrord.com/, https://jumble.social/ and https://hallway0.netlify.app, with others incoming.
If you already have NIP-46 bunker support this becomes very easy to implement, there is a step-by-step flow in the README there that even an LLM can follow.

2026-08-06 13:32:07 CEST

- reply

A idéia era não muito testar, mas ver se tinha mais alguém interessado na idéia e também contribuir com as listas de perfis que já vêm no cliente ou sugerir outras coisas.
Também seria bom se alguém rodasse algum relay aí só para brasileiros, ou brasileiros de um certo tipo. Vi que tem uns brasileiros rodando relays, tipo o @npub1nvc…3mrr, mas são cheios de spam do mundo todo, tinha que ter um relay mais restrito e exclusivo para brasileiros ou qualquer coisa assim.

2026-08-06 13:28:32 CEST

- reply

It's a show about nothing!

2026-08-05 16:27:51 CEST

Uma experiência: https://nostrbrasil.netlify.app/
Quem tiver idéias, sugestões e críticas, por favor se manifeste.
Baseado nisto aqui: #nevent1q…j8t7

2026-08-04 21:52:10 CEST

- reply

How do you scan?

2026-08-04 18:16:12 CEST

- reply

It should be the easiest thing in the world to self-host if you have a server, since it is just a static site (modify `src/universe.ts` with your defaults and run `npm run build`). There are probably dozens of templates out there of how to do it with Docker if you really want that, or you can ask an LLM from 3 years ago to do it for you and it will get it right. Netlify was just one of the ways to deploy I found that would work for people that don't want to manage servers.
Please let me know how it goes, even if you think it's trash. Either here or in the group.

2026-08-04 14:00:00 CEST

A list of features for this:
- No zaps or Bitcoin anywhere.
- A single “like” button with no millions of emoji options.
- Fast local store based on Rust-compiled-to-WebAssembly redb running on OPFS.
- Slow background syncing of profiles you follow for maximally reliable outboxing with that doesn’t get rate-limited.
- Feeds based on:
- people you follow,
- follow sets,
- relays,
- relay sets,
- feeds hardcoded by the Hallway instance that can mix any number of pubkeys and relays.
- Can display many different Nostr kinds, with a per-instance choice of which ones show up in feeds (kinds that are not selected are only shown when referenced directly).
- Kind 1111 comments, including the option to reply to kind 1 notes with that.
- Cheap YouTube embeds using just an image and title on feeds (optional Dearrow support for images and titles).
- imgproxy support with a custom protocol for authorizing only specific pubkeys (implemented in Pyramid).
- Support for a custom proxy for OpenGraph embeds (previews can be turned off; by default uses open Coracle or Jumble servers).
- Send events to specific relays (protected or not).
- Read events from a specific author from a specific set of relays.
- Read events from a specific relay from a specific set of authors.
- Modify, update, add, and remove entries on follow sets and relay sets.
- Support for NIP-43 relay membership and roles.
And the source code: #naddr1qv…lnlx
(This note is just a test of relay-managed scheduled posts.)
#nevent1q…j8t7

2026-08-03 23:00:00 CEST

- reply

The true form of an actually free market is likely to be immensely different from what we see in the current world's "capitalism".

2026-08-03 22:00:00 CEST

- reply

We really should stop using and recommending hardware wallets except in very niche use cases.
Easier multisig solutions are necessary.
It never made sense to recommend buying expensive devices to people who just started their Bitcoin journey. And then these devices are all fragile and malfunctioning anyway.

2026-08-03 21:00:00 CEST

Often people will give advice that tells you to follow existing marketing demand.
That sounds very wise and common sense, but often (specially for a thing like Nostr and Bitcoin) it's merely status quo bias turned into reasonably sounding words.
Bitcoin had zero demand when Satoshi created it.

2026-08-03 17:44:55 CEST

- reply

https://closedpyramid.netlify.app/ is a silly example of a client that tries to be super closed to single relay.
I just found out that it is buggily not blocking replies from external relays in random threads as it was configured to do. If it wasn't for that it would be fully insulated from the exterior, which can be a feature.
https://sparc-noasis.netlify.app/ is another example of a custom experience from @npub1cgc…2ndy that I don't fully understand but it's certainly more interesting.

2026-08-03 17:32:55 CEST

I've been working on a customizable client (mostly relay feeds, but a ton of other things and subtle details too). It's called Hallway for reasons I don't remember and it's a fork of Fevela which is a fork of Jumble, but very rewritten for speed and simplicity, and with some new features I haven't seen in any other clients, mostly around interacting with specific relays.
Don't try to use it immediately because it is very dry, but https://hallway-deployer.fiatjaf.com/ is a service that lets you setup the customization options through a form and the resulting static site is deployed to your Netlify account and lives there independently.
You can set up the client URL, name and logo, you can configure the strings to make it talk like a Croatian pirate, you can configure some of the colors, styling and so on, you can configure some of what shows up and what doesn't and the default relays and blossom servers used for new users, you can configure what kinds are downloaded in the background and displayed in feeds, but most of the configurations are around the relays:
- hardcoded relay-based feed sections,
- lists of relays where to publish things or read replies from,
- fallback relays,
- search relays for profiles or notes.
There are many goals to this:
- making a client that is good for onboarding a certain type of person,
- for creating a closed environment for a specific community,
- make it easier for people to use multiple clients at the same time, each with a specific purpose,
- others I forgot and yet to be discovered.
This is pretty much in experimentation and discovery phase and probably very buggy still, but if the concept interests you please join us at https://app.flotilla.social/spaces/basspistol.org/h1 or https://web.nostrord.com/#/g/basspistol.org/h1 or https://grimoire2.netlify.app/run?cmd=chat%20basspistol.org%27h1 and give feedback, suggestions, whatever. Thank you.

2026-08-03 16:20:15 CEST

- reply

May I ask what do you think about GreenAddress-style multisig solutions?
Or something like https://xcancel.com/PeterRizun/status/2084063800962253228?

2026-08-03 12:22:37 CEST

Mais uma conquista nacional: por meio do nosso herói NVK o Brasil conseguiu finalmente destruir o Bitcoin.

2026-08-02 22:14:44 CEST

- reply

I recommended it to a cousin of mine. I never really liked the idea of hardware wallets but was convinced it was an easier setup for most people.
Now I'm back to my previous position: #nevent1q…6wtz

2026-08-02 16:07:49 CEST

- reply

It's very likely to be ok since most Nostr clients run in environments that provide good RNG and are developed in languages that provide easy access to that, so the developer would have to be specially gifted and unlucky to get that wrong.

2026-08-02 14:09:06 CEST

I did an interview here if anyone is interested in learning about nothing: https://www.youtube.com/watch?v=7mWllE9AuKs

2026-08-02 01:14:51 CEST

- reply

I have these same memories. I also remember him going on a podcast to explain the thing maybe and talking a lot of things that didn't make much sense to me. At some point he made everybody agree that Bitcoin Core was the best software in the world before he could continue his explanation on why his CD-ROM scheme used Bitcoin Core necessarily.

2026-08-01 21:15:38 CEST

- reply

At first glance looks similar to what I wanted but when I try to create a policy all the options are useless for the type of thing a normal person would want.
They have an AI that builds "policies" for individuals, I said I wanted a policy to "only sign when I authorize with my Nostr account" and this was the reply I got: "I've created a rate-limiting policy as a starting point. What it does: Allows up to 5 transactions per 7-day rolling window".
Then if you try to build it all the conditions look uselessly taken straight from Bitcoin script, in which case I would rather just use Bitcoin script. Maybe I misunderstand the use case, but it doesn't help that the entire site is unreadable meaningless slop.

2026-08-01 17:33:15 CEST

I wish there was a service that allowed people to create multisig wallets (with the service holding one of the keys) that simulated OP_VAULT behavior (or better), but it would have to be cheap and easy for anyone to use from a mobile app, not a corporate offering for billionaires like some solutions that exist today.
I imagine this isn't an easy ask, but GreenAddress used to do something similar so it isn't impossible either.

2026-08-01 02:53:08 CEST

- reply

Do a multisig just in case. A 2of2 multisig with one of the keys on a normal phone or a desktop computer and the other on the hardware wallet. Make it a 3of3 if you're cool.

2026-08-01 01:09:55 CEST

- reply

What are the odds you give of anything like that being activated on Bitcoin in the next 5 years?

2026-07-31 20:09:31 CEST

Much like Nostr, NIP-29 is just signed notes on servers:
#nevent1q…6zsx

2026-07-31 20:06:00 CEST

- reply

Pretty good.

2026-07-31 13:29:19 CEST

- reply

If you don't look at the code and compile it yourself on a computer you built yourself from scratch and a pristine OS you can never be sure, but my understanding is that doing these things on a ColdCard-style device is much harder than doing them on a normal computer of phone, so it is easier to make a mistake.
On a normal computer doing secure RNG is easy, so it's much less likely that the programmers will get confused and end up doing things wrong.

2026-07-31 13:02:48 CEST

Cool thing:
#nevent1q…hcyw
#nevent1q…z42q

2026-07-31 12:57:26 CEST

- reply

Irrelevant. Probably 100% of Nostr apps generate keys using good random numbers from a full blown OS.

2026-07-31 06:23:08 CEST

- reply

I recommend looking at FROST and server-side multisig bunkers as a bridge between the two worlds out of an abundance of caution.

2026-07-31 06:15:37 CEST

- reply

I recommend migrating to Rust out of an abundance of caution.

2026-07-31 06:04:59 CEST

- reply

Seems to be this, taken from links from the article above:
https://nostr.media/c0260f242e1de4d408ec0b33b36934616b71dccf3cee59fefcdae4a1bc0f893c.png
https://nostr.media/39040e12417b3ce70bb4c0eae0e8c3720930d819cb5dffb7bf05c363e5fc2c6b.png
https://nostr.media/edc8237df402f529e7d234b78b27356ecb0297cc4f50bf34d944488d7ceb2ca2.png
Double-check the screenshots out of an abundance of caution.

2026-07-30 19:03:25 CEST

#pyramid hosting made easy: #nevent1q…cxtc
(It's already live.)

2026-07-30 18:43:54 CEST

- reply

You are free to not look at them, you are free to block them in your relay, but you can stop people from writing whatever junk they want in their own relays (or whatever other relays that decide to accept them).

2026-07-29 03:51:11 CEST

- reply

Or I can wait and ask someone who went.

2026-07-29 03:50:13 CEST

- reply

No, it doesn't. You connect to random relays and fetch only from specific authors from such relays, that's in one scenario.
Then there is a different scenario in which you want to open yourself to reading stuff from strangers, in that scenario you choose relays wisely and take what they give you.
That's the fundamental duality of Nostr, or something. @npub1t6j…ksrw has written many notes about it, made videos, even gave a talk about it. He explains it better.

2026-07-27 13:09:18 CEST

- reply

By the way, if you disagree with this, please let @npub1t6j…ksrw know how wrong you are and how much you want to learn the correct ways and he will gladly bash you in the head with the truth for hours if necessary.

2026-07-27 12:46:37 CEST

To everybody else and not only @npub1q3s…d26p, if you have any disagreements about this please voice them so you can be enlightened:
#nevent1q…mncv

2026-07-27 12:44:21 CEST

Please spread this message, follow, repost, like, subscribe, retweet, boost, share with your friends and family, bookmark, upvote:
#nevent1q…ess2

2026-07-27 12:25:11 CEST

- reply

Wrong, the only scalable and decent way to prevent against spam is by picking relays that enforce limits and reading from such relays on a case-by-case basis.
If you rely on an "authors" filter and blind relays you're limiting yourself to only ever seeing stuff from people you know and never learning that other people exist in the world -- or every client has to perform complex and costly computations locally that then make that "authors" list so big that relays will rightfully reject it.
In other words: enforcing restrictions once per write is much more effective and efficient than trying to enforce them on every read.

2026-07-25 02:20:01 CEST

- reply

@npub15qy…yejr is cooking faster.

2026-07-25 02:19:16 CEST

- reply

I'm maintaining this one: https://nostr-protocol.github.io/registry-of-kinds/
But it's not pulling data from relays, it is manually documenting the tags and type of content expected for each kind: https://github.com/nostr-protocol/registry-of-kinds/blob/master/schema.yaml

2026-07-25 02:15:16 CEST

- reply

No, no DMs were supposed to be sent. I meant just the webpage buttons that you pressed to request access and that kind of thing.

2026-07-22 16:42:16 CEST

- reply

Yes, feature requests are very welcome.
What is the point of a Blossom cache? You mean downloading files and saving them locally?

2026-07-22 13:33:18 CEST

- reply

Thank you for letting me know, should be fixed now in v0.20.2.
Please send more small issues if you have them.

2026-07-22 02:47:30 CEST

I finally managed to log in to Armada in my 4th attempt in a week and the first thing it did was to nuke my NIP-29 groups list.

2026-07-20 02:52:36 CEST

- reply

I agree that trying to build "everything" on Nostr is a bad strategic error. Specially when these things are even more dependent on network-effect than a microblogging social network (like uber or Nostr, for example) or when they depend on private communications. People have been trying to do this since day one, though, it's just something wrong with the mind of developers.
But I think tools that are "social" in nature and mostly involving publishing human-scale content in the open but don't require that the entire world is using them in order to be useful (like geocaching, for example) are good niches through which Nostr can expand.

2026-07-20 02:35:42 CEST

- reply

Yes, but people choose what torrents they seed.

2026-07-19 19:10:46 CEST

- reply

No, I hate satellites.

2026-07-18 17:53:10 CEST

- reply

Gold is used as a financial instrument and most of its value come from that.
It would be same with Bitcoin, as long as it was perceived as money by normal people. The moneyness of Bitcoin would form the core of its value on top of which other types of demand would be stacked.
With Gold I believe it has a fundamental demand for jewelry and other small use cases, and on top of that there is a vast amount of financial use cases that make its value be much bigger than that of other rocks.
In both cases if you remove the fundamental source of value the thing tends to zero.

2026-07-18 17:34:41 CEST

- reply

I always say this. Basically everything we do on Nostr is "social" in some way, but if everybody reads "social" and immediately assumes it's just microblogging then I don't know what to do.

2026-07-18 12:47:45 CEST

- reply

I thought bolt12 had already solved everything 8 years ago, or maybe when it was actually finished 2 years ago?
I think waiting another 8 years should do the job. I know that is a good idea because we are early and Bitcoin has already won.

2026-07-18 04:16:15 CEST

Finally a client that allows me to browse only through @npub1jlr…ynqn's notes in Latin: https://spatia-arcana.com/198225f2f09789a1566ad3b5053df3b5d51c3e2541cc627d2864e089aefd888a.png

2026-07-18 02:57:53 CEST

Welcome to wss://pyramid.fiatjaf.com, @npub18mf…nyu5. Did the invite flow work reasonably well?

2026-07-18 02:55:13 CEST

- reply

Looks like a good idea to me.
The problem is getting the rest of the world to notice it and add support.

2026-07-17 21:17:59 CEST

- reply

These days it's getting increasingly harder to find people who actually believe the goal of Bitcoin is to end fiat. Even in this trailer, only @npub1t28…nkzs said it explicitly, I wouldn't be surprised if all these others were more worried about other things that aren't clear and didn't care if Bitcoin remained a niche useless rock forever.

2026-07-17 02:45:42 CEST

- reply

What happened with supposed thousands of drones that were flying all over New Jersey 2 years ago?

2026-07-17 02:40:51 CEST

- reply

I use a desktop.

2026-07-17 02:31:47 CEST

Few things on the internet are worse than the fad of "vertical short videos".

2026-07-16 17:09:32 CEST

Relays that want to be public or semi-public need more ways to discern an npub that has a real person behind it from an automated sybil attack, and this is a great idea.
But instead of selling npubs someone should sell badges.
But if you're doing it from a physical location then a badge could just be given for free as long as the process can't be automated.
#nevent1q…c33p
Then we will just need someone to manually collect a list of of these badges are worth an npub be recognized as a human and relays can pick from that.

2026-07-16 17:01:01 CEST

- reply

It's not that these people need Bitcoin or anything, it's that the people who need it need that these people also use it, so they have to be led into using it even though they don't care.
There is also the greater goal of starving the State and associated evil elites of their money-printing machine, and that can't be achieved unless basically everybody is using money they can't print.

2026-07-16 16:48:46 CEST

- reply

> IF you want to move from one context to another then you have to generate the ZK proof
I don't understand. What is this ZK proof you're talking about and what are these "contexts"?

2026-07-16 14:40:59 CEST

- reply

I did, it is better, but also kinda sucks. In my understanding you have to rely on some big servers that keep the full history of all nullifiers forever so they can compute proofs on behalf of normal users. How much can that scale, if each person is making 3 transactions per day, and if each transaction will use more 2 nullifiers on average due to mixed inputs? That's over a petabyte per year just in storage.
Or maybe I misunderstood the requirements. Clarifications welcome.

2026-07-16 14:37:18 CEST

- reply

It's not clearly self-custodial. Nothing is clear, everything is awfully confusing and that's how everybody is tricked about the claims of Spark, but not only Spark, it also applies to Ark and Lightning itself.

2026-07-16 14:34:43 CEST

- reply

Yes, I'm super married to a $5 airdrop I will be getting, already making plans to buy a bag of milk with it.
What is the flaw in hashrate escrows?

2026-07-16 14:34:26 CEST

- reply

This is true. If Monero adopted Drivechains I think it could become a real contender. Still, though, it would have to migrate most of its activity to the sidechain and make mainchain very small, in that sense it would be basically the same as eCash, only with a bigger initial user base and name recognition.
The bigger question to me is: can Monero scale to billions of people via Thunder-style sidechains but with Monero technology? If yes then those sidechains should probably be used in eCash instead, but I don't know.

2026-07-16 13:40:39 CEST

- reply

Even if we assume away the problem of data availability it wouldn't be great to have the entirety of the world's monetary transactions depend on a single company building the blocks and publishing zk-proofs. I guess you can say this block generation can be made to be more open, but I think the incentives are that it would be very centralized regardless, no?
It's a similar problem of Spark: even if you could make it be totally trustless it would still be bad for it to be controlled by a single company.

2026-07-15 13:21:47 CEST

- reply

I used to think there were two ways of scaling Bitcoin: one would be with trusted entities, i.e. banks, but deployed in a decentralized way that limited liability and government capture, and the other way was with Drivechain.
Given what we're seeing with all the Lightning custodial wallets being targeted, implementing full KYC and migrating to Spark (which is becoming almost the one world central bank) that first option is looking worse.
(To be fair my plan was never to have these companies be the custodians in the first place, but it was a bad plan anyway.)

2026-07-15 13:18:31 CEST

- reply

Correct, but Zcash, Monero and BCH are all unscalable to billions too (like Bitcoin, although Bitcoin has made all the influencers believe it could do the scaling "in layers" for the last nine years).

2026-07-15 13:11:32 CEST

Finally a client that displays same-author "threads" in the old Twitter style:
https://c.nostr.media/233/a9e/233a9e01606252d00d8be83e3f2b77acfcd41b367cbb1afb3179dd5b6b0ff1e3.png
https://c.nostr.media/531/9e6/5319e6957e34831c0bc0ec7bd4acfb7029d293329bbc705c47f7b90c73f303a0.png

2026-07-14 19:20:22 CEST

- reply

I'm helping them embrace the chaos.

2026-07-14 19:19:22 CEST

Look at this amazing video about bananas:
#nevent1q…vj3x

2026-07-14 06:58:20 CEST

- reply

It is truly awful.
But the solution is simple.

2026-07-14 03:50:52 CEST

- reply

But can anyone run a Windows executable on their computers without having to click on weird places in order to authorize the execution of malware?

2026-07-14 03:47:28 CEST

paru -S nostrord-bin

2026-07-14 03:38:20 CEST

Finally a way to reply to multiple notes at the same time:
https://nostr.media/0e95ec049a29de25c23623403b694394032f66931bdb1974eca24f26c5fe5b03.png

2026-07-13 00:13:09 CEST

- reply

The video in this page is good if you want a short talk: https://drivechain.xyz/
If you prefer to read then maybe start with the article I wrote when I finally understood the idea many years ago (on that page). Paul Sztorc's explanations apparently don't click easily for most people, but to me they are pretty good. I guess you have to try multiple of these explanations from others until one of them makes sense.
Drivechain enables so much it's hard to describe, we wasted too much time defending the idea from bad repeated criticisms we forget to advertise the benefits:
- absurd self-custodial scaling for payments, such that Bitcoin payments for everything everywhere can finally be a reality;
- enabling everything that can be imagined as working on a "blockchain" immediately in Bitcoin without reducing decentralization;
- all the network-effect, developer time and interest ever poured into other shitcoin projects going back to Bitcoin to make it immediately at least 3x in size and importance from the getgo (with of course much more growth that will come from this);
- perfect privacy (not for all forms of transactions, but at arms reach of anyone -- and could be the default for most payments);
- fixing the security budget (Bitconeirs in general like to forget about this, but someone has to pay the miners) while keeping transactions cheap for everybody;
- finally a chance that Bitcoin will replace fiat once and for all and become the money of the world.

2026-07-12 23:46:22 CEST

- reply

Many otherwise intelligent people have this condescending attitude too. I understand it looks more serious and conservative to "accept" the forms of organizing society supposedly created by our forefathers (or whatever). But that by itself doesn't constitute an argument or a solid position to hold.
I think the mistake you and others make is that they compare a relatively good government that a very civilized society has created with what they imagine would be "anarchy" for a very barbaric and messy population. So the comparison is not apples to apples.
I guess there is also some missing details about how absurdly bad governments can be. The bar is really low.

2026-07-12 12:52:24 CEST

- reply

It doesn't have to be perfect, it just has to be better than a system of anarcho-tyranny in which a bunch of pedophile psychopaths enslave the rest of the population.

2026-07-11 17:00:17 CEST

- reply

1. Bitcoin can only be saved by activating Drivechain.
2. Core will never merge or support Drivechain activation (or any soft-fork).
3. Miners won't move their asses until they see sufficient real-world evidence.
Any reasonable Bitcoiner accepting these premises should support the eCash hardfork even if they are initially disgusted by the idea of betraying the Bitcoin brand and the maximalist cult (I was myself), because from these premises we have to conclude that the only thing that can save Bitcoin is a real-world thriving ecosystem of useful sidechains paying fees to miners that finally convinces them to activate Drivechain via CUSF.

2026-07-11 16:47:26 CEST

- reply

What does that mean? We chose something and we can never change our minds? No one should have a blind devotion to Bitcoin. Bitcoin was always only our best chance of fixing the problem of government monopoly over money issuance and related evils, not an idol to be worshipped.
If we spot something else that might give us a better chance we should definitely switch immediately.
With that said, Bitcoin is still miles ahead of anything else. If eCash proves to work even a little bit we may have a better chance of miners activating it on Bitcoin and that will be great.
If not, and if Bitcoiners don't come up with any better solutions (it is very unlikely they will, and even if they get a better solution it is even more unlikely that they will be able to activate it) that will mean that Bitcoin will die slowly over many decades. This will be bad as most people will not see it happening. Our only hope in this case is that eCash captures more users from outside the current Bitcoin sect and gets bigger faster than Bitcoin gets smaller. I guess this will have to happen anyway if it has any chances anyway.

2026-07-11 15:22:52 CEST

- reply

Because of custodial regulation all Lightning wallets are migrating to use Spark, which claims to be noncustodial.
But Spark is a central server that sees everything, can block anything and whose claims of "unilateral exit" are at best vastly oversold: https://xcancel.com/francispouliot_/status/2075284584489439668 (see how even at 1sat/vb and a small amount of users -- meaning small transaction trees -- you already lose 10% of your money, at 5sat/vb you lose 40% and so on).
In fact the situation is only getting worse. Before we had a dozen of different custodians spreaded throughout the globe, soon it will be a single proto-custodian controlled by a US corporation.