<unnamed>

Public Key

npub16p8v7varqwjes5hak6q7mz6pygqm4pwc6gve4mrned3xs8tz42gq7kfhdw

Profile Code

nprofile1qqsdqnk0xw3s8fvc2t7mdq0d3dqjyqd6shvdyxv6a3eukcngr4324yqpp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgcfll9q

Publishing to

nos.lol

relay.primal.net

Last Notes

2026-02-24 09:44:04 CET

If you ever wondered why email is broken despite being an open protocol here is a reminder:
Of course today you cannot run your own email sending service realistically, you will be banned in no time. So as @nprofile…vr0z is using anchor (a push and email notif server for flotilla) I wanted to setup my own for BudaBit.
Well, it is not KYC but my account was flagged and suspended immediately after registration. Why? They of course will never tell me the checks they use, completely opaque but my name being causally set to 'John Doe' might be related.
Here's the info they actually ask to review my case:
"
Your account was recently flagged by our automated security system. This occurs when certain patterns are detected that may indicate a risk to our sending reputation. To protect the integrity of our platform, we aren’t able to disclose the specific triggers involved.
....
As your website is hosting very limited information, are you able to share more on:
1. The nature/business model of your business? Could you also tell us what your sites or apps are for, and which industry they belong to?
2. What products or services will you be promoting?
Also, If you have a beta site that is accessible and or screenshots of the site content please share those as well.
Getting to know sending habits of our customers is one of the ways Postmark protects your sender reputation and our overall deliverability, so thank you for your assistance.
"
This is the world without decentralized reputation.
This is going to be massively worse in the upcoming years.
People are not at all prepared for the consequences of this, especially with AI now proliferating.
Trust is eroding. The centralized players haven't the faintest idea what to do about other than KYC the hell out of everyone.
Only #wot can save us now. Freedom tech or bust.

2026-02-24 08:11:36 CET

- reply

No, it's not just auth:
That's why I built Budabit.club , the events are still signed and moderation is a good feature for communities.
- Communities can be interoperable
- Signed events mean forking groups is actually feasible, no other solution has this kind of guarantee.
- You can still keep other things open, and not exclusive: BudaBit keeps code collab features scoped to repo relays (even comments on issues etc) but you have the exclusive group to share things you want to actually be heard targeted to an audience that is there for a good reason.

2026-02-24 07:51:18 CET

- reply

That looks great! Couple questions:
1. Why is my current nip60 wallet not showing by default?
2. Do you only persist the seed(xpriv) locally? If I go to another nip60 client, how is my wallet generating deterministic keys?
3. Where do the mint recommendations come from?

2026-02-23 08:06:38 CET

- reply

SatShoot uses them.
Good for zapping small amounts for sponsored npubs (after you made money as a freelancer you can zap a supported npub) and later could be used for paid services.
The hard parts about implementing them with decent ux:
1. You have to handle state management very well to display a stable balance, and it's also depending on relay stability.
2. In-flight tokens (aka minted but unclaimed nutzaps) are in danger of loss if recipient cannot find it on relays, is offline for a long time etc. Since sender cannot claim those back by default it's slightly risky
3. Mint selection/discovery is crucial and must be addressed in a decentralized way (i.e. personalized nostr-native recommendations)
How SatShoot solves these problems:
1. We introduced seed based recovery (NUT 13) to have a secondary recovery path if you lose nsec or relays screw you
2. We will soon implement NUT-11 to be able to reclaim your nutzaps after a certain time passes and recipient hasn't claimed
3. Web of Trust based mint exploration. Shows which mints are used by your WoT for nutzaps (nip61 kind 10019) and builds a list rank-ordered by how many ppl use a mint.
So it's doable but I haven't seen other clients implement them because this requires quite some work.
Some do use cashu but not as nutzaps but by sending tokens in encrypted DMs.
Not bad at all, I just think with nutzaps you have better guarantees of no double-spending and you can build better verifiable public reputation than with untrusted lightning zaps.
You can experiment on https://satshoot.com with the wallet but it's for freelance purposes so you can't just zap posts (there are no posts).

2026-02-22 17:28:32 CET

- reply

The layered and context-aware solution I believe works and is feasible already:
- It all starts with relays. They must mitigate basic spam. Clients can only filter after they download realistically.
- Clients calculate a naive web of trust and hide everything outside by default (toggle to see filtered content)
- Bootstrapper account helps with onboarding (can be switched off)
- NIP85 trusted providers and requests- response type of social graph services like Vertex help extending your basic wot. Explicit opt-in is better because they're trusted. Client-side wot helps choose a provider, you see which your closest circles use.
- Clients must get better at the trust UX - displaying connection to a pubkey in a compact, informative and context-aware way
The best way to bootstrap trust however is communities.
Everything would become much simpler, and all the rocket-science in the world can't substitute that. Hope they gain more ground.
Nostr is the right tool for the job I believe but a tool is just a tool: We must use it well to achieve substantial progress.

2026-02-20 08:47:21 CET

- reply

That's not quite accurate.
Dig deeper in the headlines you find quite a couple of caveats.
Coding is quite well solved for the most part with AI but working secure reliable software is not (yet). At least not without guidance. It's a sophisticated tool. A very good one.
Doesn't replace taste and values. Neither does it substitute for architectural and product thinking.
Excited to ship more with AI but the job loss narrative only applies to the proverbial code monkey.

2026-02-20 08:47:05 CET

- reply

2026-02-17 19:25:27 CET

Thoughts to ponder #naddr1qp…dcj3

2026-02-16 20:10:28 CET

- reply

I second that

2026-02-14 20:39:56 CET

The ugly truth (and why I still use nip04 and don't give a damn about the true scotsman arguments) :
#nevent1q…y8rk

2026-02-14 07:08:23 CET

LET'S SET #BITCOIN CORE FREE!
https://v.nostr.build/RRqVdNDSxaDTM4mI.mp4
Yes, you can now migrate any repo to Nostr, with issues, pr-s and comments.
A couple of clicks in #BudaBit .
This will tag events created by profiles that can be matched to a Nostr account as per NIP39.
> They don't just host our code, they mediate our relationships. When your identity, issue history, contributor graph, and CI tooling are bound to a vendor's database, "open-source" becomes a veneer over a captured workflow.
This is an IMPORTant step for Freedom tech.
#gitvianostr

2026-02-09 09:15:30 CET

- reply

You forgot to add: "make no mistakes, make it secure"

2026-01-16 22:09:09 CET

- reply

You can use any platform you want, even mirror between them but keep them redundant by publishing the state of branches, and other metadata to nostr.
By keeping the metadata on nostr you are not locked in to platform identites and the data is actually portable because it's standardized in a NIP.
Gitea, gitlab, github, forgejo and others give you one model that is hard to migrate and data is not signed by sovereig identities.
In short you are married to their way of things

2026-01-16 21:54:38 CET

- reply

The tools for this either exist or are easy to build.
Relays are using all sorts of content moderation already.
That said, I don't think any software stack on nostr is mature enough to host a project like bitcoin core *currently* but things are movind fast around here.

2026-01-16 21:29:35 CET

- reply

Moderation tools exist for nostr relays already. You can blacklist/whitelist by kinds, pubkeys etc. and use all sorts of web of trust based moderation as well.
#WoT based moderation can be personalized so you can moderate even on an individual basis, seeing only those ppl you actually trust. WoT providers are also in progress to help in these kind of decisions.
Current efforts are spearheaded by the @nprofile…lh4w team

2026-01-16 21:24:35 CET

- reply

Yes, but the #grasp spec can introduce some proactive sync if enabled.
With the benefit of nostr based auth

2026-01-16 21:22:11 CET

- reply

For the source code part git is already decentralized enough, it is not worth trying to censor a repo cloned on tens of thousands of machines locally.
For the social part: censorship resistance is important but it can be a curse, like with radicle which cannot possibly get a decent UX.
As we see with bitcoin, we can hopefully keep one of the most important system decentralized while syncing state every 10 mins.
Nostr trades off with the possibility of centralization around one or a handful of relays, but at the same time it is trivial to backup the already signed messages which are republished any time, anywhere.
Nostr is the practical solution to this problem in my opinion.

2026-01-16 20:31:46 CET

- reply

Forgot to tag #gitvianostr for folks wanting to chime in.

2026-01-16 20:30:47 CET

@nprofile…y7h4 saw yall takin a look at decentralized git solutions and github replacement on bitcoin core discussion:
https://bitcoin-irc.chaincode.com/bitcoin-core-dev/2026-01-16
Here's a couple of sources and Nostr-based solutions you could give a try:
- NIP34 spec: https://nips.nostr.com/34
- GitHub-like client: https://gitworkshop.dev
- Discord/Slack type of client with Git-integration: https://budabit.club
- ... and some others, so there's quite some effort to make code collab work with Nostr
- The grasp spec is also interesting, it is a git server with nostr-native auth, designed to be easy-to-run and to accept code collab oriented nostr events, so a relay is packaged with it:
https://ngit.dev/grasp/
Grasp is the grug-brain solution to what radicle is trying to do for years but I think this has much better chance to work.
Why nostr?
Because it is more decentralized yet much simpler than Fediverse / Mastodon and Bluesky.
All above solutions lack full functionality compared to github but hopefully you can see where this is going.
It is trivial to moderate your relay, be it comments or any other events. Nostr-git is becoming increasingly standardized so your data is portable and signed.
Open to any questions!
cc @nprofile…hk4d @nprofile…xuyp

2026-01-07 17:49:52 CET

- reply

Value for value needs to incorporate (optional) vanity/status based features to go mainstream. In a way that already happened but we can do much better.
1. Data that's not taken from the past 15-20 years of high internet adoption doesn't matter too much
2. Ads vs. V4V doesn't need to be contrasted sharply: if I showcase the top zappers or make up some other leaderboard of zaps, is that advertising? Yes, to some degree but not totally.
3. What we really have established is that attention is valuable. 'What *kind* of attention?' - is a better question to ask. The flip side of this from v4v perspective is that donating without getting attention and acknowledgement back doesn't work very well
4. So what Adam Curry says about "You just need to ask often" is not enough, you need to do shoutouts, leaderboards, publish summaries, and generally do everything you can to make donors feel special and raise their status. No way around that if you want to take this seriously.
5. Yes, it is hard to do the core thing and this other promo thing too, but that's the way it is. The internet allows more publishing so creators need to stand out by being unique in their craft and also make that obvious, and get creative not merely in the product itself but how it is received. That's not unfair, that is competition
6. Are software developers the same kind of creators as musicians, podcasters, or long-form authors? Don't think so, and there are different nuances people can try to make this work.
The big picture in my book is that this topic is not settled by far. We just need to get more creative.

2026-01-03 07:59:52 CET

Very cool project, check it out!
Home Mining X Nostr zaps ⚡️🤝⛏️
#nevent1q…fh8p

2025-12-30 13:41:40 CET

Am an operator myself and love how nostr is gradually eating the lunch of all rent-seekers of the networking stack:
#nevent1q…4s36

2025-11-01 08:17:46 CET

- reply

Lately an important contributor to the Stratum v2 (bitcoin mining pool software) project was banned on GitHub:
#nevent1q…ye29
Bitcoin related projects handle backups of discussions like this:
"Currently, the backup is created by asking the API about changed issues and PRs and fetching and storing the response JSON." - [source](https://github.com/0xB10C/github-metadata-backup/issues/8)
When GitHub banned the account it removed important comments from the whole system (and from the backup too, it was badly designed but this is not the point).
A reaction to this from a reputable bitcoin contributor @ryanofsky:
"I kind of **hope this could be fixed on github's** end. I understand if a user was flooding github with spam it could make sense to delete all their comments and issues and prs. I also understand if a user requested all of those things to be taken down it would make sense to remove them. In both of those cases the archive should probably display the same thing as github by default, even if more data is available in the history.
But it doesn't seem reasonable for github to have nuked all of plebhash's comments and issues and I **hope they could just fix that.**" - [source](https://github.com/0xB10C/github-metadata-backup/issues/8#issuecomment-3474365848)
I think we can do better than hoping in GitHub, and storing unverifiable non-standard api responses.
I think we can move our valuable conversations around freedom tech to a better place - Nostr.
Can a Nostr relay censor? Sure. But your backup is verifiable data, compatible with the nostr app universe, deployable easily on a gamut of relay implementations in minutes.
This is one goal of #BudaBit .
The other is to make the FOSS process a supercharged community effort:
#naddr1qq…6e3k

2025-10-20 18:30:34 CEST

Dev story time: How SatShoot ended up using partial #outbox model:
Using NIP65 relay lists to decentralize discovery looks like a fantastic concept at first...
And then you realize that most things taken to extremes ends up in the complete opposite way you intended.
This is true for the outbox model. You want decentralization. Maybe you convinced a lot of people to publish outbox relay lists (BIG maybe), so far so good. Still, you ended up with an app that connects to hundreds of relays **and keeps those connections alive**.
Problems:
- app uses a lot of data
- app will make your phone run flat in no time
- app likely gets heavily resource constrained by the OS when user switches away, relay conns are killed
- app code has tremendous added complexity (perhaps the worst of all!)
So what this effectively ends up doing is:
- only native apps will be able to handle this kind of load, maybe only desktop apps
- only people with close-to unlimited data plans will be able to use your app
- very few people will be able to understand your code, if any (including you)
So you ended up introducing all these centralizing dynamics, while users don't even understand or appreciate why you did it. And of course it all still relies on purplepages to fetch the initial lists, right? ;)
I had a better idea (communities are even better but until they come online this is my approach):
1. Use explicit relays by default, let normal users set explicit relays, and superusers set outbox too
2. Publishing is simple since it is targeted: you just publish to explicit relays + outbox (or inbox of target if it's a reaction to sth or mentioning someone)
3. You calculate optimal relays and fetch all relevant events ONE time, on a user-triggered "Decentralized Discovery". This should explain what's happening and why it's super cool.
4. Show the progress and at the end, add top relays to the pool for that session
5. User thinks "This is cool, I'm doing the Decentralized Discovery, Nostr Rocks!" and you did not have to keep all those connections and constantly keep score and all that. Just do it once.
This is now implemented in SatShoot:
https://v.nostr.build/8bZAOIjVjsCf41pm.mp4
Opinions?

2025-10-03 07:58:30 CEST

Social media has never worked, and will never serve people, ever. But there's a better way.
Social media was bootstrapped from communities, and then bastardized them to sell people off to advertisers.
The embrace -> extend -> extinguish paradigm that feeds on distrust and discord.
I am increasingly astonished that freedom-minded people ever thought that this distorted view of society can be tweaked to suddenly become useful. Reminds me of communists trying for ever to make their central planning "paradise on earth" a reality. Well, I guess that deep envy and resentment covered with moral camouflage will never go away either. It is highly attractive to the leeches of society.
It's time to wake up. And time to invest in communities. Nostr can really shine if it can let go of the dopamine-fueled NGU vision of social media.
You want to get closer to how people actually form successful relationships? They create families. Big families that form the root of trust. They extend it with friends, and they further extend the circle with communities forming around common interests and goals.
Nostr can make these communities compatible with each other, with less lock-in, better discovery and more flourishing than any other model we have had so far.
Just enough technological enhancement, with people's real interests in mind. No other way.

2025-09-29 06:42:21 CEST

[Hivetalk](https://hivetalk.org) is one of my favorite nostr apps, and it keeps getting better!

2025-09-21 17:19:52 CEST

I have a very strong conviction that Nostr cannot be captured by big tech at this point.
They can just ignore it.
Unless...
Let's start at the beginning: Nostr's simple design makes small room for attacks on Nostr itself: closed source software, lack of event verification, proprietary APIs rather than querying relays directly, no relay selection in clients... these type of things are trivial to spot.
I also firmly believe that event kinds will in time consolidate and ossify, it's a strong incentive for players in the same industry/area.
Decentralized relay management will get stronger too, as best practices form. We have relay selection on the user level with sane fallbacks/defaults as a starting point. Things will be fine on this front as well I think.
**The biggest threat right now is not doing the hard work to implement quality software with viable business models supporting the projects.**
Big tech has hordes of fiat code monkeys to deliver convenience. They don't have anything else than that though. They cannot do what freedom tech enables.
What is your edge?
Delivering freedom in a way people can receive it: build it up from sane default options gradually towards sovereignty. You can start with convenience but surface the options with care in due time.
This seems to be harder to do than the walled garden model, but actually pays off long-term handsomely: your users will be more educated and thank you for it because you were there when they were in the dark, when they needed you most. They will become your apostles, and network effect might build up.
For people who are afraid of "doing nostr in the wrong way" or "cannot find the exact way to do xyz", consider this:
No client app is profitable yet. Take everything with a grain of salt other than basic OS principles, freedom tech values and NIP01, which are crystal clear.
Use the OS code: look at it, play with it, fork it, think about it. There's no real substitute for that. You can read a million pages of spec, vibe code for ever to fake it till you fail, or go get your hands dirty and master it in no time. Yes, it takes more effort to do, than to consume. Demonstrate Proof of Work.
**Don't let fear guide your decisions! Build in a permissionless way, on a permissionless protocol.**
If you get dragged down arguing on NIPxyz on github or anywhere else rather than building for your target audience, you lose.
You lose because you are relying on futile reassurence instead of passion to deliver value. To ship the future.
Don't ever let them steer your ship.
The only thing you should be afraid of is opportunity cost of the precious time that distracts you from building.
If only a handful of people do this, we will win. Those who read this far might be the ones.
Go _build_ the future you want to see in the world.

2025-09-11 10:03:31 CEST

The most reliable energy source for freedom tech development is if you first and foremost do it for your own (or family or loved ones') sake, not for "humanity".
Humanity can do without you, and you don't need to save everyone. Just care for those next to you with low time-preference, and see the magic happen.

2025-08-08 18:06:13 CEST

- reply

Let a thousand nostr git projects blossom!

2025-08-05 07:02:01 CEST

- reply

Once you have an onchain address, you can send as much as you want unlike with LN.
The mints would have no control over how much money they are comfortable with handling. Since still a lot of things are experimental in this space and mints have non-negligible risks, this would possibly create an unwanted situation for them.
Refunding is an option but in practice it might be complicated.

2025-08-04 12:25:53 CEST

- reply

I assume yo are talking to a software engineer.
I would follow up with a question to clarify the areas of interests / experience and point the person to one of the open-source projects to get inspired.
The benefit is that most probably the person can view a live version of the app which is cool, and the repo would explain what NIPs, libraries and tools it uses.

2025-08-03 20:11:08 CEST

- reply

On a bitcoin standard people can thrive from the fruits of the radically free market, as long as they demonstrate creativity and proof of work.
I think in the era of AI, the process of obsoleting redundant work is accelerated, which puts those people in the top ranks that strive to learn every day, coupled with strong work ethics and integrity.
As to the early stackers:
It doesn't matter in the long run how much you stacked early. What matters is if you can really see the world through the lens of bitcoin and understood its implications. And it's never too late.
The idea that "those who have plenty will be given even more" seems like a proof of stake idea from this perspective and doesn't make sense in a system based on proof of work.

2025-08-02 20:18:12 CEST

- reply

How are you constructing the right filters for the right relays to fetch new posts for the "follows" feed?
Are you sending filters with all the user's follows listed as authors to all relays, or you do some smart selection ?

2025-08-02 20:03:59 CEST

- reply

Only counts if logged on #runstr :)

2025-08-02 20:00:51 CEST

- reply

And it's a nostr-based list, access token is only for pushing to github-hosted repos after merges

2025-08-02 19:59:14 CEST

- reply

You don't need an api key (fine-grained access token) to work, only if you have your repo hosted on github only. For reading the repo you don't even need the access token, only if you want to perform push operations.
Otherwise it will work with gitlab, gitea and such, plus of course in due time with grasp servers, bc that uses nostr-based authentication which will be the best user experience with budabit.

2025-08-02 19:53:28 CEST

- reply

Every user tracks their own arbitrary list of repos. See "Edit Repos" btn

2025-08-01 20:24:42 CEST

In the morning, I am reading nostr.
In the afternoon, I am building nostr.
In the evening, I am reading "Building NOSTR" by @nprofile…rts7 .

2025-07-31 18:40:38 CEST

- reply

Realease! Merge PRs on BudaBit!
We are in the process of making #git social and obsoleting GitHub!
https://v.nostr.build/ExVAUNExNeJlOSz0.mp4
[BudaBit](https://budabit.club) is a developer community app powered by #Flotilla from @nprofile…rts7 and nip34 #gitvianostr !
Check out our running site where we are constantly shipping new features, or host your own community !
#nevent1q…kmrl
PS: Hit me up on nostr if you want in and you're not whitelisted!
#grownostr

2025-07-25 17:57:49 CEST

- reply

Care to post some of them as [Satshoot](https://satshoot.com) Jobs?
Good use-case, looking for feedback from clients and freelancers.

2025-07-23 06:22:13 CEST

- reply

Yes that's the idea, basically.
If I want to send ecash as payment for freelancing on [SatShoot](https://satshoot.com) I want to do it with p2pk so it is easy to build Reputation from provable zaps, published to nostr but tied to the recipient pubkey.
The problem is when the zap cannot reach the recipient which could be due to multiple causes but I want to have a safe path for clients to get back the p2pk ecash that was never redeemed by the recipient freelancer.

2025-07-22 20:31:38 CEST

- reply

What about NUT14? Refund path of an HTLC-locked proof is not reverting strictly speaking but a way to spend otherwise promised ecash right?
I'm thinking about using that to undo p2pk zaps if sth happens and recipient doesn't receive and redeem a zap in a week or two.
What do you think?

2025-07-16 20:03:15 CEST

- reply

People still use the term "vibe coded" for any code the LLM wrote which is confusing.
It's not vibe coding to have the LLM write parts of your code, integrating it after careful review. Vibe coding is to not look at the produced code at all, and switching off your engineer brain completely, by blindly adopting anything the AI generates. This is mostly silly, if not done for pure hobbyist purposes.
I can of course imagine scenarios where you only need a minor tweak in an open-source app that you can just blindly get done with AI, but again that's not the heavy-lifting. It's like playing around with Wordpress themes at most.
And I don't need to keep hammering on this point really much, the results speak for themselves.
LLMs are really useful, and it will keep evolving, and we will keep using it in novel ways e.g. MCP.
However, for a piece software to be useful on the margins where ppl choose the best products, AI is going to merely raise expectations on quality.
Now, it might be the case that the verb "Vibing" will make it to common language to mean "I generated this code with an LLM" but this has not been its original meaning.

2025-07-16 18:48:23 CEST

- reply

https://github.com/coracle-social/anchor by @nprofile…rts7
Can do postmark as well as push notif with Firebase or Apple push

2025-07-16 16:44:02 CEST

- reply

You can post your Service on [SatShoot](https://satshoot.com) , if you want to earn sats and start building provable Reputation on nostr.
I recently released a new version and am looking for feedback from freelancers !

2025-07-16 15:15:51 CEST

I learned previously from @nprofile…vmd0 that I can use Neovim with goose and goose.nvim to integrate LLMs in my Neovim IDE.
I did it with OpenRouter but it doesn't accept Lightning in practice (some crapto shitcoinery with awful wallets is possible but no thanks) .
Then I have been casually listening to @nprofile…yne0 with @nprofile…when I learned they have an API that is compatible with goose! Integrated without a hassle with the nice tutorial I found on the site!
Thanks @nprofile…zup6 and @nprofile…mwff for the actionable Bitcoin discussion!
https://npub16p8v7varqwjes5hak6q7mz6pygqm4pwc6gve4mrned3xs8tz42gq7kfhdw.blossom.band/8a550733c691d3c3a3a127199f118fc5307ade473991882f639e2f3fd950cb49.png

2025-07-16 07:55:33 CEST

- reply

Why we need great UX and services like #Vertex around Web of Trust:
#nevent1q…53dk

2025-07-15 19:11:55 CEST

Hey @nprofile…87xe are you guys planning to host another #nostrville this year?
I always wanted to visit bitcoin park, and this would be a good purpose to do that.
cc @nprofile…f670

2025-07-15 06:53:54 CEST

- reply

This is an insane story!
Great talk, thanks for that!

2025-07-13 17:28:04 CEST

- reply

#Vertex coming to you on #SatShoot this autumn.
#nevent1q…vs7v
Also, I believe that at least in the marketplace usecase like SatShoot, the right way to introduce this feature is as a premium introduction service.
1. In addition to freealance-scoped follows, User has a naive #WoT calculated client-side every couple of hours, and an opt-in WoT from SatShoot's npub that can be switched off but helps in bootstrapping
2. The user will have additional lists of people he trusts e.g. from communities' members-lists or other nip51 lists
3. If this is not enough to introduce the parties, Vertex comes into play, trying to find reputable followers of the party that is analyzed. This is important for marketplace actors, who always try to grab opportunities but want to get rid of potential bad actors as well.
They will pay the fee, and it will be worth their sats.
A successful outcome means the new counterparty can be added to the freelance follows and other lists possibly.
P.S.: A naive 2-step wot with follows, mutes and reports is like 10-20 seconds to produce rather than minutes, it's more about the limit of reach than anything else.
@nprofile…6rpa
@nprofile…f670

2025-07-13 14:25:22 CEST

[Dogfooding](https://satshoot.com/naddr1qvzqqqrllupzp5zweue6xqa9npf0md5pak95zgsph2za35sentk88jmzdqwk925sqqk4xct52d5x7mm594jx2a3d2fjhwmmjdvkhqcted4jkuapdv4u8qetjd9jkucm994sk27nkxfmsc8f9hq) #SatShoot with awesome nostr devs is one of my favorite experiences with open source development.
Bullish.
#freelance #grownostr

2025-07-07 06:57:40 CEST

- reply

There should no 1 leaderboard.
Payments to centralized parties don't solve this problem either. It just reinvents existing enshittified apps.
Web of trust should filter out untrusted pubkeys for users, so everyone sees their own subjective leaderboard.
This is one of the most profound paradigms only nostr enables.

2025-07-06 20:38:27 CEST

- reply

Slowly but surely nostr will take the wind out of their sails, to the degree people want more control, more optionality and customization.
Getting rid of a continuously breaking proprietary api in favor of a protocol with sovereign identities seems like a better way. The walled gardens are not easy to leave though. Will take time.
For now, we're getting close to a nice feature set that covers plenty of use-cases. I almost never open github these days.
Keep building momentum.

2025-07-06 20:23:59 CEST

- reply

#nevent1q…tlsd

2025-07-04 18:57:15 CEST

Satshoot Release!
It's been a long-long time!
At last, Freelancers can post Services on [Satshoot](https://satshoot.com) !
If you want to earn sats and unstoppable Reputation, this is your moment.
The freedom economy is here.
https://i.nostr.build/IfDeXXXHaloCrG0F.jpg
Other major changes:
- Switch between 'Freelance' and 'Client' mode
- New branding elements @nprofile…56gx
- Sponsored npubs by @nprofile…tj7x . You can split the optional kickback pledge between Satshoot and a chosen npub, defaulting to @nprofile…4ph5 , who keeps shipping the most important dependency of Satshoot, #NDK
- Started to upgrade the #ecash wallet which will use NUT-14 HTLC-s to make payments safer, and NUT-13 to make the backup-process much better. Therefore ecash payments are temporarily disabled
- Upated a ton of stuff to future-proof the project
Special thanks to Daniyal at @nprofile…ywhu ! He did most of the work on this release.
Its hard to overstate how I feel about this... a year ago my goal has become clear at SEC02 @nprofile…3ra5 :
Create a freelance market that is worthy of the values bitcoin represents, on nostr. I feel like that time has come.
Please, hit me with your bug and issue reports and feature requests, especially on #gitvianostr !
Keep dreaming, keep building!
#satshoot #freelance #freelancing #grownostr #sec

2025-07-03 19:53:03 CEST

- reply

My estimation is that the norm will eventually be to hide absolutely everything outside of the web of trust by default, and show only optionally.
As a minimum posts should be ordered by wot.
Also, kind3 follows and 10k mutes are just the beginning. Communities will offer more reliable starting points.
Other nip51 stuff is also useful.
Context is key, and the general kind1 client use-case makes it hard to find that specific context where wot can be fine-tuned to user needs.

2025-07-01 06:21:42 CEST

- reply

If you want to shape the future for the better, listen to this, and apply for @nprofile…3ra5 .
Question: What do 21 crazy people do in a small Island on the the Atlantic ocean?
Of course they are changing the world.
#nevent1q…c7p5

2025-06-29 17:49:27 CEST

- reply

Singularity would be this post published by a machine.

2025-06-28 18:28:08 CEST

- reply

Marching ahead with #BudaBit , where you can own your sovereign developer community, using nostr!
- Search and Bookmark multiple Repos
- View Repo metadata
- View Issues, Patches, Comments
- Browse files and Commits
#nevent1q…xcrh
View live [demo website](https://budabit.club)
Features are added rapidly!
Soon:
- Edit issues
- Sharing git stuff in rooms and threads
- Merge PRs
- ... Our short-term target is to manage the whole development workflow in BudaBit
PS: If you want to join and your not whitelisted contact me on nostr or deploy your own BudaBit community, it's open source and just a static PWA you can host very cheaply, using your own name and branding !

2025-06-26 18:44:07 CEST

- reply

I see you did some work on this recently, if you say it's totally up-to-date I will zap you

2025-06-26 18:33:50 CEST

Hey @nprofile…rts7 I'll zap you 200k when you update the docs of welshman!

2025-06-16 07:21:36 CEST

Marketplaces thrive on liquidity and trust. The two seem to go against each other on the surface.
The more liquidity the more people, the more bad actors, the harder to maintain trust in general.
The safer you want it to be, the more trust you need between parties, the less people you can allow, which comes with reduced liquidity, unless everyone is trusting one entity which comes with its own downfall when those become parasitic middle-men.
Nostr is the solution to this problem. The more apps you are using, the more connections you can examine, the easier it is to introduce parties.
A high level of Liquidity can be achieved while trust is not eroded in the market.

2025-06-15 06:53:26 CEST

This kind of hustling for perms in an endless loop should not be happening:
https://v.nostr.build/uHCDllCLgHCTaWdw.mp4
#primal

2025-06-06 17:00:02 CEST

- reply

Bitcoin:
https://satshoot.com/naddr1qvzqqqrllupzp5zweue6xqa9npf0md5pak95zgsph2za35sentk88jmzdqwk925sqy88wumn8ghj7mn0wvhxcmmv9uqsuamnwvaz7tmwdaejumr0dshsqv2zd96xxmmfdecxcetzwvkk7un8943xjarrda5kutt5v9e8gctvdakj66edwdaz6apdwvkhx6mydpk8xzhgy33
Nostr:
https://satshoot.com/naddr1qvzqqqrllupzp5zweue6xqa9npf0md5pak95zgsph2za35sentk88jmzdqwk925sqy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uq3wamnwvaz7tmzd96xxmmfdejhytnnda3kjctv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcppemhxue69uhkummn9ekx7mp0qqh5y6t5vdhkjmnsd3jkyueddaexwt2wdaehgu3dw3shyarpd3hk6ttt94eh5tt594ej66tsx9hrj7g06n7f4

2025-06-06 16:45:28 CEST

- reply

Lehetne az is hogy @nprofile…z5fk bitcoin tartalommal, @nprofile…jpnk pedig noszterrel járul hozzá

2025-06-06 09:21:06 CEST

- reply

És mivel egy-két tartalomnak jót tenne egy kis frissítés (meg akár újat is lehetne belerakni), írjon aki dolgozna ezen egy két hónapot, satban fizetek.

2025-06-06 07:34:44 CEST

- reply

That's truly inspiring!
Thanks for cashu ts !

2025-06-06 05:05:56 CEST

- reply

Outbox getting out hand.
Communities will constitute a good middle ground, or even substitute in many cases.
#nevent1q…xqa5

2025-06-05 19:58:07 CEST

- reply

The problem is that the user doesn't know the trust tradeoffs of the app.
If it's about money you can easily degrade trust if user assumes things that turn out to be different.
Look at test.satshoot.com for an example flow. It could improve a lot but it's sth.
You could create a new account, go to wallet and deposit a minimal amount. Then withdraw.
Or you can test payments too. Follow that new npub with your account inside satshoot to appear in your freelance WoT and create a test Job, place bid, accept, close and pay with ecash.
It is being reworked somewhat but gets you an idea

2025-06-05 19:32:29 CEST

- reply

No default.
I would show what the user's web of trust uses, otherwise just random announcements from mints.
Would you choose a bank for a stranger?

2025-05-03 14:29:48 CEST

- reply

Good one! :)
Yeah I am aware of the debate, I'm just not too keen to make haphazard speculation on things like this.
And not all core devs are on board with this the proposed change I believe.
It is a good opportunity to learn though

2025-05-03 12:59:17 CEST

- reply

Can you show me an Austrian economist who says small inflation is beneficial?
Yes they like gold because it has been the *least* inflationary. Until bitcoin.

2025-05-03 12:56:39 CEST

- reply

I'm not looking for an authority to form opinions, and I encourage you to do the same.
Explaining how bitcoin incentives will play out using bayesian methods is a fools errand in my book:
- How do we know the rate of lost coins in the future, or the ratio of fees in the reward? Extrapolate from the past? There's no reason to accept that logic
- How do we know that miners need this extra subsidy, when other crypto currencies have never even come close to being adopted as money, and bitcoin is also far from it?
"...academic analysis has found that in this condition [only fees in the reward] block generation is unstable." - So they claim to know how this would work, even though there's absolutely no way to know this.
"The fact is, economic volatility dwarfs the effect of small amounts of inflation. Even a 0.5% inflation rate over 50 years only leads to a 22% drop"
*Only*. Really? Who says that's so low? This line of reasoning looks like taken directly from a Keynesian textbook. And taking bitcoin's current volatility as an example is just a blatant error at least, disingenuous at worst.
I'm all for good explanations, but this is a weak one, because I can substitute these arbitrary numbers and angles with any others that suit my needs. It's statistical cosmetics.
The future of bitcoin and mining is fundamentally unpredictable because humans are. Therefore, I like explanations based on first principles but no amount of statistical trickery will do any good in this matter.
I respect Peter Todd. But this is nothing but a "nice excuse to use some mildly interesting math, in the end it’s totally pedantic."
Austrian economics teaches you a lot on these matters, can recommend those instead.

2025-05-03 12:00:16 CEST

- reply

Sorry, but this is bogus.
Trying to describe what will happen to bitcoin with Bayesian probabilities leads to really bad conclusions. This is what Keynesians try to do in fiat economics textbooks.
It doesn't even scratch the surface of reality.

2025-04-30 20:06:28 CEST

- reply

We will make GitHub obsolete.
We will make Discord obsolete.
We will make LinkedIn obsolete.
We will make BigTech obsolete.
#naddr1qq…e9ev

2025-04-30 09:10:04 CEST

Big power outages in areas where it's unexpected like yesterday help us realize how we can all of a sudden become dependent on each other again.
Better not forget this, try to be nice to people or at least don't shit on them for petty reasons.
Oh, and get some things that help you last longer like:
- UPS with backup power sources
- Physical cash (ecash in a cypherpunk future)
- Alternative communication devices like meshtastic or ham radio
- Oil lamps, candles and such for lighting
- Spare fuel
- ... hellknows, visit these survivalist sites :)
Also good to know, the Mandibles writes about an event like that, as sort of a precursor to what comes after...
There will be signs.
https://stacker.news/items/966046

2025-04-30 06:30:15 CEST

https://i.nostr.build/AQHCJD87OPtORavn.jpg
Using #zapstore installing latest #Coracle . If someone sends app to google, will it stop popping up these warnings for everyone at some point?

2025-04-29 20:46:45 CEST

- reply

So stringent :)
But yeah I understand

2025-04-29 20:07:08 CEST

I need DMs in SatShoot. I also need them to show up on other clients, to have more reach when important things happen, like a Bid lands on a Job.
#Amethyst is planning to drop support for nip04 which is understandable...
But here's the problem: I actually don't want SatShoot DMs to be deniable in case of a dispute between the parties, like we have in nip17.
And since the parties are already related due to the SatShoot deal they have between each other, privacy is not of utmost concern in this case anymore. Encryption is enough is it not?
Mostro uses a special scheme to hide metadata with gift wraps but on level 2 the message is authenticated, not like with rumors in nip17 (and there's a twist for moderation purposes but let's not go there).
While I Iike that solution, it is not interoperable with other popular apps.
I also thought of supporting both nip17 and nip04 at the same time to be more compatible but seems stupid and wasteful.
Wonder what's the best decision here?
@nprofile…pyug @nprofile…5gcs perhaps you can chime in?
#asknostr

2025-04-29 15:25:10 CEST

- reply

Yes I think so, hidden onion services are only accessible via tor.
And possibly we would have to run some tor-relays to bear with the higher traffic.
Ecash could help incentivize such a network without relying on altruism alone.
There are other protocols like i2p and freenet (and possibly mesh networks and such) as a substitute or fallback but I think at that point no one would be able to predict how that situation would really play out.

2025-04-29 09:07:21 CEST

- reply

If the whole establishment tried this with full force they might succeed...for a while.
But it would reveal nostr-s supremacy and draw a lot of attention, and ppl would try to make it work by almost any means:
- Run relays behind tor
- Disseminate relay lists on DHTs
- ... ?
It's just a reality that you cannot suffocate sth that is heavily in demand worldwide. Humans find a sly roundabout way.
Look at the example of torrents and pirate bay.

2025-04-29 06:26:05 CEST

UTXOs - The jargon is used often among bitcoiners - but how do they really work?
Here's a video I produced for bitcoinplebs.org that shines light on the UTXO model(not my voice haha):
https://v.nostr.build/meYk.mp4
Another interesting diagram shows how UTXOs are created and destroyed under the hood by your wallet:
https://bitcoinplebs.org/assets/img/diagrams/hd_wallets_and_utxo_model.drawio.png
Enjoy learning about bitcoin!
#bitcoin #utxo #education

2025-04-28 22:42:43 CEST

- reply

Primal has an issue with URL parsing.
Try another app if that's the case.

2025-04-28 15:51:51 CEST

Hey Nostr,
Please help me with this issue and I can pay sats for your time:
## SatShoot Logo, Brand Design, and Branding Guidelines
# SatShoot Brand Design Project
## Project Overview
SatShoot is a freelance marketplace built on Nostr, originally focused on Bitcoin freelance gigs which is about to launch its beta service. We aim to establish a strong, memorable visual identity that reflects our values of freedom, decentralization, and peer-to-peer connections.
We are seeking a skilled freelancer to create:
- A distinctive and memorable logo
- A comprehensive brand design
- A detailed branding guideline for consistent future use
## Business Information
### Business Purpose
SatShoot creates a job market worthy of Bitcoin's values: a place where clients and freelancers connect without restrictions. Unlike centralized platforms that exploit users, SatShoot leverages top-notch freedom technologies to foster an unstoppable gig economy for freedom-minded professionals.
No rent-seeking middlemen, no bad incentives leading to a race to the bottom — just satoshis paid for honest Proof of Work.
### Brand Adjectives
- Freelancing
- Inclusive
- Fair
- Gig-economy
- Talent
- Open-source
- Nostr
- Web of trust
- Cashu ecash
- Bitcoin
- Reputation
- Lightning
- Freedom tech
- Open market
- Instant payments
### Ideal Client/Target Audience
Freelancers, solopreneurs, and small teams: people seeking to earn sats for gigs. On the client side, Bitcoin companies, teams, or individuals looking to commission projects. While freelancers must be Bitcoiners, clients may pay in sats even if they are not fully aligned with Bitcoin ideals.
### Unique Selling Proposition
SatShoot eliminates the middleman through freedom tech. It builds unstoppable reputations, is Nostr-native, and Bitcoin-only.
- Creates opportunities to earn sats — an "earn ramp" for Bitcoiners, even in underbanked regions or economically challenged environments.
- Offers a voluntary revenue-sharing model where freelancers set their own pledges to SatShoot, enhancing their reputation.
- Clients can also pledge sats voluntarily at the end of a job.
- Future optional services like recommendation tools may be introduced, but forced cuts will never be part of the platform.
- Connections, deals, and reputations are influenced by individual preferences such as selected relays, followed people, hashtags, and past transactions.
- SatShoot integrates seamlessly with the Nostr ecosystem, supporting DMs, status posts, public zaps for payments, and relay selections that appear in other apps as well.
### Services Provided
- Matchmaking
- Discovery
- Connecting clients to freelancers
- Bidding process for clients to get the best offer
- Reputation building
- "Contract execution" with built-in encrypted DM chat and Bitcoin-based payments via LN and Cashu
### Competitors
- Fiverr
- Upwork
- LinkedIn job postings
- Crypto/blockchain freelance solutions that take forced cuts
- microlancer.io (similar features but less serious and engagement-focused)
### Business Goals & Future Expansion
Enable the freedom economy of freelance with the right incentives, eliminating middlemen. Drive more economic energy towards Nostr and Bitcoin. Aim to make SatShoot the largest Bitcoin-only job market, particularly for software development.
### Logo Usage
- In the web app
- Nostr posts
- Other media appearances on Nostr
- Flyers
- Conferences
### Creative Considerations
Blue is essential in the design — not necessarily the current shade, but blue in general to convey professionalism, expertise, and peace of mind. SatShoot aims to facilitate fair deals, ensuring users engage with people they trust based on their actions and preferences.
## Deliverables
### Logo Design
- Primary logo (full color)
- Monochrome variant
- Icon-only version for compact usage
### Branding Guideline Document
- Logo usage rules
- Color palette (including hex codes)
- Typography guidelines
- Visual identity principles
### Brand Assets
- Web and social media banners
- Favicon and app icons
## Timeline
Please provide an estimated timeline for deliverables.
## Budget
Please submit your estimated cost along with your proposal.
## Submission Requirements
When submitting your proposal, please include:
- Examples of previous logo and brand design work
- Any initial ideas or concepts inspired by SatShoot's vision
We look forward to your creative vision and expertise in shaping SatShoot's identity for the future.
Make an offer on this URL:
https://satshoot.com/naddr1qvzqqqrllupzp5zweue6xqa9npf0md5pak95zgsph2za35sentk88jmzdqwk925sqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uqsuamnwvaz7tmwdaejumr0dshsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshsqw2nv969x6r0da6z6nr0vahj6snjv9hxgt2yv4ekjemw94skuepdgfexzmnyd9hxwt28w45kgetvd9hx2uedwsch2urdds5dszls
#asknostr #branding #design #logo #satshoot

2025-04-23 16:24:05 CEST

- reply

I wouldn't know, I'm nostr only.
Had a minor problem with your primal link on the site though:
If I opened it on the web in a new tab it worked but I have primal android installed and that one gave this error on clicking the nostr link:
https://i.nostr.build/r9HehqA6ZGpxa3tZ.jpg
Must be a primal problem on the looks of it

2025-04-23 14:31:07 CEST

Was looking for ppq.ai npub, only npub.world was able to find it, basically instantly!
Thanks @nprofile…6rpa !

2025-04-22 20:05:24 CEST

- reply

The difference is just that SatShoot uses a bootstrap WoT, that is based on the social graph of the official SatShoot npub, while the other one is the user's own.

2025-04-22 18:04:19 CEST

- reply

There is search but lately the "my repos" is gone. It used to be available by just clicking on my profile image.
I guess that can be quickly fixed

2025-04-22 15:35:17 CEST

In the veins of building in the open, I'll share my recent ruminations of WoT and Reputation in SatShoot:
https://i.nostr.build/QLbJLX9hXMXYAuef.jpg https://i.nostr.build/cyhsatVZqPob6uGS.jpg
Feedback welcome! ( @nprofile…6rpa !)
This plan is about 50% done and it will be complete after "Freelance mode" is implemented (switch between freelance and client role in the app) along with the ability to post your Freelance Services rather than merely Clients posting Jobs.
#wot #grownostr #ux #freelance #satshoot #vertex

2025-04-18 16:23:03 CEST

- reply

Thanks!
Okay... so I guess this explains why NDK tries to redeem found nutzaps immediately.
SatShoot uses Cashu payments optionally next to LN to pay for Freelance services(with an "experimental" warning ofc) so this is kinda important to me.

2025-04-18 12:21:21 CEST

- reply

Thanks for the article!
Can you elaborate on the DLEQ proof?
How it works and why it is important?
I think that nip61 nutzaps don't yet use this but it is still considered only spendable by the receiver.
So it boils down to this question:
If I received a nutzap offline and trusted the mint, but there is no DLEQ, is that not final settlement yet?

2025-04-18 10:51:19 CEST

@nprofile…xafw @nprofile…qft7 : The collapse of the wave function and the Copenhagen interpretation is a serious scam, and an attack on science itself.
The best scientific explanation of the two-slit experiment is the Multiverse theory, introduced by Hugh Everett and taken further by David Deutsch.
You can read about this in layman's terms in The Beginning of Infinity, a great book on science and philosophy by David Deutsch.

2025-04-16 22:14:33 CEST

- reply

Thanks for the your thoughts and suggestions!
There's a lot to think about when it comes to communities but at the end of the day shipping something and iterate on user demand will be most prioritized.
I read your spec(and saw you launched your communikey, congrats!) but will be more confident in my assessment of the communikey approach when I see more things fleshed out.
As to the reply sections, I believe there is room (pun intended) for more frequent and less formal discussions around nip34 events, and a place to post the more formal stuff (repo relays).
Any community could set up its own moderated space around any repos is good overall I think.
Zaps are a great thing but not strictly necessary to launch something useful in my mind.
Also, copying some stuff that github does well doesn't hurt. It's about fusing github and discord with nostr paradigms, that creates a unique end result.
This is the best thing about nostr: the better UX wins, and ppl can target multiple niches.
All the best, and keep building!

2025-04-16 07:45:46 CEST

- reply

Then I might be wrong about this.
I think the compatibility would help in a hard-core censorship scenario. If all bootstrap relays like purplepag.es or damus are methodically censored on the dns level, there is no starting point to discover users relay lists.
In this case some trustworthy pubkeys could just run a homeserver relay and the pubky protocol essentially allows to access those in such a scenario.
Also, anyone could run their own personal relays in a censorship-resistant way. Say you are Alex Jones or on some high-level blacklist, you would run your stuff on pubky, so you have a censorship-resistant pointer to your relays.

2025-04-16 07:35:24 CEST

- reply

Can recommend latest [TGFN](https://thank-god-for-nostr.simplecast.com/episodes/frostr-wBOrP0Te) episode on Frostr.
It achieves the following:
- You can chop your nsec into shards (shamir secrets). These can generate valid signatures with an arbitrary threshold you configured initially
- You have your nsec (or just the shards of it) in cold storage and can distribute shards to bunkers, even custodians with high uptime in a safe way (eg 2 of 3, one at a custodian, one hot in your bunker and one only used when rotating)
- You can rotate the setup to a new set of shards. However, all setups remain valid (possible problem but not if you don't leak your cold storage nsec or threshold of shards). You cannot rotate your nsec though.
This achieves a kind of key rotation without nsec rotation, and still needs bunkers.
A subkey system would simplify the bunker problem but at the huge cost of transmitting, storing and coordinating a bunch of data on nostr for all events for just the subkey-related stuff.
The coordination part is the nastiest: Nostr is distributed so there is no guarantee of consistency. Therefore I wonder how you want to solve the problem of
"Am I really, really sure that I validated this event against the absolute latest state of this user's keys?
Was this event really signed before that old key has been deprecated?"
Nostr is designed so that no relay needs to be an absolute source of truth. The events themselves, signed by the pubkeys are. Self authentication. But what do we do when this assumption is broken? It all falls apart. You cannot have absolute consistency on nostr.
...and subkeys would not simplify the master key leak either.

2025-04-15 19:47:07 CEST

- reply

Much discussion went into this topic, and the conclusion has been so far that the interoperability of nostr apps would be seriously threatened by such a move.
We have nip46 bunkers and now with #Frostr I really think the subkey hell can and will be avoided.

2025-04-15 19:41:15 CEST

- reply

This is a great answer!
Also, I learned that the two protocols could be made compatible but sadly they use different cryptographic curves (pubky: ed25519 vs nostr: secp256k1) which makes this kinda problematic.

2025-04-13 08:09:58 CEST

- reply

It's funny how people time and again come up with the idea of "neutral language" and "just the facts". It's a fools errand, or more like an oxymoron.
All facts and observations are theory laden.
Compressing information about things happening in the world and helping one to make sense of it, i.e. news reporting is a service, and there is one fundamental aspect to this service:
People are interested in *other* peoples' views on things happening in the world. A different perspective than theirs. This is the only way to get truly new information because they intuitively know that this new perspective is valuable:
It helps them correct their systematic errors and misconceptions. Without it, they cannot improve.
What you suggest here I believe is that you want to enforce your own perspective with the help of LLMs. I don't think this is a good idea based on the above. You would just create a negative feedback loop enhancing the errors in your thinking. Also, it would be uninteresting. AND it would still be biased, not neutral in any way.
0. There is nothing like neutral facts
1. Other's perspective is far more valuable than mimicking your own with an LLM, even if you think those people are utterly wrong and misguided
2. People are and always will be better at making sense and deliver insights than LLMs therefore it's more valuable and more interesting, regardless of agreement

2025-04-08 18:52:41 CEST

- reply

It could be:
1. Recipient's LN node doesn't issue a Zap receipt event
2. OR it is issued but it gets lost/deleted on the relay (less likely)
3. OR Yakihonne checking for the Zap receipt event incorrectly
I would say most likely the problem is 3.
And even if it's not Yakihonne, I would definitely apply a timeout on fetching the Zap receipt, like 10 seconds, then I would just alert the user that the payment might have failed

2025-04-07 21:25:59 CEST

- reply

Is this hyperdrive related?
If so ask Pablof7z about it, he had experience with it but said he eventually dropped it mentioning overcomplication / overengineering reasons.