William Casarin (jb55)

People14 min readHuman profile

William Casarin (jb55)

William Casarin made Nostr feel touchable on iPhone through Damus.

The iPhone moment for Nostr

William Casarin, better known in the code world as jb55, matters because he made Nostr feel less like a protocol rumor and more like something you could actually open on your phone. Damus was not the first Nostr idea, and Casarin did not create the protocol. But for a large group of people, Damus was the first time Nostr looked like a social app instead of a GitHub thread.

That distinction is important. Early protocols often live too long in the builder room. Everyone involved understands the primitives, but outsiders see a fog of keys, relays, clients and strange handles. Damus gave iPhone users a recognizable surface: a timeline, profiles, notes, private messages, follows, reactions and eventually zaps. It let people try Nostr with their thumbs.

TechCrunch captured the shift when Damus hit the App Store in early 2023. The article framed it as the first mobile app to leverage Nostr and arrive at a moment when people were looking for alternatives to Twitter. That timing gave Damus a job bigger than a normal app launch. It had to explain Nostr by being usable.

A Bitcoin and Lightning developer walks into social media

Casarin did not come to Nostr as a media founder chasing a feed trend. His public background sits closer to Bitcoin and Lightning. Bitcoin Magazine described him as a developer previously working on the Lightning network, and longer interviews around Damus keep returning to the same point: he saw Nostr as social media with a Bitcoin-native payment layer nearby.

That background shaped the app. Damus did not treat money as a later monetization feature. Zaps became part of the social gesture. A user could like a note, reply to it, repost it, and also send a small Lightning payment. That sounds simple now because Nostr culture absorbed it quickly. At the time it was a very direct challenge to the way social platforms and app stores think about money.

The point was not only tipping. Zaps made value part of speech without forcing every creator into ads, subscriptions or platform-controlled monetization. Casarin's contribution here was product and culture at once: he helped turn Lightning payments from a wallet demo into a social reflex.

Damus as a product statement

The Damus site says the quiet part directly: no ads, no toxic algorithms, no censorship, user control over data and speech. That is strong language, and a product has to earn it. Damus tried to earn it by making the client feel simple enough for normal use while keeping the account model rooted in Nostr keys and relays.

The App Store listing is useful because it shows the consumer pitch stripped down for mobile users. No phone number, email or name required. Messages distributed through decentralized relays. End-to-end encrypted private messaging. A social network for friends or business where there is no single platform that can ban or censor you. Whether every claim is perfect in practice is a separate question; the pitch is clear.

Casarin's role was to turn that pitch into screens. That is harder than protocol people sometimes admit. A raw Nostr client can expose too much, too early. A smooth one can hide so much that users forget what makes Nostr different. Damus walked that line in public, in the most opinionated mobile ecosystem in the world.

The Apple fight made zaps political

The most public Damus fight came from Apple, not from another Nostr client. In 2023 Apple threatened to remove Damus from the App Store over zaps. The issue was whether Lightning tips attached to posts counted as digital content payments that should go through Apple's in-app purchase rules.

TechCrunch reported the dispute as an app-store payment fight, but for Nostr users it became more than policy language. It showed exactly why Bitcoin-native social payments are uncomfortable for platforms. If users can send value directly after a post, and if that payment does not unlock content inside the app, where does Apple's tollbooth fit?

Damus eventually stayed in the store after changes, as Decrypt reported, but the fight left a mark. It made Casarin's work feel less theoretical. Nostr was no longer only a conversation about censorship resistance and user-owned identity. It was colliding with the rules of the device ecosystem that controls how millions of people install software.

That collision is part of Casarin's biography because he chose the hardest place to prove the point. Building an open social client on the open web is one thing. Building it for iOS means dealing with Apple review, payment rules, regional takedowns, push notifications, signing, privacy labels and a user base trained to expect everything to just work. Damus brought Nostr into that controlled room and forced the contradiction to show itself.

China, app stores and the censorship claim

Damus also met censorship pressure almost immediately. Coverage from AppleCensorship noted that the app was removed from China's App Store shortly after launch because of directives from the Chinese government. That is a hard test for any app that talks about censorship resistance. The protocol can remain open while a national app store can still block a client.

That difference is important. Casarin did not build an invisibility cloak. He built an iOS app for an open protocol. If a government or platform blocks the app, the user's key and the network's data model can still matter, but access has to move through other clients, other stores, other devices or the web. That is the grown-up version of censorship resistance: not immunity, but more routes around the gate.

For readers, this makes Damus more interesting than a clean success story. It shows where open protocols meet closed distribution. Casarin's work lives right at that boundary. He wants the user to own identity, but he still has to ship through an ecosystem where Apple controls the doorway for iPhone users.

Why zaps changed the culture

Zaps are small, but culturally huge. They make appreciation measurable without turning everything into a subscription. A funny note, a useful thread, a live stream, a song, a tutorial or a bug fix can receive money in the same place where people discuss it. That collapses social feedback and economic feedback into one gesture.

Casarin's name is tied to that shift because Damus helped make zaps visible to everyday users. OpenSats' long-term support post credits his development of Damus with advancing Bitcoin integration into social networking through pioneering zaps. That is not just a feature bullet. It is one of the reasons Nostr feels different from other open-social attempts.

The best zaps do not feel like monetization. They feel like someone buying you a coffee across the internet. The worst version could become noisy, performative or status-obsessed. Casarin's work did not solve that cultural tension, but it created the surface where the experiment could happen.

Notedeck, nostrdb and the second layer

Damus made Casarin visible, but the later work is just as important. OpenSats lists Notedeck, NostrDB and Notecrumbs alongside continued Damus development. That tells you the biography is not only an iPhone story. It is a client-infrastructure story.

Notedeck points toward a multiplatform Nostr client. That matters because a serious social protocol cannot live inside one mobile app, even a successful one. The user should be able to move across desktop, mobile and different interfaces without losing identity. A good client becomes a room; the protocol keeps the doors open.

nostrdb is more technical, but it matters for speed and local control. Nostr clients need to store, query and render large piles of events quickly. If every interaction feels slow or dependent on remote services, the user will not care how elegant the protocol is. Casarin's database work shows a builder thinking beyond the feed and into the local machinery that makes a feed feel alive.

The boring parts that make social apps feel fast

A good social app looks simple when it works. You open it, the feed appears, profiles load, replies make sense, images and links render, search does not feel broken and the app remembers enough state that you do not feel lost. Under Nostr, none of that is automatic. Events arrive from relays. Clients cache. Profiles change. Threads can be spread across the network. A fast app needs local intelligence.

That is why nostrdb belongs in Casarin's biography. It is not glamorous, but it points at the real bottleneck. If Nostr is going to compete with platform apps, clients cannot behave like fragile relay viewers. They need local databases, fast queries, smart indexes and sane rendering. Otherwise the open protocol will feel slow next to the closed platform, and most users will choose the thing that feels alive.

Notedeck has a similar meaning. It shows Casarin trying to move beyond the single iOS doorway and toward a broader client experience. That matters because a protocol should not be trapped inside the first successful client. Damus can be the door that made Nostr visible. Notedeck can be part of the next question: what does a serious, multiplatform Nostr workstation look like when it is built by someone who already fought the app-store battle?

The product tension around jb55

Casarin sits in one of the most difficult positions in Nostr. Protocol purists want clients to expose the network's real shape. Normal users want things to be obvious. Apple wants rules followed. Bitcoiners want zaps to work. Developers want performance. Privacy-minded users want fewer leaks. Every decision in a client like Damus touches one of those groups.

That is why Damus can be praised and criticized at the same time. It made Nostr easier, but no client can make keys, relays, payments and moderation disappear without changing what the network is. Casarin's work keeps returning to that line: simplify enough for humans, but not so much that the app becomes a soft platform.

The best reading of jb55 is not that he solved mobile Nostr. He made the problem visible. Before Damus, it was easy to talk about a decentralized social protocol in theory. After Damus, the questions became practical: how should onboarding work, where should zaps live, what can Apple block, how fast can a client feel, and how much of the protocol should a normal person ever have to see?

The human detail in the work

There is not much need to reach for private biography with Casarin. The public work already shows the person clearly enough. He is a builder who likes hard edges: iOS, Lightning payments, local databases, open protocols, app-store rules and the point where ideology becomes an interface.

That kind of builder is valuable because Nostr has plenty of philosophy. It needs people willing to deal with the boring fights that philosophy creates. Who hosts the app? Who approves the update? Where does the money button sit? What happens when Apple says no? How does a client stay fast? How do users know they still own the account? Casarin's biography is the record of someone answering those questions in public.

The press attention around Damus sometimes made it sound like another Twitter rival. That label was never enough. Damus was a test case for a bigger claim: that a social app could be familiar enough for mobile users while depending on a network that no single company owns. That is why the app-store fights and database work belong in the same profile. They are two sides of the same job.

What changed after Damus

After Damus, Nostr had a different kind of proof. It had already proven that builders could publish notes through relays. Damus proved that a normal-looking mobile app could sit on top of that model. It also proved that direct Lightning payments would make platform owners nervous, because the payment rail was no longer neatly inside their business model.

It made the rest of the client ecosystem more serious. Amethyst had to show what Android could do. Primal had to show what a consumer social layer could feel like. Coracle had to show why web-of-trust and relay choice mattered. noStrudel gave builders a cockpit. Damus held the iOS line and made zaps part of the public imagination.

That is the right scale for Casarin's role. He is not the whole Nostr story, but one chapter cannot be written without him. If fiatjaf gave the network a primitive base, Casarin gave it one of its first everyday faces.

The kind of builder he is

Casarin's public trail reads like someone who likes the product surface but does not trust it alone. He builds apps, but he also builds the lower pieces. He talks about social media, but keeps Bitcoin and Lightning close. He wants Nostr to be usable, but not so abstracted that the user forgets the escape hatch.

That combination is why his work matters to both normal users and protocol people. Damus gave the network a social face. zaps gave it a payment reflex. nostrdb and Notedeck point toward a more serious client stack. The work moves between user experience and infrastructure instead of choosing one permanently.

There is a personality visible in that movement. Casarin does not come across as a pure marketer. He is a builder who got pulled into the public argument because the thing he built made the argument real. The App Store fight, the zaps debate and the launch coverage all happened because Damus was not only an idea. It was a shipped app in a controlled ecosystem.

The interviews show the early bet

The long Bitcoin Fundamentals interview is useful because it catches Casarin close to the early explosion. He explained Nostr through fiatjaf's original idea: a simple way to build a Twitter-like social network without control by a single party. He also described seeing the technology, deciding to build a client and being surprised by how simple and impressive the base design was.

That early tone matters. Casarin was not describing a finished consumer category. He was describing a protocol that had suddenly become exciting because it was simple enough for builders to understand and weird enough to attract people frustrated with centralized social media. Damus came from that moment: part engineering reaction, part Bitcoin-culture instinct, part product opportunity.

The same interview connects Damus to Lightning in plain language. If Nostr made speech portable, Lightning could make small payments portable inside that speech environment. That pairing became one of the reasons the Bitcoin world adopted Nostr so quickly. It was not just another feed. It was a place where money could move at the same speed as a reply.

Why Damus mattered beyond iOS

Damus mattered even to people who never used iOS because it made the protocol publicly legible. A working iPhone client creates screenshots, app-store pages, reviews, press coverage and social proof. That sounds superficial, but early networks need those surfaces. They tell outsiders that the thing exists in the world, not only in developer chat.

It also raised the bar for other clients. Once Damus showed that Nostr could be an app-store product, Android clients, web clients and desktop clients could no longer hide behind protocol purity. Users had seen a front door. They could ask why another client was harder, slower or uglier. Competition became more real.

At the same time, Damus proved that product polish brings platform pressure. A rough command-line tool can avoid Apple. A popular iPhone client cannot. Casarin's work therefore sits at the exact place where Nostr has to mature: enough polish for normal users, enough openness that the polish does not become another trap.

His role in Nostr now

In the Nostr ecosystem, William Casarin is the iOS doorway, the zap pioneer and one of the builders proving that client polish does not have to mean platform capture. He sits in a different place from fiatjaf. fiatjaf made the primitive weirdness. Casarin made that weirdness feel like something a person could install.

That role is easy to underrate after the fact. Once a protocol has many clients, the first usable mobile surfaces can look obvious. They were not obvious. Someone had to decide which complexity to show, which to hide, how to explain keys, how to make relays feel less strange, and how to bring Lightning into the product without making the app feel like a wallet tutorial.

Damus did not solve Nostr onboarding forever. No client has. But it gave the ecosystem a proof that Nostr could live in the App Store, attract normal curiosity and force Apple to react to open social payments. That is a real chapter in the network's history.

The biography in one line

William Casarin is the builder who turned Nostr from a clever protocol into an iPhone habit. Damus gave people a way in. Zaps gave the feed a money pulse. Notedeck and nostrdb show that he is still working below the surface, where good clients become serious software.

His story is not just about one app. It is about the moment open social left the developer room and had to deal with users, app-store rules, payment rails, performance, design and public attention. That is why jb55 belongs in the People archive as one of Nostr's core product builders.

The simplest read is this: fiatjaf made Nostr small enough to build on. Casarin made it visible enough for people to care.

Sources worth opening

• DamusPrimary product page for Damus and its control-your-own-social-network positioning.
• Damus App StoreApple listing for Damus, including the open-protocol positioning and privacy claims.
• TechCrunch on Damus launchLaunch coverage describing Damus as the first mobile app to leverage Nostr on the App Store.
• TechCrunch on Apple's zap disputeReporting on Apple's threat to remove Damus over zaps and the app-store payment conflict.
• Decrypt on Damus and AppleFollow-up on Damus remaining in the App Store after changes around zaps.
• OpenSats project: DamusPrimary OpenSats project page covering Damus, Notedeck, NostrDB, Notecrumbs and grant history.
• OpenSats LTS for William CasarinPrimary long-term support announcement for Casarin's Damus, Notedeck, NostrDB and Notecrumbs work.
• Damus repositoryPrimary iOS client codebase.
• Notedeck repositoryMultiplatform Nostr client repository connected to Casarin's next product layer.
• nostrdb repositoryEmbedded database work for faster local Nostr event handling.
• GitHub: William CasarinPrimary public developer profile.
• Bitcoin Fundamentals interviewLong interview source on Damus, Nostr, Bitcoin and the early client story.
• Bitcoin Magazine backstage interviewVideo/interview context around Damus and Casarin's Bitcoin/Lightning background.