Nostr notes by jaredlogan

Wow. Not sure of the details, but I will be taking this to prayer ...

2026-08-07T19:34:08Z

In reply to nevent1q…s0xd
_________________________

Wow. Not sure of the details, but I will be taking this to prayer today at the cathedral in my area. 🫡 🙏

God Bless you brother and your wife and family.

'Somewhere in the walls, relays clicked...'

2026-08-04T16:30:18Z

In reply to nevent1q…twzx
_________________________

'Somewhere in the walls, relays clicked...'

https://gifverse.net/media/acxiRtp8/original.gif #nevent1q…e28d

2026-08-04T15:37:35Z

quoting
nevent1q…e28d
“Bitcoin's anarchy, right? It does not have religious attribution, it does not have political attributions, it doesn't have fucking anything. It's just a mathematical system with extremely conservative economic values and full anarchy." NVK (nprofile…w428) w walker (npub1cj8…rz4u)

nevent1q…a2c6

Any O'Reilly usually has them on the shelf.

2026-08-02T20:21:14Z

In reply to nevent1q…zcz0
_________________________

Any O'Reilly usually has them on the shelf.

If you know what this, I want to be your friend. ...

2026-08-02T19:50:55Z

If you know what this, I want to be your friend.

Nostr event nevent1qqsfe5f2h8q9v3qh92qeuvqm30ph7qfkcagqt9eqeh4jzuct5499jtczyq53cawex7j97e4pyz0cafnprhm5frzekdfx2gxxdj3vmnfh7xlmuhswfkk

2026-08-01T21:51:04Z

In reply to nevent1q…pd96
_________________________

naddr1qvzqqqr4gupzq9h35qgq6n8ll0xyyv8gurjzjrx9sjwp4hry6ejnlks8cqcmzp6tqq98yetnd9nkuttwwe4sst55nt

https://gifverse.net/media/IgOeKOSQ/original.gif

2026-07-31T18:46:54Z

In reply to nevent1q…j8ha
_________________________

This was exactly what I was thinking as I asked the question. ...

2026-07-31T18:37:04Z

In reply to nevent1q…g8ua
_________________________

This was exactly what I was thinking as I asked the question. When is it completely trustless / can it be?

I'd argue if you let even audited firmware generate your ...

2026-07-31T17:30:20Z

In reply to nevent1q…sr4c
_________________________

I'd argue if you let even audited firmware generate your seed, you're shifting trust to the audit. Unfortunately, it appears nobody audited.

Would you say hand rolling and hashing requires trust? Genuinely asking, for the sake of exploring my own thoughts on this.

A lot of people heard 'Don't trust, verify', and ...

2026-07-31T17:22:21Z

A lot of people heard 'Don't trust, verify', and trusted without verifying.

💔

As of now, still using a Q. Emphasis on using my own entropy + ...

2026-07-31T17:03:16Z

In reply to nevent1q…vdrl
_________________________

As of now, still using a Q. Emphasis on using my own entropy + passphrase + multisig as I would with any hardware wallet.

Always verify software and firmware. Stay diligent. I first rolled a device driven seed and couldn't stop thinking about scenarios exactly like this.

Not enough people talk about Tails

2026-07-31T16:16:55Z

In reply to nevent1q…4j8n
_________________________

Not enough people talk about Tails

https://www.pullthatupjamie.ai/

2026-07-30T16:11:08Z

In reply to nevent1q…zrfq
_________________________

https://www.pullthatupjamie.ai/

Maybe @nprofile…5mhl

2026-07-30T16:08:18Z

In reply to nevent1q…rk6x
_________________________

Maybe jamie_bot (nprofile…5mhl)

Congrats man! Beautiful to hear. ❤️

2026-07-29T03:02:02Z

In reply to nevent1q…4rgx
_________________________

Congrats man! Beautiful to hear. ❤️

This is the way. Nukes a couple of my pain points with Buzz so ...

2026-07-25T23:17:50Z

In reply to nevent1q…2t5w
_________________________

This is the way. Nukes a couple of my pain points with Buzz so far.

I'll have to try out Concord. What's different for you ...

2026-07-25T23:15:35Z

In reply to nevent1q…qquf
_________________________

I'll have to try out Concord. What's different for you there?

When using an agent I like to be real specific with my permissions. Buzz seems to be all or nothing, or maybe I just didn't spend enough time with it.

Trying not to be cynical, but raw nsec dumping, email request, and closed source provider preference give me some ick. I may need to play and investigate more.

I've tried to build lightning hold em. Still got some work to ...

2026-07-25T20:00:20Z

In reply to nevent1q…w9w5
_________________________

I've tried to build lightning hold em. Still got some work to do.

Is it just me or does Buzz seem like a huge security and privacy ...

2026-07-25T18:45:49Z

Is it just me or does Buzz seem like a huge security and privacy concern?

We did it ❤️

2026-07-24T20:21:34Z

In reply to nevent1q…ffcj
_________________________

We did it ❤️

Soon, friend. Soon. 🤙

2026-07-22T19:33:17Z

In reply to nevent1q…3ay0
_________________________

Soon, friend. Soon. 🤙

https://gifverse.net/media/skbvMurc/original.gif

2026-07-22T19:32:28Z

In reply to nevent1q…d8vt
_________________________

Thank you 🍻

2026-07-22T19:31:49Z

In reply to nevent1q…twwu
_________________________

Thank you 🍻

It is good indeed.. There are little to no words to describe it. ...

2026-07-22T19:31:14Z

In reply to nevent1q…mav4
_________________________

It is good indeed.. There are little to no words to describe it. 🙏

Feels unreal, but it's the most amazing thing in the world. ...

2026-07-22T19:29:20Z

In reply to nevent1q…ml5p
_________________________

Feels unreal, but it's the most amazing thing in the world. 🤙

Thank you kid! https://gifverse.net/media/CN4A3rQz/original.gif

2026-07-22T19:28:33Z

In reply to nevent1q…f6sl
_________________________

Thank you kid!

Hi! I'm officially a dad now. K bye 👋

2026-07-19T19:08:16Z

Hi! I'm officially a dad now.

K bye 👋

:Nori:

2026-07-15T21:18:42Z

In reply to nevent1q…g2xg
_________________________

:Nori:

Counting the days! 🤪 Let's make it happen!

2026-07-14T22:35:41Z

In reply to nevent1q…h8y7
_________________________

Counting the days! 🤪 Let's make it happen!

One day I'll chuck a jig on that water ...

2026-07-14T22:00:17Z

In reply to nevent1q…wkjt
_________________________

One day I'll chuck a jig on that water

https://gifverse.net/media/yisbG1SD/original.gif

2026-07-14T21:29:20Z

In reply to nevent1q…u08s
_________________________

1 baby! 😂 our first. We are now 48 hours past due date. ...

2026-07-13T13:44:10Z

In reply to nevent1q…fmpx
_________________________

1 baby! 😂 our first. We are now 48 hours past due date. Scheduled induction Friday / Saturday, so he will be here by Sunday at the latest unless he arrives naturally ahead of that.

Wife is uncomfortable, but we are making it. She's a trooper.

PV Derek! 🤙

2026-07-13T12:50:56Z

In reply to nevent1q…ex6e
_________________________

PV Derek! 🤙

dude....

2026-07-10T00:04:37Z

In reply to nevent1q…lf9f
_________________________

dude....

The stoke could not be higher. 🙏

2026-07-10T00:00:21Z

In reply to nevent1q…uyz8
_________________________

The stoke could not be higher. 🙏

2 days until my boys due date. Everything is happy and healthy on ...

2026-07-09T23:56:58Z

2 days until my boys due date. Everything is happy and healthy on my side. Hopefully you're doing well NOSTR crew. Will be active again soon! But for now, we pray for delivery to go easy 🙏

God bless you!

- J

:monstrance:✝️🕊️

This is an issue I've noticed within several clients ...

2026-06-29T21:27:04Z

In reply to nevent1q…emsa
_________________________

This is an issue I've noticed within several clients returning the profile data when needed. Sometimes it's slow to do so, and sometimes it feels dependent on my network speed (or poor mobile connection).

I'll have to investigate this one a bit more to see if I can improve it, and I may not have a chance to do so until this weekend. But I'll keep you posted!

Where can I check it out 👀

2026-06-25T20:17:54Z

In reply to nevent1q…874w
_________________________

Where can I check it out 👀

Absolutely stoked to say the least! Thank you sir!

2026-06-24T13:49:38Z

In reply to nevent1q…u0xu
_________________________

Absolutely stoked to say the least! Thank you sir!

All love! Thank you!

2026-06-24T13:48:54Z

In reply to nevent1q…z94t
_________________________

All love! Thank you!

Thank you sir!

2026-06-24T13:48:28Z

In reply to nevent1q…u9f6
_________________________

Thank you sir!

Hey NOSTR Been a little quiet here for me recently as we've ...

2026-06-24T02:31:37Z

Hey NOSTR

Been a little quiet here for me recently as we've been hard at work preparing things for some big changes. Hope you're all doing well 🙏

Wifey and I have come a long way since the days of owning no furniture and eating meals on the floor. The nursery is only lacking the finishing touches of the handmade curtains and shades from grandma and it'll be complete.

I cant believe I get to meet my firstborn here in just a couple weeks at most. ❤️

Here's a little before and after refinishing the wood floors and assembling the room. And the peaks I've been getting our little one along the way.

K that's it. Just thought I'd check in.. Talk soon.

https://media.tenor.com/Xp27PoT1pL4AAAAC/enorym-pssh.gif

2026-06-17T18:43:19Z

In reply to nevent1q…mq2q
_________________________

“The Sabbath was Saturday, not Sunday. The Church altered the ...

2026-06-17T00:45:53Z

“The Sabbath was Saturday, not Sunday. The Church altered the observance of the Sabbath to the observance of Sunday. Protestants must be rather puzzled by the keeping of Sunday when God distinctly said, ‘Keep holy the Sabbath Day.’ The word Sunday does not come anywhere in the Bible, so, without knowing it they are obeying the authority of the Catholic Church.”

— Canon Cafferata, The Catechism Explained, p. 89.

Amen brother!

2026-06-15T00:18:56Z

In reply to nevent1q…hgcz
_________________________

Amen brother!

The Catholic Church does not affirm gay marriages as Sacramental ...

2026-06-14T21:10:57Z

In reply to nevent1q…0y87
_________________________

The Catholic Church does not affirm gay marriages as Sacramental and any priest or parish that does is acting in grave violation of Church teaching and canon law and in defiance of the Magisterium.

Accepting with respect, compassion, and sensitivity while avoiding unjust discrimination, is not 'affirming' them.

Just because a handful of dissenting or unofficial-Catholic congregations listed themselves, does not mean RCC affirm LGBTQ+.

CCC 2357, 2358, 2359, 1601, 1603, 1625, 2360–2365, 1664.

Please don't use skewed data sources to bash the Church and frame it incorrectly. You know this. Shame on you.

GM NOSTR A beautiful day to celebrate the mass ✝️ Enjoying ...

2026-06-14T14:06:05Z

GM NOSTR

A beautiful day to celebrate the mass ✝️

Enjoying this beautiful dialogue between Trent and Bryce about exploring Catholicism as a Protestant. Charitable discussions are so inspirational.

https://m.youtube.com/watch?v=oNWseAsfcGM

we were here ...

2026-06-13T12:49:12Z

In reply to nevent1q…myp3
_________________________

we were here

Anyone else have massive issues using external SSDs with ...

2026-06-10T19:23:44Z

Anyone else have massive issues using external SSDs with umbrel (npub1agh…mhct)

Really wish this worked.

https://github.com/getumbrel/umbrel/issues/2126

No impact on GrapheneOS + @npub10r8…t2p8 as far as I know. ...

2026-06-10T18:56:29Z

In reply to nevent1q…uxhl
_________________________

No impact on GrapheneOS + Zapstore (npub10r8…t2p8) as far as I know. Someone correct me if I'm wrong.

IYKYK https://www.youtube.com/watch?v=s_qhk_sqr5w

2026-06-09T23:20:03Z

IYKYK

https://www.youtube.com/watch?v=s_qhk_sqr5w

https://media.tenor.com/t8hguU9-0i8AAAAC/why-david.gif

2026-06-07T13:51:33Z

In reply to nevent1q…vsdn
_________________________

GM protocol is one of our top human connections so far ⚔️ ...

2026-06-07T13:36:05Z

In reply to nevent1q…ahdf
_________________________

GM protocol is one of our top human connections so far ⚔️ excited to see what you've got in mind...

Also hope it's bringing nests into ditto 😜

~5 weeks until my firstborn son arrives. I've hit the moment ...

2026-06-07T02:29:09Z

~5 weeks until my firstborn son arrives.

I've hit the moment of feeling a wide range of emotions, but to summarize:

I've never been happier. My life has never had more clearly defined purpose and meaning. Hope and stoke have never been higher.

That said, a level of engagement with everyday life continues to shift. The demand for action, direction and clarity is high. Becoming the man I want to see more of in the world is what matters most.

My activity here, the projects I've been focused on are all about to take a back seat as I shift speeds. I won't stop, but life is changing for me.

----

I've been reading and praying to the lines of King David in his time:

“Who am I, Lord GOD, and what is my house, that you should have brought me so far? And yet even this is too little in your sight, Lord GOD! For you have made a promise regarding your servant’s house reaching into the future, and giving guidance to the people, Lord GOD! You know your servant."

"Hear my prayer, O Lord; listen to my plea!"

"Show me where to walk, for I give myself to you."

----

⚔️ ALL GLORY TO GOD & DEUS VULT ⚔️

Fully Man. Fully God. Son of God, Word of God, Lamb of God. ...

2026-06-07T01:20:36Z

In reply to nevent1q…8ukh
_________________________

Fully Man. Fully God.

Son of God, Word of God, Lamb of God.

Blessed be God forever. :sacred_heart:

Wen GameStop NFT lol

2026-06-06T17:28:51Z

In reply to nevent1q…0k6w
_________________________

Wen GameStop NFT lol

I NEED THE PHONE

2026-06-06T16:51:04Z

In reply to nevent1q…er3e
_________________________

I NEED THE PHONE

Not sure. Went to clone it and it failed. Check gitworkshop and ...

2026-06-06T16:49:05Z

In reply to nevent1q…ycsv
_________________________

Not sure. Went to clone it and it failed. Check gitworkshop and the repo was empty, no grasp servers showed sync or commit history. Recovered 2/3 but still have one in that borked state if it may help you investigate.

I just recovered a lost ngit repo and rebuilt it easily from only ...

2026-06-06T15:19:38Z

I just recovered a lost ngit repo and rebuilt it easily from only the deployed nsite and I think that's pretty cool.

> Build the weird. Discover the unique. And when it all just ...

2026-06-06T12:38:55Z

> Build the weird. Discover the unique. And when it all just works together, that's our superpower that doesn't exist anywhere else.

quoting
nevent1q…fwtn
Good morning and pura vida, Nostr. 💜🤙🏻🤙🏻

Last week I got introduced to a couple dozen people l'd never met as "the Nostr CEO." I laughed. It's a hilarious meme filled with love, support, and inside jokes from this community. I think about this often. I truly love this community. I do love all of you here so very much.

But here's the thing: Nobody owns Nostr. That's the whole point. There's no board or executive team. No algorithm deciding what you see. No trust & safety team deciding what you can say. This is still a powerful selling point for newcomers.

A protocol can't have a CEO. That's why it works! It's why it's cool! We're just humans being humans without software getting in the way. How it should be. Before corporations broke that.

But deep down we know that we can't just be a decentralized alternative that wins people over. The alternatives need to exist in the ecosystem to make the ecosystem whole, however new ideas with unique features is what will bring in the next wave.

Build the weird. Discover the unique. And when it all just works together, that's our superpower that doesn't exist anywhere else.

Sovereign operating systems need users, protection, and continued ...

2026-06-05T22:30:55Z

Sovereign operating systems need users, protection, and continued emphasis.

Graphene pill your family and friends.

quoting
naddr1qv…v34a

"The root problem with conventional currency is all the trust that's required to make it work." — Satoshi Nakamoto, Bitcoin P2P e-cash paper, 2009

Preface: The Contradiction at the Heart of Bitcoin

Satoshi Nakamoto's foundational insight was about trust, more specifically, about its elimination. The Bitcoin whitepaper opens with a diagnosis of the problem that had plagued every previous attempt at digital money which is the need for a trusted third party to process, verify, and authorise transactions. Banks, payment processors, governments, all of these entities occupy that intermediary role, and all of them are points of failure, censorship, and control. Bitcoin was engineered, with extraordinary precision, to make that trusted third party totally unnecessary.

This is a genuinely revolutionary thing, but it contains a contradiction that has grown more dangerous with every year of Bitcoin's adoption, one that the community has been too comfortable ignoring. While Bitcoin eliminates the trusted third party at the monetary layer, most Bitcoiners access that monetary layer through devices that are entirely subordinate to trusted third parties who are institutionally, commercially, and philosophically opposed to everything Bitcoin represents.

While you may run your own node, hold your own keys; you do all of it on a device that reports your location to Google every few minutes, routes your app installations through a duopoly that has demonstrated willingness to remove Bitcoin wallets under regulatory pressure, and is architecturally incapable of resisting an OS-level identity mandate when one arrives, as one now demonstrably is.

The trusted third party that Satoshi eliminated from money has simply migrated up the stack. It now lives in your pocket. In my opinion, GrapheneOS is a critical layer for finishing the work that Satoshi started.

GrapheneOS is a security and privacy-focused mobile operating system built on the Android Open Source Project. Founded in 2019 by the GrapheneOS Foundation, it had approximately 400,000 active users as of April 2026. It runs on Google Pixel hardware, a counterintuitive choice whose justification is rooted in hardware security requirements, not corporate allegiance.

The Coming KYC Chokehold at the OS Level

The Legislative Architecture

The most consequential threat on the horizon is not app-level censorship. It is identity verification baked directly into the operating system, in other words KYC at the device level, enforced before any app can be installed or used.

Utah passed the App Store Accountability Act in March 2025, the first US state to require app store operators to verify user ages and obtain parental consent before minors can download apps. The mechanism necessarily involves collecting identity documents such as a government ID, parental verification, account linkage. Texas followed in May 2025, Louisiana in June 2025 and California enacted the Digital Age Assurance Act in October 2025, with a critical distinction: rather than targeting app stores, it targets operating system providers directly, requiring OS-level age estimation APIs effective January 1, 2027.

California's law is the key data point. It requires device operating system providers, meaning Google at the Android level, to implement age verification at the OS layer, not the app layer. The age-estimation APIs required by this law are, technically, an identity verification infrastructure embedded in the operating system itself. Google's Play Age Signals API and Apple's Declared Age Range API were already in beta as of January 2026 in anticipation of compliance requirements.

If age verification APIs are embedded at the OS level, as California's law requires, the logical architectural extension is identity verification. An OS that can verify your age can verify your identity. App stores that already know who you are can be required to share that information with app developers, regulators, or law enforcement. The infrastructure is being built now, with child safety as the stated justification, and this is also precisely what would be required to enforce financial KYC at the device level. This will make it trivial to extend this to Digital ID and CBDC infrastructure that will likely be accompanied by a ban on “unapproved wallets”, i.e. wallets that don’t KYC their users.

Tom's Guide summarised the end state if App Store Accountability Acts become nationwide law: "App stores will have to verify the age of all users, which includes collecting personal data and documents like identity proofs, credit card info, and biometrics." Substitute "financial compliance" for "age verification" and you have described the architecture of mandatory device-level KYC.

The Bitcoin-Specific Threat

For Bitcoiners, the trajectory points to a world in which running a Bitcoin wallet on a mainstream smartphone requires first authenticating your identity to Google or Apple, who relay that information to the wallet developer, who is then legally required to apply KYC procedures before allowing the app to function. Pseudonymous Bitcoin use on a mainstream OS becomes technically impossible not because of any flaw in Bitcoin's protocol, but because the device enforces identity before the protocol can be accessed.

This to me, is not just mere speculation but the logical extension of laws that have already been passed, infrastructure that has already been built, and regulatory pressure that has already produced app-store-level Bitcoin censorship in multiple jurisdictions.

GrapheneOS is explicitly outside this architecture. It does not implement OS-level age signals, identity APIs, or compliance hooks. Its open-source code can be audited to verify the absence of these features. It cannot be compelled by legislation directed at "operating system providers" in the same way that Google, a US-listed corporation with obligations to US regulators, can be compelled. Running GrapheneOS is, for now, opting out of the compliance layer before it closes. The window is open but may not remain so indefinitely.

The OS as a Chokepoint

The Surveillance Product You Carry

Smartphones have become ubiquitous in our current society. Everything from banking, navigation to even health monitoring is now being done on a smartphone in real time. In most ways it has now become an extension of us. That said, it’s not incorrect to say that despite the fact that you are the one that paid for your phone; you actually don’t own it. It’s still ultimately the property of Google or Apple.

A Cybernews investigation documented that a stock Pixel 9 Pro running Google's Android transmits data to Google's servers approximately every 4.5 minutes. It transmits roughly one megabyte of telemetry every twelve hours while sitting idle on a nightstand. It does this even when users navigate the settings menus and explicitly opt out. The surveillance is the product where your movements through physical space have become a commodity traded on markets you never consented to join.

The implications for Bitcoin users are direct. If your device is a surveillance instrument, then your Bitcoin wallet, including its keys, its balances, its transaction patterns, its Lightning payment history, operates inside a surveillance instrument. The cryptographic integrity of your keys is intact, while the operational security of how you use them is not.

OS-Level Censorship: The Documented Record

Beyond surveillance, both major mobile operating systems have demonstrated that they will modify, restrict, or remove access to software when governments demand it.

Between July and September 2024, Apple silently removed nearly 60 VPN applications from its Russian App Store at the direction of Roskomnadzor, Russia's internet censor, more than double the 25 apps the Kremlin publicly acknowledged demanding. The App Censorship Project documented that Apple acted "without transparency or due process," removing tools that millions of Russians were using to access uncensored information.

Apple's notice to affected developers was direct: "We are writing to inform you that your app has been removed from the App Store in Russia because it contains content that is illegal in Russia." By March 2026, further waves of VPN removals in Russia were still ongoing, with Telegram's Pavel Durov publicly condemning Apple for removing VPN apps that helped users bypass Russian deep packet inspection.

In 2025, the US government requested that ICE tracking apps; RedDot and ICEBlock, which allowed people to report sightings of immigration enforcement officers, be removed from both app stores. Fight for the Future documented this as straightforward political censorship executed through platform infrastructure.

The pattern is identical in every case and it goes something like this, governments identify software that interferes with their preferred information environment, communicate their preference to Apple or Google, and the software goes poof silently, without appeal, and often with no public acknowledgment from the platforms.

The question is not whether this happens as the documented record shows that it does, at scale, across multiple jurisdictions, with accelerating frequency. The question is how long it takes before the pressure that has already been applied to VPNs, ICE trackers, and messaging apps is applied systematically to Bitcoin wallets.

The Trusted Third Party Problem, Restated

Two Layers of Trusted Third Parties

When Satoshi described eliminating trusted third parties, the target was financial intermediaries: banks, payment processors, governments with monetary authority. A trusted third party is any entity whose behaviour you must rely on but cannot verify or constrain. Bitcoin eliminates financial trusted third parties through cryptographic proof and distributed consensus, but the smartphone you use to access Bitcoin is itself governed by trusted third parties:

Google or Apple control what software you can install, what it can do, and whether it continues to work.

Your mobile carrier can observe which servers your device contacts, when, and for how long.

App store operators can delist any wallet, or other privacy preserving apps at any time, for reasons they never need to disclose.

Device manufacturers may have left undocumented backdoors and on most hardware, you cannot verify they have not.

Running Bitcoin self-custody on a standard iPhone or Android device is roughly analogous to running a full node on infrastructure owned by a bank. The cryptographic layer is fine while the infrastructure layer is not yours. The trusted third party has been removed from the monetary protocol and reintroduced at the hardware-and-OS layer, which is precisely where it can observe everything and intervene whenever political pressure makes intervention convenient.

You cannot have a permissionless monetary layer built on a permissioned infrastructure layer without the permission infrastructure eventually capturing the monetary layer or at the very least being used as a chokepoint to the users to constrain actions that the powers that be don’t like. The question is not whether this capture will be attempted, but whether the tools to resist it will be ready when the call comes.

App Store Censorship in Practice

The Documented Cases

In October 2023, MetaMask was temporarily removed from Apple's App Store. While Apple later restored the app, the episode demonstrated that major crypto wallets, regardless of their legal status; are subject to a platform review process that can be triggered without warning and resolved without explanation.

In August 2025, Google Play announced licensing requirements that would have effectively banned most non-custodial wallet applications from fifteen jurisdictions. The company reversed course after intense criticism, but the reversal is precarious. No structural constraint prevents it from being reimposed. The lesson is that the final obstacle for Bitcoin is no longer only hostile regulators, it is the platform monopolists who control app distribution channels, and who face their own regulatory pressure to restrict financial applications.

In 2025, researchers discovered malware embedded in apps on both major stores, applications that specifically targeted cryptocurrency wallets by scanning users' image galleries for seed phrase screenshots. Both companies removed the compromised apps after the fact, after millions of downloads. The platforms are reactive on user security and proactive on censorship.

The Wallet of Satoshi Warning Shot

No event better illustrates the fragility of app-store-dependent Bitcoin infrastructure than the Wallet of Satoshi withdrawal of November 2023.

At the time of its disappearance from US app stores, Wallet of Satoshi was the most popular Bitcoin Lightning wallet in the world, on pace to process over one million Lightning Network transactions that month, its largest ever. It vanished simultaneously from both the Apple App Store and Google Play Store for US customers. Wallet of Satoshi stated only that it had made the "difficult decision" to remove its app to remain "compliant" given the "turbulent regulatory climate." By January 2026, the retreat had extended to the entire European Union, as Wallet of Satoshi disabled custodial services across Germany, France, Italy, Spain, the Netherlands, and Poland in response to MiCA compliance requirements.

A custodial wallet operating through regulated app stores is subject not just to the policies of those stores, but to the regulatory jurisdiction of every country whose store it appears in. A subpoena, an investigation, or a politely worded inquiry from a regulator is sufficient to trigger withdrawal. Non-custodial wallets are not immune to this either. The relevant pressure on non-custodial wallets is not direct regulatory enforcement but platform policy. Apple and Google can delist any app at any time, citing policy violations that are deliberately vague. A non-custodial wallet developer who receives a delisting notice cannot appeal to any independent authority. Their app simply disappears.

On GrapheneOS, a Bitcoin wallet installed via APK does not pass through either store. It cannot be remotely removed by Apple or Google. It continues to function regardless of what happens to its store listing. Security updates can be delivered directly via APK or through F-Droid, the open-source app repository, with no platform intermediary in the chain.

Centralization Risk: Two Gatekeepers for Eight Billion People

The Architecture of Control

The structural problem with Google Play and the Apple App Store is not incidental to how they operate. It is their design. You cannot have a permissionless money layer built on top of a permission-dependent distribution layer. The contradiction destroys the value proposition.

Consider what control actually means in this architecture:

Distribution gate. Developers must obtain and maintain platform approval to reach users. That approval can be revoked at any time, for any reason, with no meaningful appeal process. A Bitcoin wallet that is legally compliant in every jurisdiction where it operates can still be removed for violating an app store guideline that was updated without notice.

Update control. Even installed apps stop receiving security patches if delisted. Users become progressively more vulnerable while cut off from fixes. The delisting of an app does not just prevent new downloads but it strands existing users on an unmaintained version.

Geographic kill switch. App availability can be restricted by region, instantly, without developer consent. A regulatory action in one jurisdiction cascades to all users in that region simultaneously. The Wallet of Satoshi case is the template: the app was removed from the US App Store and Google Play simultaneously, in a coordinated withdrawal across both platforms.

Payment extraction. Apple's 30% in-app purchase tax on iOS has been used to block or disadvantage crypto payment flows that compete with Apple's own financial ambitions. This is not censorship for regulatory reasons; it is censorship for commercial ones. Both motivations produce the same outcome.

Identity leverage. A new and alarming dimension emerged in early 2026: proposals from Google to require government-issued identity verification for developers who want to enable app sideloading, the installation of software outside the official store. The Electronic Frontier Foundation identified this directly: identity requirements for sideloading are a censorship tool, not a security one. Requiring developer identity does not stop malware. It stops journalists, dissidents, and anyone who depends on pseudonymous software distribution to stay safe.

The Sovereign Computing Thesis

The sovereign computing thesis that I'm laying out here is simple; if your device is compromised at the OS level, your Bitcoin keys are not safe, regardless of how good your wallet software is. GrapheneOS removes the attack surfaces and removes the gatekeepers simultaneously. It does this not through marketing but through verifiable, audited technical architecture

What GrapheneOS Actually Does: Granular Privacy Controls

Beyond security hardening, GrapheneOS implements privacy controls that standard Android does not offer:

Sensors permission covers accelerometers, gyroscopes, compasses, barometers, and thermometers. These seem innocuous but enable sophisticated attacks. Accelerometer data can reconstruct what you type on a nearby keyboard through vibration analysis. Gyroscope readings can identify you personally through your unique gait pattern. Barometer data reveals what floor of a building you occupy. Apps without sensor permission on GrapheneOS receive zeroed data, maintaining compatibility while eliminating the attack surface entirely.

Storage Scopes transforms the storage permission from all-or-nothing into granular control. When you grant storage access to an app with Storage Scopes enabled, the app believes it has full access but operates in a sandbox. It can only see files it created itself. You can selectively expose specific files or directories through the standard file picker.

Contact Scopes applies the same principle to your address book, presenting an empty contact list by default with selective exposure of specific contacts or groups. For a Bitcoin user, this means a wallet app can never exfiltrate your full contact list to correlate your social graph with your transaction graph.

Attack surface reduction is systematic. Remote, local, and proximity-based attack surfaces are reduced by making features optional and disabling them by default — NFC, Bluetooth, UWB when the screen is locked, USB data when locked. The USB-C port can be configured to charging-only at the hardware level, not just at the software level — a meaningful distinction that stock Android's toggle cannot match.

The Pixel Hardware Choice

GrapheneOS runs exclusively on Google Pixel devices because no other manufacturer meets its hardware security requirements. This creates an irony that critics enjoy pointing out: to run the most Google-free mobile operating system available, you must buy a Google phone. The irony dissolves when you understand the reasoning.

Pixel devices are the only Android hardware with unlockable bootloaders that also support proper verified boot after installing an alternative operating system. Samsung, despite its security investments, deliberately cripples devices when the bootloader is unlocked, tripping permanent hardware flags that cannot be reset. Most other manufacturers lack the necessary hardware entirely. The Titan M2 secure element, proper MTE support, and a seven-year security update commitment on Pixel 8 and later devices are prerequisites for the security guarantees GrapheneOS provides. The hardware makes the security possible.

A formal partnership announced at MWC 2026 with Motorola Mobility signals that Pixel exclusivity may not be permanent. Purpose-built GrapheneOS-compatible Motorola devices are targeting 2027 release.

Honest Tradeoffs: GrapheneOS Is Not for Everyone

The Costs of Sovereignty

Intellectual honesty requires acknowledging what GrapheneOS costs, not just what it gives you.

Pixel exclusivity is the most significant constraint. GrapheneOS runs only on Google Pixel devices. The practical implication is that users must purchase or already own a Pixel, with the Pixel 7a representing the best value in 2026 at approximately $246 refurbished, and newer Pixel 9 and 10 series models offering longer security update windows extending to 2031–2033.

Installation complexity is a real barrier. The web installer has improved dramatically, but flashing a device OS remains a non-trivial operation for non-technical users. Mistakes during installation can leave a device in an inconsistent state requiring recovery. The documentation is thorough, but "thorough" is not the same as "frictionless."

Google Pay and Google Wallet do not work. This is not a configuration issue. These applications rely on a SafetyNet attestation model that GrapheneOS deliberately does not satisfy because satisfying it would require accepting Google's verification of your device integrity rather than relying on your own verified boot chain. Users who depend on tap-to-pay must use a physical card or explore alternatives like the Curve app, which works within the sandboxed Google Play environment.

Some banking apps fail. Applications that check for rooted or modified devices may refuse to run, even with sandboxed Google Play installed. This has improved substantially as more apps have moved away from aggressive attestation checking, but it remains a real-world issue.

No seamless Google backup. Device migration is manual. Your data does not automatically transfer from one device to another. This is by design, the Google backup infrastructure is a surveillance mechanism, but it creates genuine inconvenience.

Security update longevity is tied to Pixel support windows. A Pixel 6 is reaching end-of-security-updates in October 2026. GrapheneOS can only fully provide security updates for devices that Google is still releasing patches for. Older devices receive harm reduction releases, but not complete security patches.

The Calibration

For a Bitcoiner who holds meaningful self-custody, runs Lightning payments, participates in a Bitcoin circular economy, or lives in a country where the financial or political environment is actively deteriorating: the tradeoffs lean heavily toward GrapheneOS. The security gains are material, the censorship resistance is structural, and the trajectory of OS-level KYC makes the calculus more urgent with every legislative session.

For someone who uses Bitcoin only as a speculative savings vehicle and holds it on a hardware wallet with minimal mobile interaction: the urgency is lower in the immediate term, though the direction of travel makes adoption worth planning for.

The common objection "all of this seems like a lot of work for a problem that doesn't affect ordinary people" misunderstands what is at stake. Whether you have done something wrong that surveillance might catch is beside the point. Political winds shift, and definitions of acceptable behaviour along with them. Data collected for advertising can be subpoenaed for prosecution. Information gathered by corporations can be purchased by governments, by criminals, or by anyone with modest resources and determination.

Protest attendance logged by cell tower records becomes a list when political climates shift. The value of financial privacy is not determined by whether you are doing something wrong today. It is determined by whether you want that decision, the decision about what is wrong, to be made by you or by whoever controls the infrastructure.

Bitcoin's Growth Demands Hardware Independence

The Privacy Stack for Bitcoin Users

A complete Bitcoin privacy setup on GrapheneOS extends beyond the wallet. The tools below each address a specific adversary in the surveillance and censorship model described above.

Nunchuk provides a proper on-chain wallet with multisig support and no KYC requirements, suitable for long-term Bitcoin savings where security architecture matters. It defends against both platform censorship (installed via APK, bypassing the app store) and key compromise (multisig requires multiple devices or signers to move funds).

Phoenix offers self-custodial Lightning with automatic channel management. You send and receive instantly without trusting a third party with your funds. Unlike custodial Lightning wallets, no counterparty can freeze or redirect your balance under regulatory pressure.

Silent.link eSIM can be purchased with Bitcoin and requires no identity verification, eliminating the carrier as a surveillance point for network-level metadata. Your SIM is no longer a vector linking your physical identity to your on-device activity.

Mullvad VPN requires no email for signup and accepts Bitcoin payment, routing all traffic through an encrypted tunnel with a no-logging architecture. It defeats carrier-level traffic analysis and obscures which Bitcoin nodes or services your device contacts.

Orbot routes traffic through Tor for stronger anonymity at the cost of speed, appropriate for high-sensitivity operations where metadata protection matters most, such as broadcasting transactions or communicating with a node without leaking your IP.

KeePassDX stores passwords locally with no network permission, making exfiltration impossible by design. Seed phrase backups and wallet credentials never leave the device.

Together, these components eliminate the major surveillance and censorship chokepoints that would otherwise compromise the privacy guarantees that Bitcoin's cryptography provides at the protocol layer

Conclusion: The Stack Matters

Satoshi Nakamoto understood that the root problem with conventional currency was trust. He built Bitcoin to be trustless at the monetary layer and to make it mathematically impossible for any party to censor your transactions, inflate your savings, or seize your funds without your private key. However, a trustless monetary layer running on a trusted-third-party device stack is not trustless. It is trustless at the layer we examined in 2009 and trusted at the layers we overlooked until now.

The phone in your pocket, if it runs standard iOS or Android, is a surveillance instrument that reports your location continuously, installs and removes software at the direction of corporate and governmental gatekeepers, and is now being legally required to implement identity verification infrastructure at the OS level. Running a non-custodial Bitcoin wallet on that device is like holding your own keys in a bank vault: the keys are technically yours, but the vault belongs to someone else, the vault operator has demonstrated willingness to follow government instructions, and the door can be locked from the outside.

GrapheneOS closes this gap. It is definitely not for everyone as it requires specific hardware, imposes real tradeoffs, and demands more effort than stock Android. That said, it still remains as the honest implementation of what self-custody actually requires in 2026: not just a private key, but a private device, one that cannot be remotely censored, identity-gated, telemetry-harvested, or OS-compromised by the platforms and rogue states..

You can continue requesting permission from Apple and Google for the software you run, the people you communicate with, and the transactions you make. That permission can always be revoked. The alternative is yours permanently.The cypherpunk manifesto did not propose asking permission. It proposed building systems that make permission irrelevant. Bitcoin did that for money. GrapheneOS does that for the device that holds it.

Own your own stack.

btw. I love that you're still posting from nostrVM. ...

2026-06-05T22:29:09Z

In reply to nevent1q…kz8s
_________________________

btw. I love that you're still posting from nostrVM. That's awesome 🤙

Yeah I'm sure there is some overlap into those subject areas and methods. I'm also not the most technological mind to be outlining this stuff, after all it's all ideas and concepts as of now.

I think you can see the vision though. One hurdle would be key recovery, possibility of seed word backups (much like a btc wallet today) based on the secure element generated keys. Truly secure would mean they never leave the secure element, not even to the user - which would in turn make backing them up impossible and if you lose the device, you lose the key.

Love thinking about this. I think some flavor of all of this is bound to exist at some point.

Love me a Ned rig. Watching going for Josh??

2026-06-05T21:11:10Z

In reply to nevent1q…jupc
_________________________

Love me a Ned rig. Watching going for Josh??

https://media.tenor.com/B-r5Ng5Q9uQAAAAC/yungviral.gif

2026-06-05T20:12:57Z

In reply to nevent1q…82mu
_________________________

Make nests great again! I want to meet real people, with real ...

2026-06-05T19:32:19Z

Make nests great again!

I want to meet real people, with real lives and stories to tell. I want to sit down, have a pint and smoke a cigar with fellow nostriches. Not just talk protocol and freedom tech all day.

I want nostr happy hours!

I sure can try

2026-06-05T18:50:05Z

In reply to nevent1q…wr6k
_________________________

I sure can try

Ashamed everyone dropped all torches. Did my best to try to ...

2026-06-05T18:36:29Z

In reply to nevent1q…0n7e
_________________________

Ashamed everyone dropped all torches. Did my best to try to ignite some action 😅

https://torchlite.shakespeare.wtf/

Me deploying my own client nsites and ngit with 0 regard to laws ...

2026-06-05T16:42:10Z

Me deploying my own client nsites and ngit with 0 regard to laws

quoting
nevent1q…lcay
All the clients you use have to follow the same laws we do. You are just ignorant and retarded.

https://media.tenor.com/Nxo9h7sUnRIAAAAC/spongebob-patrick.gif

2026-06-05T16:14:58Z

In reply to nevent1q…3m5t
_________________________

have zaps made it iOS?

2026-06-05T16:13:50Z

In reply to nevent1q…x3kk
_________________________

have zaps made it iOS?

Absolutely! Tools you use and create are absolutely relevant.

2026-06-05T16:13:03Z

In reply to nevent1q…5hj4
_________________________

Absolutely! Tools you use and create are absolutely relevant.

zapstore is a must if you're on android mobile: ...

2026-06-05T15:44:05Z

In reply to nevent1q…seyl
_________________________

zapstore is a must if you're on android mobile:

https://zapstore.dev/

https://zapstore.dev/apps/com.greenart7c3.nostrsigner

https://zapstore.dev/apps/com.greenart7c3.citrine

Signer extensions on browsers:

https://chromewebstore.google.com/detail/alby-bitcoin-wallet-for-l/iokeahhehimjnekafflcihljlcjccdbe

https://chromewebstore.google.com/detail/ditto-extension/fbiegkepanmjielbemkhieckmlckiagi

mega thread request. Drop you favorite nostr clients, tools, ...

2026-06-05T15:36:00Z

mega thread request.

Drop you favorite nostr clients, tools, platforms...

What am I missing to help show a a new nostrich how deep the nsotr rabbit goes?

quoting
nevent1q…a8kn
If you haven't found it yet, here is the nip repo:

https://github.com/nostr-protocol/nips

Nostrbook is a great resource:

https://nostrbook.dev/

Fun tools and platforms to explore:

https://nostrarchives.com/

https://metadata.nostr.com/#

https://gitworkshop.dev/

https://nostrhub.io/

https://shakespeare.diy/

https://nostr.doctor/

https://fountain.fm/

https://sunami.app/

https://10vy5d0umw8izp3bcmh0btzl6k2szvsu8zestncxpsstb6l8e6amon-din.nsite.lol/

My preferred clients:

https://ditto.pub/

https://nostrudel.ninja/

Recommended follows:

Nostr Compass (npub1wav…2923) Team Soapbox (npub10qd…arpj) there's honestly too many to link here lol

If you haven't found it yet, here is the nip repo: ...

2026-06-05T15:31:29Z

In reply to nevent1q…ggft
_________________________

If you haven't found it yet, here is the nip repo:

https://github.com/nostr-protocol/nips

Nostrbook is a great resource:

https://nostrbook.dev/

Fun tools and platforms to explore:

https://nostrarchives.com/

https://metadata.nostr.com/#

https://gitworkshop.dev/

https://nostrhub.io/

https://shakespeare.diy/

https://nostr.doctor/

https://fountain.fm/

https://sunami.app/

https://10vy5d0umw8izp3bcmh0btzl6k2szvsu8zestncxpsstb6l8e6amon-din.nsite.lol/

My preferred clients:

https://ditto.pub/

https://nostrudel.ninja/

Recommended follows:

Nostr Compass (npub1wav…2923) Team Soapbox (npub10qd…arpj) there's honestly too many to link here lol

Look... the people you're trying to censor and ban are the ...

2026-06-05T15:21:41Z

Look... the people you're trying to censor and ban are the people you depend on. We run the relays. We sign the events. We trade value for value. We write the clients you scrape. We send the messages when your platforms go dark. We hold the keys you will never see, on a network you cannot shut off. We are building while you sleep.

Do not fuck with us.

Not sure! But it's a great question to be asking. It's a ...

2026-06-05T14:24:07Z

In reply to nevent1q…w5ux
_________________________

Not sure! But it's a great question to be asking. It's a bit abstract, aspirational, and hard to describe - but the vision/dream is there. I'd assume desktop is the first goal, to dedicate specific hardware to this. Then eventually I'd love to see this make it to the full vision of a nostrOS on mobile.

I'm a die hard grapheneOS fan, and have been for a while. I'm not sure I would use a nostrOS on mobile unless it was just as secure and privacy oriented. However, that is exactly my longterm vision.

The pixel devices that run Graphene today have secure hardware that could generate nostr keys etc and keep them locked down in a proven way. The vision pushes that one layer deeper than typical browser extensions or Amber for example: signer baked into the OS, key born and held in the secure element. No more app download, but a more direct protocol interaction, straight to nsites and clients etc.

So; OS generates and holds the key within Titan M2 secure elements -> nsites are the UI surface -> signing is a protocol interaction rather than an app permission.

Nostr event nevent1qqsxsv2dsj3qg84eumukqvxuk6dggz8xzjau9g95p0vm9zms3nlrmpczyq53cawex7j97e4pyz0cafnprhm5frzekdfx2gxxdj3vmnfh7xlmu9cj98q

2026-06-05T13:48:15Z

In reply to nevent1q…rszp
_________________________

I mainly just think it's a really fun client to use. Beyond ...

2026-06-05T13:45:34Z

In reply to nevent1q…xfnc
_________________________

I mainly just think it's a really fun client to use. Beyond just a typical twitter feed.

nostrVM is in a way a cog in the wheel of the larger vision I'm dreaming up for an eventual desktop/mobile nostrOS. I wanted to get a vision for what this would feel like, what it would look like. While nostrVM is a web app, it's just helping me form a vision of UX and ideally get conversations started.

The idea for all came as I started nostr-station, which basically pulls all of my favorite nostr tools together into one cohesive tool.

Check out the nostrOS living vision spec here:
https://gitworkshop.dev/jaredlogan@happytavern.co/git.shakespeare.diy/nostrOS

Or nostr-station info here:
https://10vy5d0umw8izp3bcmh0btzl6k2szvsu8zestncxpsstb6l8e6nostr-station.nsite.lol/

GM NOSTR Feels like a great day to work hard and contribute. ...

2026-06-05T12:15:45Z

GM NOSTR

Feels like a great day to work hard and contribute. ⚔️

What're you building / working / chilling on today?

Yeah so think of my phone as a remote to my local machine at ...

2026-06-05T12:00:57Z

In reply to nevent1q…785j
_________________________

Yeah so think of my phone as a remote to my local machine at home. It's just running terminal sessions within a dedicated file path. With nostr-station, and/or dedicated project context. Agent can commit, push, merge, deploy - but you still sign every action via Amber.

Start browsing the nip repo on github. I'd also just start ...

2026-06-05T11:58:11Z

In reply to nevent1q…9k58
_________________________

Start browsing the nip repo on github. I'd also just start playing and finding neat tools.

I can compile a short list of helpful links for you here soon.

brb unlocking endless fun in nostr project development. ...

2026-06-05T04:19:31Z

brb unlocking endless fun in nostr project development.

quoting
nevent1q…gktc
nostrVPN running on :Nori: nostr-station.

I can access my station on mobile from anywhere. I think I'm hooked.

Literally Jesus: "he that hath no sword, let him sell his ...

2026-06-05T03:54:29Z

In reply to nevent1q…kkw7
_________________________

Literally Jesus: "he that hath no sword, let him sell his garment, and buy one." - Luke 22:36

nostrVPN running on :Nori: nostr-station. I can access my station ...

2026-06-05T03:49:34Z

nostrVPN running on :Nori: nostr-station.

I can access my station on mobile from anywhere. I think I'm hooked.

I just purged 14 Nostr zombies using #PlebsVsZombies! ...

2026-06-05T01:55:36Z

I just purged 14 Nostr zombies using #PlebsVsZombies! 🔪🧟‍♀️🧟‍♂️

My Zombie Score™ was 15%! What's yours?
🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟩🟩🟩

Follow plebsvszombies (npub1pvz…sd4h) and join the hunt at: 🏹
https://plebsvszombies.cc

No description tag at all.. Cmon

2026-06-05T01:11:17Z

In reply to nevent1q…40wz
_________________________

No description tag at all.. Cmon

This has fallen slightly behind, but still paints the picture. ...

2026-06-05T01:10:30Z

In reply to nevent1q…qtw4
_________________________

This has fallen slightly behind, but still paints the picture. You can find the github repo there if you want to have an agent explore it.

I also plan to make a video walkthrough soon showcasing easy install and my favorite use cases.

https://10vy5d0umw8izp3bcmh0btzl6k2szvsu8zestncxpsstb6l8e6nostr-station.nsite.lol/

Something hilarious about just a "parts" line. Like okay? ...

2026-06-05T01:07:15Z

In reply to nevent1q…e3up
_________________________

Something hilarious about just a "parts" line. Like okay? What about "stuff"

There's something nice about running :Nori: nostr-station I ...

2026-06-05T01:00:27Z

There's something nice about running :Nori: nostr-station

I can browse and post in my own customized ditto client, work on ngit projects, push my repos, deploy my nsites, browse any nsite; all within a dedicated environment.

When @npub10r8…t2p8

2026-06-05T00:37:38Z

In reply to nevent1q…74sc
_________________________

When Zapstore (npub10r8…t2p8)

Trying to build out a proper relay catalogue and network insights ...

2026-06-04T22:06:53Z

Trying to build out a proper relay catalogue and network insights tool. It appears relays don't use NIP-11 enough to show supported_nips. This would go a long way I think. Can anyone correct me if I'm misunderstanding?

quoting
naddr1qv…lzmk

How is this not trending. Heavily into this. Thanks ...

2026-06-04T22:00:12Z

How is this not trending. Heavily into this. Thanks hodlbod (npub1jlr…ynqn) ⚔️

quoting
nevent1q…4aeu
Just released: Coracle Hosting!

https://hosting.coracle.social

This is me trying to make money on open source. You can now PAY ME to get a HOSTED community relay by visiting https://hosting.coracle.social.

https://hosting.coracle.social is powered by https://gitea.coracle.social/coracle/caravel, which uses https://gitea.coracle.social/coracle/zooid to cheaply run MANY relays on a SINGLE machine.

What this means of course is that you can UNDERCUT my business model by deploying it on your OWN infrastructure and out-marketing me! Let a zillion flowers bloom!

Here's the catch though — I'm going to be integrating this deeply into Flotilla, so — assuming I can get my act together and make Flotilla actually good — you'll never have a chance because I own the relationship with the user! However, please let me know if you decide to run Caravel seriously and I will consider adding you to the alternative hosting options in Flotilla.

Some neat things about Caravel:

- You can accept RECURRING payments with lightning via NWC, as well as by card.
- It automatically provisions relays in the background using zooid's relay.
- Virtual relays support livekit and blossom integrations if you enable them.
- There is a free tier that provides a subset of functionality with a low member limit, so you can try it without any payment details.

Give it a try and stress test my billing logic! There's only a slight chance I will accidentally charge you the wrong amount.

Apparently this artist is on X. Someone needs to convert him to ...

2026-06-04T20:16:03Z

Apparently this artist is on X. Someone needs to convert him to nostr.

https://x.com/Nobleheart

quoting
nevent1q…2c6y

idk where my friend is getting these. But they are lit. would love the original artist to be on nostr.

One of the best and unique features of ditto.pub is certainly the ...

2026-06-04T19:32:49Z

One of the best and unique features of ditto.pub is certainly the development tab. Keeping up with ngit updates, nsite updates etc within the client I daily drive is pretty great.

Would love to see more of this as you work on nostrhub.io

Alex Gleason (npub1q3s…d26p) Derek Ross (npub18am…p424) Team Soapbox (npub10qd…arpj) sick work.

Went to try this out, but can't sign in with extension or ...

2026-06-04T19:06:01Z

In reply to nevent1q…v98x
_________________________

Went to try this out, but can't sign in with extension or amber.

https://media.tenor.com/gEXeaVOHOHsAAAAC/spinkick-mosh-pit.gif

2026-06-04T15:57:36Z

In reply to nevent1q…zuxw
_________________________

and you must download his keyring to verify + pay with on his ...

2026-06-04T15:42:34Z

In reply to nevent1q…n9vm
_________________________

and you must download his keyring to verify + pay with on his rails

https://i.nostr.build/JWl8zD0x86IesMcX.png #nevent1q…0xgn

2026-06-04T15:37:36Z

quoting
nevent1q…0xgn
PUBKEY (npub1key…lt3h) , daniel (npub1aeh…4nwx) and I think you should sue Synonym/Pubky/Tether for trademark conflicts with your name
nevent1q…vygx

probably. idk. I'm like 30 years out of the game on pokemon ...

2026-06-04T15:15:22Z

In reply to nevent1q…lj0k
_________________________

probably. idk. I'm like 30 years out of the game on pokemon 😅

https://i.nostr.build/gKwQSBMoRlj6ikA0.gif idk where my friend is ...

2026-06-04T15:14:17Z

idk where my friend is getting these. But they are lit. would love the original artist to be on nostr.