Nostr notes by Five

The only question is whether we can find the solutions with the ...

2026-10-06T07:21:47Z

In reply to nevent1q…80em
_________________________

The only question is whether we can find the solutions with the right tradeoffs before falling back to politics completely.

Bitcoin brought adaptive proof of work based money, nostr gives us the simplest primitives for sovereign identity and independently verifiable data.

These protocols let us design freedom oriented, natural, human-scale systems.

Hard coordinaton problems in digital space should always fall ...

2026-10-06T07:14:42Z

Hard coordinaton problems in digital space should always fall back to a solution in meatspace, there will not be a time where we completely let machines decide everything for us I hope.

quoting
nevent1q…n5z7
The problem with append only state is that remember:
From the other partie's perspective who only sees your signed event, delegated signing is key rotation.

For your idea to work you must (as you mention) introduce an append only tracker of your key states.
This is the exact point where you introduce a strict ordering burden on Nostr verification since now everyone must take a roundtrip:
"Do I know this key? This could be xyz's subkey/delegated key so let's look up the original to verify the real identity" and this must be done each event.

And if you leak the subkey it's even worse, now you have to introduce even more extra roundtrips and edge cases where a client must look up the history of revocations with each and every event verification process.

So a delegation process producing a different signature will not work practically in my opinion.

The delegated signing process must produce the same signature as the original key.
This is what FROST solves. Your nsec is sharded and you define in the key ceremony what kind of quorum you will use.
Let's say 2/3. Now you keep one on a server, one on your phone and one just in cold storage (for now).
If the server or the phone is compromised you get the 3rd shard and never trust the compromised one again. These tools exist already you can experiment with them.

The burden / complexity is now on you instead of the whole network to make sure that the compromised shard is being handled (you cannot revoke it) but realistically you can drop it, and use the other 2 or even add further keys to the quorum, making it practically 2 of 4 etc.
Note that adapter signatures could be used differently but Frost has additional benefits.

AtProto (Bluesky) solves this by introducing a trusted so called PLC server that tracks key rotations. You cannot practically run your own equivalent because that's hardcoded into each client solving the consistency / roundtrip problem I described above. It's that theoretical thing that doesn't work in practice, and they acknowledge that.

All in all UX can go a long way so a co-signer FROST setup can be quite convenient to use with the right tooling, and services.

And if all breaks we always fall back to meatspace, there will never be a perfect solution, that's alright I think. Bitcoin can be hardforked even with overwhelming consensus.
Note that key rotation is essentially just that:
You want the whole world to overwhelmingly accept that the state of your identity changed. That is an oracle problem and Bitcoin handles it the same way:
Leaves it open.
That's why altcoins exist.
You fork an identity that's your alt identity. I don't have to accept but I cannot exclude others to accept it and enforce it practically.
The difference is that rotation of your identity will not affects global trade so it will be alright.

By the way you can create a sign in with google experience today ...

2026-10-01T15:22:18Z

In reply to nevent1q…5mz7
_________________________

By the way you can create a sign in with google experience today with frost fiatjaf had a demo I think.

You can run a bunker signer for your mom, or later when ppl have much at stake there will be professional co-signing services.

The problem with append only state is that remember: From the ...

2026-10-01T15:15:58Z

In reply to nevent1q…k3ju
_________________________

The problem with append only state is that remember:
From the other partie's perspective who only sees your signed event, delegated signing is key rotation.

For your idea to work you must (as you mention) introduce an append only tracker of your key states.
This is the exact point where you introduce a strict ordering burden on Nostr verification since now everyone must take a roundtrip:
"Do I know this key? This could be xyz's subkey/delegated key so let's look up the original to verify the real identity" and this must be done each event.

And if you leak the subkey it's even worse, now you have to introduce even more extra roundtrips and edge cases where a client must look up the history of revocations with each and every event verification process.

So a delegation process producing a different signature will not work practically in my opinion.

The delegated signing process must produce the same signature as the original key.
This is what FROST solves. Your nsec is sharded and you define in the key ceremony what kind of quorum you will use.
Let's say 2/3. Now you keep one on a server, one on your phone and one just in cold storage (for now).
If the server or the phone is compromised you get the 3rd shard and never trust the compromised one again. These tools exist already you can experiment with them.

The burden / complexity is now on you instead of the whole network to make sure that the compromised shard is being handled (you cannot revoke it) but realistically you can drop it, and use the other 2 or even add further keys to the quorum, making it practically 2 of 4 etc.
Note that adapter signatures could be used differently but Frost has additional benefits.

AtProto (Bluesky) solves this by introducing a trusted so called PLC server that tracks key rotations. You cannot practically run your own equivalent because that's hardcoded into each client solving the consistency / roundtrip problem I described above. It's that theoretical thing that doesn't work in practice, and they acknowledge that.

All in all UX can go a long way so a co-signer FROST setup can be quite convenient to use with the right tooling, and services.

And if all breaks we always fall back to meatspace, there will never be a perfect solution, that's alright I think. Bitcoin can be hardforked even with overwhelming consensus.
Note that key rotation is essentially just that:
You want the whole world to overwhelmingly accept that the state of your identity changed. That is an oracle problem and Bitcoin handles it the same way:
Leaves it open.
That's why altcoins exist.
You fork an identity that's your alt identity. I don't have to accept but I cannot exclude others to accept it and enforce it practically.
The difference is that rotation of your identity will not affects global trade so it will be alright.

This is cool! Can agents use Opal locally without the relay ...

2026-09-28T09:59:29Z

In reply to nevent1q…3q0f
_________________________

This is cool!
Can agents use Opal locally without the relay roundtrips?

I think the problems you pointed to are real so they already ...

2026-09-27T17:47:58Z

In reply to nevent1q…fsey
_________________________

I think the problems you pointed to are real so they already manifested. Perhaps not enough ppl realize yet.

I also say that a pragmatic optimism is warranted though.

So in a way yes, I am saying most problems will be solved. Not sure about the timeline and want to accelerate the solutions to problems I see more pressing, that's my part.

Yes the narrative has been misleading it's not ideal. However ...

2026-09-27T06:08:26Z

In reply to nevent1q…5uxy
_________________________

Yes the narrative has been misleading it's not ideal.

However with more overall bitcoin adoption, including adjacent tech, we will hit obvious walls if what you say is true:
- Big LN nodes failing / hacked due to too much complexity
- Adverse fee environment destroying LN UX for the nth time
- Backlashes from 99% kyc custodial wallet usage
- Just sheer fatigue and churn of developers and non-custodial users alike

If these will play out increasingly, the issues become obvious and the problems need to be addressed. To some extent Spark, Ark and even #Cashu came about for exactly these reasons.

I know it's very hard to be among the first adopters because we tend to be impatient for the tech to succeed (like nostr) and when we face the chasm to cross it can burn us out quickly.

Endurance and timing are most relevant in this situation.

You look at Lightning and especially how hard it is to run a node ...

2026-09-26T07:57:10Z

In reply to nevent1q…49j5
_________________________

You look at Lightning and especially how hard it is to run a node securely and economically and one can realize this is made for industrial grade batched bitcoin transactions.

But it does scale bitcoin in a way, it allows for institutions to cheaply send and receive and this benefit trickles down the value chain: A cheap LSP e.g.
It's like a checking account for tenth the cost of what it is today, and stronger exit guarantees.

However, to truly scale bitcoin to microtransactions, we might not be able to avoid custodians.

Hope ark and spark help this situation but I don't see them solving this problem as cleanly as people would like

So I guess you considered #Frost if you have been thinking about ...

2026-09-25T17:33:22Z

In reply to nevent1q…7jdy
_________________________

So I guess you considered #Frost if you have been thinking about this for a long time but you haven't mentioned it. Why?

Key rotation on the nsec level will hardly be a thing unless there's some cryptographic breakthrough because it would centralize the protocol, see PLC in atprotocol and such.
You basically must centralize key lineage tracking to a trusted party but that just doesn't go well in a distributed system.

Frost shard-based signing UX can be very stable and fairly revocable, it's just not yet spread so much.

Social rotation is the other way, it's been talked about many times. It is a viable alternative in a network like nostr, especially if communities get more popular.

The reason why there's not too much anxiety over this is just the fact that there's not yet enough demand I think for nostr in general.

We're building things out and if there's real pressure in the future from economically relevant users accruing, at some point it's gonna be figured out.

You mean @nprofile…u0w6

2026-09-19T13:28:34Z

In reply to nevent1q…rfpv
_________________________

You mean hodlbod (nprofile…u0w6)

Nostr event nevent1qqsqqq9ysjwwxlpucdmflnex0dzl0pys8xc2u7jguw0x9ay09dty4gqzyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqtafc0r

2026-09-17T12:37:30Z

Massive scale corrupts massively

> I think it is important to say specifically how pacing will ...

2026-09-12T18:32:28Z

> I think it is important to say specifically how pacing will allow us to make the AI development process safer.
---
Specifically, I hope to get hold of smart enough unrestricted AI hosted safely in my apartment. That constitutes safety for me.

https://darioamodei.com/post/we-must-pace-the-frontier

Didn't know so much wokism is left in Linux land: ...

2026-09-12T10:03:01Z

Didn't know so much wokism is left in Linux land:
https://stopomarchy.neocities.org/

It's only time that can show the true nature and benefits of ...

2026-09-11T13:41:12Z

In reply to nevent1q…mjpe
_________________________

It's only time that can show the true nature and benefits of Nostr.
Waiting for the masses is futile, we must go step by step, first a focused cypherpunk group then work our ways towards a broader audience.

That is why niche apps are more justified currently than anything else

I second this.

2026-09-09T20:21:50Z

In reply to nevent1q…ez38
_________________________

I second this.

My first idea would be around agent-identity, Omarchy people ...

2026-09-09T20:19:12Z

My first idea would be around agent-identity, Omarchy people appreciate AI and Nostr can is a good fit here

quoting
nevent1q…96ty
Regardless if you like it or not:

We should get Nostr into #Omarchy one way or another.
I am way too busy right now but want to contribute :

I am offering a 5.000.000 (5M) sats bounty for the first author of a meaningful nostr integration with Omarchy that is merged by a maintainer and shipped in the canonical release.

This is the way we should showcase the power of Nostr: Not with echo-chamber-ware but demonstrate value in the real world.

If you have good ideas to share with like-minded devs come chat in #BudaBit :
https://budabit.club

Share this to your nerdy friends!
#devstr

Regardless if you like it or not: We should get Nostr into ...

2026-09-09T16:55:00Z

Regardless if you like it or not:

We should get Nostr into #Omarchy one way or another.
I am way too busy right now but want to contribute :

I am offering a 5.000.000 (5M) sats bounty for the first author of a meaningful nostr integration with Omarchy that is merged by a maintainer and shipped in the canonical release.

This is the way we should showcase the power of Nostr: Not with echo-chamber-ware but demonstrate value in the real world.

If you have good ideas to share with like-minded devs come chat in #BudaBit :
https://budabit.club

Share this to your nerdy friends!
#devstr

Coldcard happened

2026-09-08T15:28:11Z

In reply to nevent1q…7dcq
_________________________

Coldcard happened

BudaBit is coming along nicely, will start more activities for ...

2026-08-31T17:36:23Z

BudaBit is coming along nicely, will start more activities for all the freedom tech devs out there!

If you want to set up your own community **on any relay** (not like nip29) with just a few clicks, take a look at how BudaBit communities work:

https://budabit.club/community-guide

In the future I will implement optional server side enforcement but I think it should be super easy to start a public moderated group.

Why are BudaBit groups unique?
- Technical focus (tight nostr-git integration)
- Fine-grained moderation enabled by content sections
- Community-first web of trust
- Curate Repos, Code Snippets and Smart widget extensions into your groups
- Run and recommend infrastructure as a group admin: Relay, blossom media, grasp server, ecash mint, email alert service, possibly more in the future
- Select your service providers based on your community memberships and community-first #wot

Join to learn more or talk about freedom tech:
https://budabit.club

Keep in mind that insurers will dictate your setup to a degree. ...

2026-08-01T07:05:08Z

In reply to nevent1q…qetn
_________________________

Keep in mind that insurers will dictate your setup to a degree. They won't just insure any scheme you figure out for yourself, or receive much worse terms.
Still could be worth it but it's a serious tradeoff, along with privacy implications.

Mostro.network is nostr-native. Haven't used yet

2026-06-14T16:56:40Z

In reply to nevent1q…gtra
_________________________

Mostro.network is nostr-native. Haven't used yet

Nostr event nevent1qqsqqq8xs5dv3yhftyp2r2yy7x4z6j3qw9ssut4qvsa7jsfsdjzswgszyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqf2kpc6

2026-06-09T12:28:48Z

https://keepandroidopen.org/

Love Zapstore and its recent emphasis on Communities! Didn't ...

2026-06-07T06:40:40Z

In reply to nevent1q…9v4p
_________________________

Love Zapstore and its recent emphasis on Communities!
Didn't know you accepted this role but makes perfect sense!

If you want to get inspired how to build communities on Nostr around open source take a look at https://budabit.club it's coming nicely together I think.

Funneling people into an engaging community is really important in my opinion but it needs good moderation and distributed content-curation.
I use the #communikey spec from Niel Liesmons (nprofile…4s8y) what's your angle? Curious!

Anyway wish you all the best! I hope Zapstore gets increasing traction.

#nevent1q…y3dm

2026-05-31T18:33:22Z

In reply to nevent1q…vjg6
_________________________

quoting nevent1q…y3dm
Shipping software or seeking interesting technical conversations rather than a doomsrcoll experience?

Now is the time to join or create your own moderated sovereign community, just a few clicks:
https://budabit.org
#grownostr #devstr #communikeys

cc GammaMarkets (nprofile…5s7u) TollGate (nprofile…8mrq) fips (nprofile…nsnk) fiatjaf (nprofile…cy6q)

We have been polishing community UX for a while now, and I can say #BudaBit is already a fully usable community experience with nip34 #gitvianostr deeply integrated.

We'll keep being laser-focused on high-signal easy-to-moderate technical communities so the future won't be locked into walled gardens like github.

Keep shipping.

Shipping software or seeking interesting technical conversations ...

2026-05-31T18:28:07Z

Shipping software or seeking interesting technical conversations rather than a doomsrcoll experience?

Now is the time to join or create your own moderated sovereign community, just a few clicks:
https://budabit.org
#grownostr #devstr #communikeys

cc GammaMarkets (nprofile…5s7u) TollGate (nprofile…8mrq) fips (nprofile…nsnk) fiatjaf (nprofile…cy6q)

We have been polishing community UX for a while now, and I can say #BudaBit is already a fully usable community experience with nip34 #gitvianostr deeply integrated.

We'll keep being laser-focused on high-signal easy-to-moderate technical communities so the future won't be locked into walled gardens like github.

Keep shipping.

#nevent1q…fkpc

2026-05-19T09:39:07Z

In reply to nevent1q…tnqg
_________________________

quoting nevent1q…fkpc
I like nutzaps because:
1. Better verification assuming the mint is widely trusted - > reputation builds up
2. Still some degree of plausible deniability: You could say ecash doesn't equal real money, it's an IOU (not a lawyer)
3. No peel-chain type of privacy leak like with Bitcoin
4. More stable from a developer standpoint because there is no third party involved in the publishing of the zap receipt like with LN zaps
5. Funny name

LN zaps:
- Less verifiable probably due to random LN nodes posting the zap receipt
- Worse stability of receipt structure : it is third party publishing with whatever tags they want. You can just propose the event as a client app
- Better deniability due to the above

Onchain:
- Very strong verifiability
- Privacy ramifications most users can't calculate beforehand
- Future fees and waiting times if bitcoin succeeds

Most use a custodian LN wallet (99.9%) anyway and there's really no way to abstract away the privacy consequences of onchain so ecash is my winner.
nevent1q…8l9f

I like nutzaps because: 1. Better verification assuming the mint ...

2026-05-18T06:16:51Z

I like nutzaps because:
1. Better verification assuming the mint is widely trusted - > reputation builds up
2. Still some degree of plausible deniability: You could say ecash doesn't equal real money, it's an IOU (not a lawyer)
3. No peel-chain type of privacy leak like with Bitcoin
4. More stable from a developer standpoint because there is no third party involved in the publishing of the zap receipt like with LN zaps
5. Funny name

LN zaps:
- Less verifiable probably due to random LN nodes posting the zap receipt
- Worse stability of receipt structure : it is third party publishing with whatever tags they want. You can just propose the event as a client app
- Better deniability due to the above

Onchain:
- Very strong verifiability
- Privacy ramifications most users can't calculate beforehand
- Future fees and waiting times if bitcoin succeeds

Most use a custodian LN wallet (99.9%) anyway and there's really no way to abstract away the privacy consequences of onchain so ecash is my winner.

quoting
nevent1q…8l9f
You know nostr is just reusing one pubkey for all posts, right? Then you use that key, that knows everything about you, to send zaps which include public keys of everyone involved, right? It's all public on Nostr.

"Marxists are unteachable. This is so difficult to eradicate, ...

2026-04-15T17:55:42Z

"Marxists are unteachable. This is so difficult to eradicate, as you know with my book I've tried to eradicate it for 50 years."
- Karl Popper

Somehow we see this coming back to bite us again and again. Theft and coercion fueled by envy, camouflaged by the "protection" of "underprivileged".

The central planners will try to crack down once more, with terrible consequences. The signs are there.

Working on unstoppable speech, communities, and markets for me is not optional. If I want a future for myself and my family I must carry on and do my best to ship the tools for freedom.

This is what keeps me going the most.

I'm a daily active user of nostr. Just not on the social ...

2026-03-19T06:39:11Z

I'm a daily active user of nostr.
Just not on the social media front.

I speak to my AI coding agent inside BudaBit (npub1p28…hpp3) via DMs.

Also doing other dev work in BudaBit that 99% replaced GitHub in my workflow. Organizing BudaBit Demo Day events on Hivetalk (npub1z0l…8ldk)

Occasionally managing apps with Zapstore (npub10r8…t2p8), watching a stream on Zapstream or paying my contributors in sats on SatShoot (npub1uvj…d955). Tipping sponsored freelancers with nostr-native ecash. Shilling TollGate (npub1zzt…ljrv) every now and then on my meetups.

Antennapod is still my daily driver rather than fountain, simply the best in this category and open source. Hope I can switch one day though.

Ppl trying to measure nostr usage with social media as a proxy is understandable but the whole picture is very far from what you can extract from such a narrow view of a diverse ecosystem.

Patience pays off. Gradually then suddenly.

SatShoot is going to implement nip85 soon. I want to grab kind ...

2026-02-08T17:46:19Z

In reply to nevent1q…lk83
_________________________

SatShoot is going to implement nip85 soon. I want to grab kind 10040 TA preference of a user and everything would be straightforward if ppl declare their providers.

Will see how the trust scores and metrics can be nicely fit into the ux.

This will decouple SatShoot from the wot service to a degree bc users seelect their own providers external to SatShoot.

How #Vertex is currently integrated in #SatShoot : - Search bar ...

2026-02-07T18:06:43Z

How #Vertex is currently integrated in #SatShoot :
- Search bar that filters page content can be used to search profiles with Vertex
- Brand new pubkeys or pubkeys without vertex credits are sent to buy credits to vertex pricing page:

- My account has by default some credit allowance and can use profile search as well as analyze profiles with Vertex: verifyReputation method:

This is done with DVM-based query. It serves not to replace client-side #wot but to complement it. You want to know more about an npub you potentially want to make a deal with, you can use this to get to know better. Result is cached.

Then you might include this person to your web of trust by following and making a deal. That is how you expand your network and thus grow the business network of Nostr.

Check it out on https://satshoot.com

#freelance #grownostr

Additional confirmation that you got them right. Could be ...

2026-02-07T17:10:23Z

In reply to nevent1q…hp30
_________________________

Additional confirmation that you got them right.
Could be optional but since I don't show this ever again, better be safe than sorry. Copy-paste works btw for the whole mnemonic sentence

#Ecash fans alert! We finally shipped NUT13 in SatShoot ecash ...

2026-02-07T10:50:32Z

#Ecash fans alert!
We finally shipped NUT13 in SatShoot ecash wallet!

What this means: This is the first nostr-based ecash wallet that is backed up by a seed as well.

You are double-protected: ecash is saved on relays, encrypted to your nsec, and additionally you have the seed backup.

Why big deal?
Ecash wallets on nostr have been notoriously unreliable, mostly due to relays and all sorts of state bugs. It is not easy to implement a stateful wallet and if the app loses state (i.e. your money) somehow, you were out of luck.
Your seed allows you to recover from state bugs or relay sync issues.

But at the end of the day your nsec serves as a backup if you lose your seed. That's the neat part.

Try it on https://satshoot.com

CAVEATS:
1. Due to an Amber bug the wallet will not work with amber remote signer. Only try with local key or browser extension login
2. Still experimental! Please don't use it for high amounts
3. Feedback welcome! You can try to deposit on a seed and recover from cashu.me or the other way round! Report bugs and such.

Bonus for the #wot lovers:
Now you can choose a mint based on recommendations from your nostr web of trust! (As shown in the video)

Ecash has two hard problems nostr can help with:
1. Discovery and reputation of mints: From explicit mint recommendations AND implicit nutzap info (which mints ppl want their nutzaps to be received) we can show the user mint usage from his own trusted network. This helps selecting mints for newbies or switch if mints get compromised.

2. Wallet portability: Thanks to nostr relays, your ecash should be synced to all devices. All you need is a nip60-capable nostr app.

Thanks to rodant (nprofile…67u0) for the implementation of NUT13 on Nostr!
cc calle (nprofile…xnfk)

You can use any platform you want, even mirror between them but ...

2026-01-16T21:09:09Z

In reply to nevent1q…50gz
_________________________

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

The tools for this either exist or are easy to build. Relays are ...

2026-01-16T20:54:38Z

In reply to nevent1q…g82q
_________________________

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.

Moderation tools exist for nostr relays already. You can ...

2026-01-16T20:29:35Z

In reply to nevent1q…jqgp
_________________________

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 nosfabrica (nprofile…lh4w) team

Yes, but the #grasp spec can introduce some proactive sync if ...

2026-01-16T20:24:35Z

In reply to nevent1q…hsy5
_________________________

Yes, but the #grasp spec can introduce some proactive sync if enabled.

With the benefit of nostr based auth

For the source code part git is already decentralized enough, it ...

2026-01-16T20:22:11Z

In reply to nevent1q…dh0h
_________________________

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.

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

2026-01-16T19:31:46Z

In reply to nevent1q…nfet
_________________________

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

@nprofile…y7h4 saw yall takin a look at decentralized git ...

2026-01-16T19:30:47Z

matt (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 DanConwayDev (nprofile…hk4d) fiatjaf (nprofile…xuyp)

Hey there, the link on your official website seems to be broken: ...

2026-01-08T15:02:00Z

In reply to nevent1q…vp6n
_________________________

Hey there, the link on your official website seems to be broken:
https://zap.stream/nosfabrica
Gave me:

Very cool project, check it out! Home Mining X Nostr zaps ...

2026-01-03T06:59:52Z

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

quoting
nevent1q…fh8p
Zaps are implemented in Zappool, from now on payouts are done as Zaps by default!
With this, Zappool is feature complete, so I declared it v1.0 live version.

Zaps are shown in most Nostr clients; e.g. https://www.fatzaps.com/npub17qt0gf99uxe3n3aa8nj93hspe0x3vfn7wwmv42adfc96y8g8ngcqpakg7l (The zaps are to npubs, not a post, that's why not all clients show them).

If you don't want the Zap, only the lightning payment, you can prefix your npub by "NOLN:" (nostr lightning),
e.g. "NOLN:npub17qt0gf99uxe3n3aa8nj93hspe0x3vfn7wwmv42adfc96y8g8ngcqpakg7l".
See https://zappool.org/faq.html#can-i-get-paid-to-my-nostr-account-without-the-zap-event .

Sometimes I sit back and think about how wonderful is all the tech on which Zappool is built upon:

A crazy guy had the idea to reverse-engineer a mining chip, and build an open source miner hardware, just for fun. Joined by another crazy guy (across the ocean) they did it: Bitaxe was born, now produced by many companies by hundreds of thousands.

Another crazy crazy guy created a mining pool that is permissionless: Ocean pool was born, now with more than 20 exahash of power.

And there is the whole Nostr world, and the whole Lightning ecosystem.

And all based on bitcoin.

Whose genesis block was created exactly 17 years ago (well, tomorrow).

Am an operator myself and love how nostr is gradually eating the ...

2025-12-30T12:41:40Z

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

quoting
nevent1q…4s36
The folks at TollGate (nprofile…94rw) are innovating non-stop!
They already signed up for #BudaBitDemoDay !
Come check it out on https://budabit.club !
Got your own project? Apply today!

What if the relay has an outdated record? In a multiple-relay ...

2025-12-28T08:40:44Z

In reply to nevent1q…q7dc
_________________________

What if the relay has an outdated record? In a multiple-relay scenario the client might have the latest state synchronized from multiple relays, but the relay that has outdated info will not allow "force push".

Otherwise can you explain how a nip60 wallet get rekt exactly from a race condition? Token events are not replaceable.

I found these scenarios to be problematic:
- relays deleting token events
- app not being able to publish new token events (signing and publishing are async), especially nutzaps
- nutzaps getting lost on relays
- spent tokens disrupting user-experience (unexpected change in balance)

So state management is an issue with Nostr wallets, and precisely that is why SatShoot went the NUT13 (and perhaps later NUT14) way - with the seed based wallets you get double protection:
1. Nostr stores your state on relays so even if you lose the seed you can swap to a different one. Mitigates losing local state as well

2. The NUT13 seed protects from relays deleting, censoring or losing your nsec - an additional hedge on nostr state. Like a recovery code to an account. rodant (nprofile…twvn) extended the nip60 spec so the NUT13 counter can also be synchronized to nostr.

NUT14 is important because it makes in-flight payment state atomic. If the nutzap is not redeemed the money is not lost.

Sadly, I haven't found well-maintained apps with nip60-61. A few apps use it with outdated specs and none of them work with the latest spec, using both nip60 and 61, other than #SatShoot

Are you already planning your next moves as a builder in freedom ...

2025-12-27T09:41:22Z

Are you already planning your next moves as a builder in freedom tech?
Tell us about it!
The best way to do it is applying with your demo on https://budabit.club !

When I found Bitcoin, I was mostly alone with my thoughts and my ...

2025-12-22T06:18:37Z

When I found Bitcoin, I was mostly alone with my thoughts and my plans to reorient my life around PoW and decentralization.

I've always been fond of doing things in a community though, so when I learned there were no active meetups in Hungary I started one.

Now that's officially part of the "twentyone" family of meetups:
https://portal.huszonegy.world/hu/meetup/budabit-cypherpunk-meetup .
Thanks for the awesome website El Presidento Ben (nprofile…9lpv) !

But to me who is working on freedom tech full time, a monthly meetup still wasn't enough:
I started #BudaBit for all builders and aspiring devs in freedom tech to connect, share and collaborate like never before.
It is an attempt to transcend the platform model for open-source development, and bring it to the next level: Community driven development, powered by Nostr.

BudaBit Demo Day is part of that plan:
What I've found on my journey is that feedback is essential to the process, and it is not easy to find people who get it and can provide valuable feedback.

If you're a builder in freedom tech, this event is for you! Go to https://budabit.club for details!

📢 ANNOUNCING BUDABIT DEMO DAY Have you got something exciting ...

2025-12-21T13:58:49Z

📢 ANNOUNCING BUDABIT DEMO DAY

Have you got something exciting cooking in Freedom tech?
It's time show it off to an audience that truly cares!

Early next year I am launching BudaBit Demo Day - a regular event series focused on Builders in Freedom tech! 🤙

Want to get honest feedback on your project from other builders in the space?

This is your chance then!
Go to https://budabit.club for details, and **apply with your demo today!**

Spoiler alert!
Everyone’s invited but only the best are chosen! 🏅

PS: If you got friends in the space, please share!
I created BudaBit for all freedom tech builders to find inspiration, get feedback and supercharge their work with the power of Nostr!

Haven't got a demo to share just yet? You are still invited to the party! Come, get inspired and provide constructive feedback to the presenters!

#budabit #gitvianostr #ngit #community

Seems like a decent client but where's the cashu wallet? Is ...

2025-12-14T18:36:00Z

In reply to nevent1q…rtx9
_________________________

Seems like a decent client but where's the cashu wallet?

Is this feature not released yet?

Of course you want to present your best case to get back a ...

2025-12-14T08:09:55Z

In reply to nevent1q…lrr3
_________________________

Of course you want to present your best case to get back a valuable account. There's nothing surprising here.

The problem is when people start accepting bullshit harmful narratives like "There's no smoke without fire" or "He really shouldn't have pissed them off now he ruffled too many feathers".

... and get back to business as usual. Stories like this point to important truths about the current reality: We are controlled and this could happen to anyone, REGARDLESS of what he did.

Like that idea. More power to you! The more options the better, ...

2025-12-13T19:28:19Z

In reply to nevent1q…3sz6
_________________________

Like that idea.
More power to you!

The more options the better, and I think in the long run if any of the clients are successful they will have some kind of native app.

The web has its limits and is really bloated indeed.

For me it's just a problem above ca 10k users. It's cheaper, faster and easier distribution on the web today.

I can relate to that btw. But here's the thing: Once I ...

2025-12-13T19:17:07Z

In reply to nevent1q…f5ze
_________________________

I can relate to that btw.

But here's the thing:
Once I learned how easy it is to censor native app distribution I realized I won't put my efforts into a project to then have a petty bureaucrat at google or apple gatekeep my app.

But I guess now I will have to properly redirect the .org :)

2025-12-13T19:13:51Z

In reply to nevent1q…83lv
_________________________

But I guess now I will have to properly redirect the .org :)

budabit.club

2025-12-13T19:12:46Z

In reply to nevent1q…007h
_________________________

budabit.club

#nevent1q…phza

2025-12-13T08:25:12Z

In reply to naddr1qp…5gxh
_________________________

quoting nevent1q…phza
merryoscar (nprofile…xytq) fountain subs are buggy.
You say sub from $5 (5.530 sats) which is then converted to $55.30 incorrectly and that amount is calculated in sats (61.162) .

This is a serious bug fix it soon.

Amethyst 0.94.3

2025-12-13T08:08:01Z

In reply to nevent1q…9yvs
_________________________

Amethyst 0.94.3

@nprofile…xytq fountain subs are buggy. You say sub from $5 ...

2025-12-13T08:02:12Z

merryoscar (nprofile…xytq) fountain subs are buggy.
You say sub from $5 (5.530 sats) which is then converted to $55.30 incorrectly and that amount is calculated in sats (61.162) .

This is a serious bug fix it soon.

Thanks I'll check! What about Trex? Is that working for you?

2025-12-11T16:18:32Z

In reply to nevent1q…wj0x
_________________________

Thanks I'll check!

What about Trex? Is that working for you?

@nprofile…nggv Trex stopped working, cannot browse events on my ...

2025-12-11T07:19:47Z

cloud fodder (nprofile…nggv) Trex stopped working, cannot browse events on my relay.
It's not showing any events when I put in a specific kind that must exist (eg kind9 as chat msg). Tried desktop and mobile, neither works.

Otherwise curious about this issue as well:
Can't auth to my relay with nak, but only when I want to send events.
Returns "Failed... you must auth"

I gave it the auth flag and otherwise when I run "nak req ..." it works.
Only problem is when I want to post.

Other relays also auth alright (e.g. filter.nostr.wine)

Appreciate your help.

Due to the nak problem + trex not showing I cannot delete any events from my relay.

Today I started to implement a new #WoT UX for #SatShoot . ...

2025-12-08T17:06:01Z

Today I started to implement a new #WoT UX for #SatShoot .

Client-side Web of Trust is already working, taking extended social follows, mutes and reports into account.
New users are bootstrapped with SatShoot account follow network (can be switched off in settings)

Plan for improvements:
1. Implement Mutes as blocklists. Network (ppl you follow) mutes can remove from WoT but user-mutes (kind 10k) will hide blacklisted ppl from Services and Jobs feed.
You can still land on a profile page or service/job landing page of a blocked user avatar will be shown as blocked. DMs will be blocked from these ppl and there's no way to allow them in Reputation calculation. Only affects visibility

2. You will be able to show/hide ppl outside WoT in Job/Service feed

3. I will implement #Vertex analysis in Profile pages. I will query top 5 reputable follows (personalized). I will make this feature paid (thinking 100 sats / query) but Vertex is not yet able to handle ecash or LN payments easily so I will get some credits myself.
I'll cache the result so it will be reusable. Will show the user if he follows any of those reputable followers of the analyzed pubkey.
I think of this as sort of a fallback or extra info for the user to be able to trust more and eventually follow people in freelance context (kind30k) which is explicit trust in SatShoot.

Later community memberlists of uswr can be added as well, when they come alive.

Plan to demo this in the #wotathon later.

Thoughts?

#devstr

That's right self-interest beats appealing to altruism. The ...

2025-12-07T14:13:48Z

In reply to nevent1q…mxaz
_________________________

That's right self-interest beats appealing to altruism.
The questions are:
1. What kind of perks are the best for a certain audience?
2. How to communicate those to the user?
Both are enormously important.
And as shawn (nprofile…h069) points out: we don't need to exclusively rely on #v4v .

It's always getting into those important details that shines light on a specific use-case. There's this generic thing called "creator economy".
We inherited this awful term because mass products like FB, Insta, TikTok, and others like to, well, think about their users in masses rather than niche cohorts of people.

To make this clear:
E.g. in freelance ( #satshoot ) I let the freelancer set up the pledged percentage per deal, importantly *before* being accepted by a client.
I also let the freelancer set his own sponsored npub to split the pledged percentage between the app and a selected person as he likes.
Overall pledged sats are conspicuous in profiles.
I believe this model is fine-tuned to my use-case, and it can get pretty far if freelance on Nostr takes off.

This however doesn't mean I couldn't offer extra optional services: the most lucrative to me seems recommendations. If the market is liquid enough it's not feasible to crawl a big network on the client side and calculate the best counterparties, so this could be offered as a premium for someone who cares enough to pay.

That said, a musician for example needs something very different. The design space is infinite.
The real technical hurdles have been demolished with bitcoin and nostr. This was also pointed out in the pod.

Now all that's left is to build the right product for the right people.

Both APIs you mention live off donations. This is not really ...

2025-12-07T09:43:38Z

In reply to nevent1q…27ce
_________________________

Both APIs you mention live off donations. This is not really feasible for the whole internet.

Furthermore, they still apply rate limiting and such to not be abused. What if I want to run a service that puts heavy load on the that api but am ready to pay for it?
IP based rate limiting is a primitive technique compared to what Nostr offers.

If you want curated data sustainably you will need authentication and you are better off with a paid service beyond a threshold for sure.

If on the other hand some successful service goes rogue you will have much better guarantees to fork that service and jailbreak the data, if it uses signed and standardized Nostr events.

Otherwise your left with unverifiable data that only makes sense in a proprietary format that no one else uses.

The primary issue in my mind is that the api-s don't follow ...

2025-12-07T06:40:03Z

In reply to nevent1q…p9hk
_________________________

The primary issue in my mind is that the api-s don't follow one well-defined standard, like signed Nostr events queried with filters.

This way you don't have to keep rewriting interfaces, and all data is verfiable.

The "closed" part is tricky: Even with wide-spread Nostr adoption I don't think that we would have completely free access to data.

Data is precious and people will protect it with digital fences, even if everything is signed and standardized.

But to the degree everything is interoperable and verifiable, we are in a very good place.

Even small backups can help in a major way. Real censorship becomes too costly in practice even for a large player.

It will result in more competition and therefore more openness as well.

Some clients don't render markdown in kind1, on Amethyst it ...

2025-12-06T19:07:06Z

In reply to nevent1q…jaqe
_________________________

Some clients don't render markdown in kind1, on Amethyst it looks okay.

But yeah, I checked on jumble, primal, yakihonne and perhaps others look bad too.

As to BudaBit, I intend to improve radically on all fronts, ...

2025-12-06T08:41:08Z

In reply to nevent1q…mpg4
_________________________

As to BudaBit, I intend to improve radically on all fronts, mobile view is constantly being worked, as well as other things.

You have any specific suggestions?

I can pay for sizeable PRs

1st step: Nostrize it. See [Gitworkshop](https://gitworkshop.dev) ...

2025-12-06T06:39:53Z

In reply to nevent1q…tyj7
_________________________

1st step:
Nostrize it.
See [Gitworkshop](https://gitworkshop.dev)
And
[BudaBit](https://budabit.club)

These utilize nip34 to take issues, PRs and discussions on Nostr and makes all repo state (even branches and code) platform-independent.

You can even install [nostr-git extension](https://chromewebstore.google.com/detail/nostr-github-integration/fagibbjlnnmfcgogkobglpcgpcllcjek) in chrome that you can use to nostrize a repo directly from GitHub.

We're winning.

I guess this has something to do with why people are sleeping on ...

2025-12-05T16:14:18Z

In reply to nevent1q…x7p7
_________________________

I guess this has something to do with why people are sleeping on groups.
And nostr overall

... and most job opportunities can only be accessed on a ...

2025-12-05T06:35:55Z

In reply to nevent1q…hy4h
_________________________

... and most job opportunities can only be accessed on a permissioned platform.
Reputation and business network is kept hostage. Nostr can solve that.

That's why I built [SatShoot](https://satshoot.com) .

It aims to create a platformless job market.

The better question is: How do we obsolete them? They're just ...

2025-12-05T06:18:26Z

In reply to nevent1q…j9zm
_________________________

The better question is:
How do we obsolete them?

They're just a shitty corp with a bad product.

Me too. Beautiful. One of my favorites

2025-12-05T06:16:20Z

In reply to nevent1q…vjyd
_________________________

Me too. Beautiful. One of my favorites

I would try your app for a gig but still can't figure out how ...

2025-12-04T08:15:19Z

In reply to nevent1q…wltm
_________________________

I would try your app for a gig but still can't figure out how to post a job on mobile

Thanks this will come handy for testing out grasp features in ...

2025-12-02T20:08:31Z

In reply to nevent1q…d5mk
_________________________

Thanks this will come handy for testing out grasp features in BudaBit.

Similar here, I just think replacing all of this and LinkedIn and ...

2025-12-02T19:58:54Z

In reply to nevent1q…7dzu
_________________________

Similar here, I just think replacing all of this and LinkedIn and GitHub is achievable by well-designed communities with easy deployment and a credible exit.

Most of the real value is trapped in fiat marketplaces and platforms of collaboration (especially around software).

Unstoppable reputation and authentic connections in interoperable high-trust and high-signal private groups is the new internet in my book.

Nobody really knows what quantum is really about and if it's ...

2025-11-30T08:19:18Z

In reply to nevent1q…hy20
_________________________

Nobody really knows what quantum is really about and if it's feasible at all.
At this stage it is nothing more than vacuous promises and shitcoin-style fear-mongering.

I suggest you look deeper than superficial FUD before making such claims.

You can try posting your service on ...

2025-11-30T08:11:29Z

In reply to nevent1q…gp5z
_________________________

You can try posting your service on [SatShoot](https://satshoot.com/post-service/) , a freelance app I built on Nostr.

No middle man, no forced fees.

Someone might jump on it, but you'll need to promote it, markets are not yet so liquid in freelancing (and other areas on Nostr)

#Ecash bears will have a hard time explaining why self-custody ...

2025-11-28T16:49:40Z

#Ecash bears will have a hard time explaining why self-custody Lightning fees are skyrocketing when Bitcoin adoption hits new levels.
...
Or why we still won't have a single self-custodial LN wallet that competes on UX with fiat wallets.

Think in spectrum rather than religious dogma. Black and white.

We need multiple solutions with all kinds of different tradeoffs for a gamut of use-cases.

Do you think #Zeus wallet adopting ecash was a simple decision? Do you think they don't care about Self-Custody?

They did what reasonable people do: act in a careful and smart way to meet people where they are.

It's always great to clash and test the different approaches ...

2025-11-28T08:03:40Z

In reply to nevent1q…cter
_________________________

It's always great to clash and test the different approaches to decentralization, and Cory has valuable thoughts.

I am biased towards action that builds an alternative rather than deconstruction, or trying to appeal to corrupted and morally bankrupt governments. He even said AT&T was broken up because some higher ups wanted it, not necessarily because of any political activism from below. It's an unreliable path, leaving freedom to the whims of people.

The new foundation that will bring undeniable results starts with freedom tech, because nothing else gives us real guarantees of a credible exit.

Written law can be there as guidance but has been superseded by permissionless protocols and cryptographic guarantees overall.

Just like speech was obsoleted by writing.

Good idea thanks!

2025-11-27T14:59:49Z

In reply to nevent1q…sqmx
_________________________

Good idea thanks!

Full Grasp support coming to BudaBit soon, the primitives are ...

2025-11-27T14:20:09Z

In reply to nevent1q…rszs
_________________________

Full Grasp support coming to BudaBit soon, the primitives are already implemented.

1. What we struggled with is the creation flow where we first post the repo announcement then the newly created git repo, but that must be done with an arbitrary sleep(X ms) wait time so that's not really ideal.

You guys have ideas to improve this flow?

2. I think it this was discussed before but want to get a fresh opinion of yall: Unified grasp api for file browsing and perhaps diffs and really data-heavy ops? Cloning repos via git smart http can still be a fallback but this would benefit performance a lot. Blossom has an api as well so I guess this would make sense, especially in a browser context.

fiatjaf (nprofile…xuyp) DanConwayDev (nprofile…s74j)

In my demo of BudaBit in #Bitfest I was asked if I was after the ...

2025-11-25T11:10:38Z

In my demo of BudaBit in #Bitfest I was asked if I was after the 10BTC bounty originally promised by Jack Dorsey to replace GitHub.

My answer has always been:
I really don't care about bounties as primary incentives to build anything in freedom tech.
I like when people donate to worthy projects but that motivation alone gets nowhere.

I build #SatShoot and #BudaBit for my own goals: Making code collaboration and digital work platformless and social.

I put my own sats and time in my projects and will see how far that goes. If people find it useful enough they will contribute in ways they can, money or otherwise. I already received a lot of support from many people in the space which I am really grateful for.

But receiving charity support is not my goal.

Keep the Services coming! We build the the freedom economy, step ...

2025-11-25T09:55:26Z

Keep the Services coming!
We build the the freedom economy, step by step.

quoting
nevent1q…df2a

Check out this service I'm offering on Satshoot! ⚡

## Creative Writer for Hire!

Do you have an idea for an article or blog post?

Do you need content for your website?

Let me help you get your project done! I will create for you a composition of up to 600 words that meets and exceeds your needs.

Reach out, or place an order here:

https://satshoot.com/naddr1qvzqqqrll5pzpyt202m5u853wpdg9822mw0l6pv86s83ahc7r5v64cm2x52xhwp7qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqp7smjv4shg6tkv5k4wunfw3jhyttxdaez6jrfwfjj6amfw3kxcdc0g9tu0

#satshoot #nostrservice #freelance #writing #blog #editing #poet #article

... and of course let me know how I can improve #SatShoot and #freelance on nostr!

Thanks for an awesome conf! Glad I could present #SatShoot and ...

2025-11-24T22:26:12Z

In reply to nevent1q…k86h
_________________________

Thanks for an awesome conf!
Glad I could present #SatShoot and #BudaBit !
Freedom tech is stronger than ever!
#bitfest

You should try to run your own private nostr community that you ...

2025-11-24T16:15:54Z

In reply to nevent1q…47r4
_________________________

You should try to run your own private nostr community that you own and your voice cannot be falsified, reputation lasts, and is verfiable.

You would be able to channel your audience into a sovereign group where you talk directly to your them, and you can customizeto your needs.

For projects like yours shadowbans and censorship is inevitable. You need a place you own and makes your noble efforts unstoppable.

I recommend looking at #Flotilla ( [start here](https://flotilla.social) ).

It has a lot of the features you expect from a Discord community, even more in some aspects.
E.g. it has Zap Goals which raises awareness and can help with funding.

#BudaBit ([link to demo comm.](https://budabit.club) , [link to repo](https://github.com/Pleb5/flotilla-budabit) ) is a fork of that, especially for developer communities that strives to make code collaboration platform-independent and a social effort at the same time.

hodlbod (nprofile…dgdk)

https://i.nostr.build/oFy53ZgdLQUSezwq.jpg

2025-11-21T20:44:17Z

In reply to nevent1q…5j5p
_________________________

BudaBit is very close to a fully usable git experience. I'll ...

2025-11-19T06:17:36Z

In reply to nevent1q…dcuf
_________________________

BudaBit is very close to a fully usable git experience.

I'll deploy latest and post a demo about it tomorrow.

Will also do a workshop in Bitfest conf Manchester Sunday afternoon.

#Ecash people fret the critics too much. Just remember: Attention ...

2025-11-08T18:48:16Z

#Ecash people fret the critics too much.

Just remember: Attention doesn't have polarity.

Successful projects capitalize on this fact. Bitcoin too.

NUT13 seeds and NUT14 HTLCs make #Cashu #ecash safe. Nostr ...

2025-11-06T08:24:37Z

NUT13 seeds and NUT14 HTLCs make #Cashu #ecash safe. Nostr NIP60-61 make ecash ubiquitous and allow zaps to build verifiable Reputation.

They both will soon be available in [SatShoot](https://satshoot.com) and any Nostr web app using NDK:

quoting
naddr1qq…nykt

Introduction

The e-Cash Cashu protocol has gained remarkable momentum in recent years and officially entered the Nostr ecosystem with the introduction of NIP-60. This specification provides the foundation for Cashu wallets that store their state on the Nostr network and is currently implemented (or under development) in several ecosystem libraries, including nostr-dev-kit (NDK), rust-nostr, and Dart NDK. Several applications have built Cashu wallets using these libraries as well and some of them are quite usable, at least for first experimentation with this novel way of Bitcoin wallets.

The prospect is compelling: a Nostr identity is sufficient to create a native wallet—it's just an event away. Once created, the wallet, balance, and transaction history are linked to your Nostr identity, enabling users to theoretically switch between applications while maintaining wallet continuity. However, this vision remains largely unrealized due to limited ecosystem adoption and incomplete feature support, particularly for Nostr's core zap (nutzap) functionality.

Very likely one reason for the restricted usage of Nostr Cashu wallets is the inherent lack of strong consistency in Nostr as a decentralized network, it does not feel like a safe place to store your Bitcoin. But what if you were able to restore your funds any time in case of loss?

NUT-13 (Deterministic Wallets) to the Rescue

NUT-13 defines the deterministic wallet standard within the Cashu protocol specification. It specifies how wallets can deterministically derive proofs from mints. The specification lends the BIP-39 from Bitcoin for that purpose and defines the derivation path scheme for Cashu wallets, similar to BIP-32. The technical details about how this works can be read in the specifications. For our purposes, it is sufficient to understand that through this mechanism, a wallet can restore its balance with mint collaboration—a core assumption in Cashu. If anything goes wrong, 12 seed words are sufficient to recover access to all funds, a feature that could also be beneficial in the Nostr context.

Bringing NUT-13 to Nostr

As mentioned in the above section, the user would need to keep his seed words at a safe place like with any Bitcoin wallet and would be able to restore the funds in case of loss. For everyday Nostr usage, asking users for seed words, or some other data, on every app or device switch would be impractical. This is precisely what NIP-60 is supposed addresses. Moreover, deterministic wallets must maintain state by tracking the counter value for the next derivation path step, enabling generation of new Cashu proofs from mints.

This proposal extends NIP-60 defining how the wallet seed (generated from the seed words) and the counter state for every mint and key set should be stored in a Nostr event. In NIP-60, kind 17375 stores both a private key (used to lock tokens for exclusive spending) and the user's selected mints. To maintain backward compatibility and reduce the risk of affecting existing clients, we introduce a new event kind rather than modifying the existing 17375 schema: We decided not to alter the schema of this event and instead define a new kind (deterministic wallet event):
{
    "kind": 17376,
    "content": nip44_encrypt({
        "bip39seed": "hexkey",
        "counters": {
            "<normalized-mint1-url>|<keyset=keyset-id-1>": "<counter-1>",
            "<normalized-mint1-url>|<keyset=keyset-id-2>": "<counter-2>",
            "<normalized-mint2-url>|<keyset=keyset-id-3>": "<counter-3>",
        }
    }),
    "tags": [],
    ...
}
As in the kind 17375, the event content is encrypted according to NIP-44. In the encrypted content the relevant information get stored, the bip39seed field contains the 32-byte seed in hexadecimal format. Upon initialization, the counters map is empty ({}). The map keys are formed by combining a normalized, unique mint URL with its keyset ID.

We identify several advantages in this approach. It is good for backward compatibility with clients already using this NIP. It is possible to extend kind 17375 for our purposes in a backward-compatible manner, but with it we would introduce risk to affect existing clients depending on how they are implemented. A new kind reflects also better the separation of concerns, updates to 17376 can not affect the wallet information, reducing risks. Note that wallet mints are now distributed across two events, improving resilience and providing this information for potential wallet restore operations.

Wallet implementations must fetch both kind 17375 and the new kind 17376 to initialize their state properly. The Cashu NUT-13 specifies how to proceed to obtain deterministic proofs from the corresponding mint and how to implement the restore process. The counter state for every mint and key set ID must be kept up to date by publishing updates of the kind 17376.

Reference Implementation

This proposal has been implemented in a fork of nostr-dev-kit/ndk-wallet and is demonstrated in the latest Satshoot 1.0.0 release: Satshoot.

In this release, new Satshoot users can create their deterministic Cashu wallet on the wallet page, while existing ones keep their existing non-deterministic wallet with the option to upgrade it. The wallet restore functionality is available in any case, for non-deterministic ones too. Of course, users can restore their wallets using compatible implementations such as cashu.me or minibits as well.

Next Steps

We encourage the Nostr developer community to provide feedback on this proposal, helping to refine and consolidate our approach. Only through broad consensus can Nostr maintain its interoperability promise while evolving.

Our action items for the upcoming time include:

a pull request for NIP-60 with the new deterministic wallet kind,

an integration of the new kind in the nostr-dev-kit library, filed as pull request as well.

This text was written with the Pareto Client.

Something around Community. Which is my intention. Here's a ...

2025-11-05T17:27:54Z

In reply to nevent1q…7phh
_________________________

Something around Community.
Which is my intention. Here's a rough plan what I got in my head right now:

Problem: Communities around open source and freedom tech software development are fragmented.
- Code collab is mostly on GitHub but also on Gitlab, Gitea and some others.
- Conversation is scattered in even more places like Telegram, Discord, Signal, Simplex (group chat) and Reddit, Discourse, Github and some others (forum-like interactions).
- Coordination efforts like events (physical and virtual like community calls) are all over the internet as well

From the project leader's perspective open source is mostly a love-hate grind. Dealing with a flood of issues and PRs, keeping the community engaged and trying to balance a life with all challenges of open-source.

From the beginner dev's perspective It's really hard to get started and become useful. There's inherently low trust due to low quality contributions and churn. Hard to find mentors and jump-start a career, although it's attractive from the distance. College doesn't teach you useful stuff so this would be a nice replacement.

From the companies' perspective it's increasingly hard to find talent. College kids come out with fiat knowledge that's hard to utilize without massive investment from the company.

What all of these lack is a high-trust environment, sort of like a guild of the old days where craft and apprenticeship was taken seriously, and where talent can grow.

Moderated communities on Nostr are like these guilds in my head, without the monopolistic prices because you get a simple exit and continuity using Nostr.

Grow the community --> Establish Trust and let people earn reputation doing open-source /freedom tech work --> Get sponsored by companies for visibility in a place where mostly everyone could be their next hire.
Get sponsored on the main community site, community streams, etc. Companies could also pay for zapraisers in the community to virtue-signal.

They effectively pay for open-source development without having a say in what gets developed and how leaders want to manage their groups.

LinkedIn and such are just very lame these days. Everyone's there because they have to. It's because that is a low-trust environment, bad for recruiters.

Nostr could be the next place to grow developer talent. And we have literally everything to make this happen, the hard work is to grow successful communities. These will become unstoppable because if leaders screw up, members fork and keep it alive someplace else. It's the most trivial to do compared to other protocols.

BudaBit is designed to do something like this. Gives control to project leaders over their code collab (issues, PRs on Nostr, code anywhere at all redundantly), over the conversation (forum-like threads and group chat), coordination (calendar, later calls and streams), and funding (zaps, potential sponsorships).

Everything is verifiable and the content is compatible with other nostr apps. This coupled with moderation creates the perfect competition for the best communities where devs thrive, and is sustainable.

This is kind of my vision.

Lately an important contributor to the Stratum v2 (bitcoin mining ...

2025-11-01T07:17:46Z

Lately an important contributor to the Stratum v2 (bitcoin mining pool software) project was banned on GitHub:

quoting
nevent1q…ye29

bitcoin FOSS dev deplatformed by github

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:

quoting
naddr1qq…6e3k

Open-source software is becoming increasingly critical to our civilization: projects like GNU, Linux, Bitcoin, and many others are becoming absolutely essential to our flourishing and freedom in the digital age. Yet, the tools for open-source collaboration as a community effort fall short in so many ways: code collaboration and social interactions are fragmented across isolated platforms waiting to be rugpulled in one way or another.

Discovery, coordination, and discussion mostly happen on GitHub, Discord and a handful of other corporate solutions. They own our accounts and discourse: we have no real way to protect our projects from them. They created a false sense of safety, and we traded most of our freedom for convenience.

Current more freedom-oriented solutions do not solve the problem of capture either: Mastodon has shown us that server operators with absolute power are not the answer. Even if the dictator of the self-hosted server is benevolent, conflicts are inevitable. Others like Matrix and Bluesky are too complex to operate, so they do not provide a practical means of exit either.

We need to lay new foundations for communities around open-source software. Self-owned, easy to operate, and leader-accountability baked-in from the start. This is BudaBit in a nutshell.

Open-source development: not just code but a community effort

Outsiders might think of open-source software development as just nerds hacking on code. In reality, this is about 10% of the whole picture: like any software project, open-source needs all sorts of support: funding, testing/feedback, coordination around events, marketing and spreading the word... the list goes on.

Serious developers realize the need for social coordination but in practice the different aspects of open-source software development are heavily fragmented. It exists on a myriad of platforms and apps, using incompatible and unverifiable data. The rise of sovereign digital identity protocols gives communities the opportunity to jump sinking ships and build lasting relationships.

Nostr is the protocol that can make this shift happen. It provides sovereign cryptographic identities, is agnostic about data storage (a Nostr event is meaningful and verifiable on its own without any servers), and has open standards for any content type imaginable. This makes Nostr the firm foundation open-source needs.

Pragmatic decentralization: How BudaBit works

Leadership with accountability

Some community solutions disregard freedom entirely: they’re designed to lock people in and inevitably become enshittified. Others try to decentralize without a practical approach to user experience. If the average user cannot easily fork the community, it is bound to repeat the mistakes of the Fediverse, Matrix, Secure Scuttlebutt or Bluesky.

Therefore, BudaBit uses a moderated Nostr relay as the basis of a community: One central relay that anyone can back up means: - Consistency of community data - A way for contributors to step up as community leaders - An easy way to migrate or fork the community by any member

This creates a usable group with high signal, and keeps its leaders accountable. They have less incentive to kick people out and more incentive to solve conflicts. Nevertheless, if some people want to go the other way, they can trivially do so by downloading the Nostr events and uploading them on another relay. Relays do not have critical functionality tied to them but are mere repositories of events. They matter for good UX, but cannot lock users in. This is secession made simple.

Reputation of members in BudaBit accumulates and cannot be easily erased, but the real people behind them can freely create any number of Nostr identities. An identity reboot can happen with the trade-off that it starts with a clean slate of reputation and might be less trusted initially. However, communities can quickly recover from a leaked or stolen identity in practice if some members vouch for each other or by using off-protocol methods. The absence of protocol-level key rotation is another design aspect Nostr got right: resist complexity, and let people figure out the rest.

Use platforms where it makes sense, avoid where it doesn't

BudaBit is not a drop-in replacement for GitHub, GitLab or such. However, it deeply integrates code collaboration from any of these, while making them redundant utilities for open-source projects.

Code can still be hosted on popular platforms so projects make use of the convenience they provide, while drawing a clear boundary around social features they want to keep separate. Issues, discussions and the PR workflow must be protected by Nostr events. Code, CI/CD (like GitHub actions), and file hosting (such as releases) can either remain on platforms or be gradually migrated to an even more sovereign setup, like Grasp servers with Nostr-native Git server authentication.

Freedom tech tools are getting better for heavier tasks by the day but first movers have to endure an unpolished experience while the tech is maturing. BudaBit wants to provide a straightforward complementary experience requiring minimal changes to the usual workflows but delivering maximum impact on control and peace of mind. This is laying the groundwork for further steps toward freedom later on.

Ecosystem over platform bloat

BudaBit wants to offer a good community experience with git-centric workflows but not more. We strive to build software that is extensible via the Nostr protocol, similar to how WordPress has done it with blogs in the past. With Nostr, however, we have stronger cryptographic guarantees instead of loose conventions, and a vast number of use-cases instead of an inherently limited reach (e.g. only blogs and very basic websites for WordPress).

Nostr apps find niches and interoperate while platforms bloat. GitHub users understand what I am talking about: a mishmash of features that try to do everything at once. Users cannot draw clear boundaries and extend or modify features because GitHub is not open-source software and it is not trying to adhere to open-source values. It merely wants to leech off of open-source. In contrast, BudaBit is fully open-source and embraces cypherpunk values while meeting projects where they currently are.

BudaBit uses standard Nostr events for content types and NIP34 for git-related operations. In fact, https://budabit.club is just a static website easily deployable on a cheap web server. Moreover, running or renting a Nostr relay is considered quite simple already. This means that you can launch your own BudaBit community today, and we will make that even simpler in the future. Existing communities are compatible with each other, and thanks to Nostr the data speaks for itself, so the only thing required is to keep a copy of it somewhere.

Current status and future plans

BudaBit is focusing on delivering a stable experience for basic social interactions and code collaboration: - Chat rooms - Forum-like threads - Event calendar - Direct messages - Create and fork repos using GitHub, GitLab or Gitea - Track and browse repos announced on Nostr - Issues and Comments on Nostr - A basic PR flow that handles patches posted with ngit - Share git-related data anywhere

Expect some rough edges, with quick stability improvements on the basics. The future of BudaBit communities holds even simpler hosting, easy migration, and exciting innovations only possible on Nostr: - One-click migration from popular platforms for repo metadata, issues, and discussions - One-click deployment of all important components of the community - Full Grasp compatibility - Seamless PR workflow across all hosting providers, thus making ngit optional - CI/CD as a marketplace on Nostr for sats: generate income or help your cause by running CI jobs on your machine or phone - A Nostr-wide marketplace of extensions (NIP89) for extra features in BudaBit such as community calls, streams and job listings

BudaBit is here for the adventurers to start their own colonies on the new continent of digital freedom, unlocked by Nostr and Bitcoin. Try it today in beta, or take a glance at how the magic is made! We need feedback from open-source contributors, community leaders around OSS, and everyone trying to help open-source projects succeed.

#nevent1q…0pjm

2025-10-31T03:34:01Z

In reply to nevent1q…rjdt
_________________________

quoting nevent1q…0pjm
> "BudaBit is not a drop-in replacement for GitHub, GitLab or such. However, it deeply integrates code collaboration from any of these, while making them redundant utilities for open-source projects."

naddr1qq…6e3k

Ark server operators create a secondary "VTXO" system ...

2025-10-30T18:40:21Z

In reply to nevent1q…235q
_________________________

Ark server operators create a secondary "VTXO" system which eliminate the need for the bidirectional channel setup that LN has.
LN suffers from liquidity lockup: bitcoin sits on channels mostly inefficiently until a payment is initiated.

If your VTXO expires, you cannot unilaterally exit anymore so users are incentivized to move the money from time to time, avoiding inefficiencies of dormant liquidity.

I may be wrong but that's my curent understanding.

Ark has unilateral exit under certain conditions, while ecash ...

2025-10-30T18:31:05Z

In reply to nevent1q…235q
_________________________

Ark has unilateral exit under certain conditions, while ecash does not.

Liveness is necessary because they supposedly work with expiring presigned transactions.

The mistake they make is trying to centralize all the costs of ...

2025-10-30T17:09:39Z

In reply to nevent1q…4gh6
_________________________

The mistake they make is trying to centralize all the costs of hosting a group.

Relay-based groups on Nost don't assume that, it is just a group where anyone can run anything (mostly group admins but they can offload to some to enthusiastic members) *while staying compatible using nostr events* (signed and standardized) .

You can imagine plenty of sustainable models in this setup, and you get the network effect benefit.

Simplex wants to run on a platform model to capture value while not being the central point of failure.
This is unfeasible.

More competition certainly helps but to me it seems like there ...

2025-10-30T03:26:04Z

In reply to nevent1q…j837
_________________________

More competition certainly helps but to me it seems like there are limits to how much Lightning and especially the LSP model can improve on transaction costs, privacy and UX compared to custodial.

UX is harder for them because they need to explain channels somehow to the user when they charge for open/closes. They can abstract many things but not everything.

In my mind we have these spectrum of options:
1. Onchain
2. Lightning with own managed node
3. LSP with more convenience, more fees, less private
4. Cashu - we can think of this as custodial LN with very good privacy and very cheap transactions and offline capabilities under some circumstances

I don't know where to put ark and spark, I don't know them well enough. Fedi can also become an option in time.

I don't see a problem people choosing which tool and trade-off balance they like. I have used all on the above list for different purposes, and Cashu has its place for me, with a very clear tradeoff balance.

#Cashu seed backups (nut13) are coming to Nostr wallets ...

2025-10-29T18:45:57Z

#Cashu seed backups (nut13) are coming to Nostr wallets (nip60-61), thanks to rodant (nprofile…rs6u) !

Reckless people feel free to test on [SatShoot](https://satshoot.com) .

Recovery needs some more work but it's getting there. Cashu.me recovery should already work.

I heard honest and smart bitcoiners disregard Nostr because it ...

2025-10-29T17:34:23Z

In reply to nevent1q…xth2
_________________________

I heard honest and smart bitcoiners disregard Nostr because it still needs a blatantly obvious use-case it captures with an app that solves a very important and urgent problem they have.

Also, Bitcoiners have been spoiled with fantastic libertarian explanations of money, its origins and how it is broken.

We need that explanation for Nostr, and pioneer an example that cannot be waved off. The rest will follow.

You yourself are somewhat wary of the merits of social media, contrasted with an urgent problem with money. They feel that too.

It doesn't have to be an either or question, of course. We can attack centralization on multiple fronts. So we need to explain what Nostr is excellent (not just good) for and have that a particular solution featuring those properties.

Unfortunately I came to believe that social media might not be the area that gets us through the chasm. People mostly act like it's okay to have that centralized by corporations (they don't pay for services, gravitate back when a ban is lifted).
Network effects and convenience over freedom. It's the reality.

Social media will benefit from Nostr winning but those users will most likely be laggards in Nostr adoption.

My bet is markets (make sats, earn verifiable unstoppable Reputation) and interoperable/forkable communities (more signal and exclusiveness, more fear of censorship from gov, platforms and group leaders alike) .

Yeah I love Phoenix but it's really expensive and massively ...

2025-10-29T15:13:26Z

In reply to nevent1q…6pnc
_________________________

Yeah I love Phoenix but it's really expensive and massively less private compared to Cashu.

No cashu needed, but no real privacy from the custodian either. ...

2025-10-29T04:39:08Z

In reply to nevent1q…j680
_________________________

No cashu needed, but no real privacy from the custodian either.

Cashu is about private payments in a custodial setup.

If you could get most people to run LN nodes this would be great but that's not gonna happen.

Oh, and apparently some mints don't _yet_ charge for swaps ...

2025-10-29T04:20:47Z

In reply to nevent1q…zz5k
_________________________

Oh, and apparently some mints don't _yet_ charge for swaps but they will, this is just a matter of time.

They need to charge or they expose themselves to DoS and it'd be unsustainable as a business.

I think spending is acquiring in most cases bc you want to swap ...

2025-10-29T04:17:06Z

In reply to nevent1q…vycj
_________________________

I think spending is acquiring in most cases bc you want to swap tokens to the desired denomination and probably sometimes consolidate your proofs as well.

"Acquiring" can mean minting with LN, that's more fees than swapping.

Sending tokens to the other party without a swap means the recipient must swap them to avoid double spending so there's your fee on that too.

In summary, most every #cashu tx will at least require the recipient to swap, rarely the sender can avoid a fee.

It makes sense because at the end of the day without fees no payment system is sustainable.

But to your point, #ecash is massively lower fees than LN or onchain.

> "BudaBit is not a drop-in replacement for GitHub, GitLab ...

2025-10-25T11:45:18Z

> "BudaBit is not a drop-in replacement for GitHub, GitLab or such. However, it deeply integrates code collaboration from any of these, while making them redundant utilities for open-source projects."

quoting
naddr1qq…6e3k

Open-source software is becoming increasingly critical to our civilization: projects like GNU, Linux, Bitcoin, and many others are becoming absolutely essential to our flourishing and freedom in the digital age. Yet, the tools for open-source collaboration as a community effort fall short in so many ways: code collaboration and social interactions are fragmented across isolated platforms waiting to be rugpulled in one way or another.

Discovery, coordination, and discussion mostly happen on GitHub, Discord and a handful of other corporate solutions. They own our accounts and discourse: we have no real way to protect our projects from them. They created a false sense of safety, and we traded most of our freedom for convenience.

Current more freedom-oriented solutions do not solve the problem of capture either: Mastodon has shown us that server operators with absolute power are not the answer. Even if the dictator of the self-hosted server is benevolent, conflicts are inevitable. Others like Matrix and Bluesky are too complex to operate, so they do not provide a practical means of exit either.

We need to lay new foundations for communities around open-source software. Self-owned, easy to operate, and leader-accountability baked-in from the start. This is BudaBit in a nutshell.

Open-source development: not just code but a community effort

Outsiders might think of open-source software development as just nerds hacking on code. In reality, this is about 10% of the whole picture: like any software project, open-source needs all sorts of support: funding, testing/feedback, coordination around events, marketing and spreading the word... the list goes on.

Serious developers realize the need for social coordination but in practice the different aspects of open-source software development are heavily fragmented. It exists on a myriad of platforms and apps, using incompatible and unverifiable data. The rise of sovereign digital identity protocols gives communities the opportunity to jump sinking ships and build lasting relationships.

Nostr is the protocol that can make this shift happen. It provides sovereign cryptographic identities, is agnostic about data storage (a Nostr event is meaningful and verifiable on its own without any servers), and has open standards for any content type imaginable. This makes Nostr the firm foundation open-source needs.

Pragmatic decentralization: How BudaBit works

Leadership with accountability

Some community solutions disregard freedom entirely: they’re designed to lock people in and inevitably become enshittified. Others try to decentralize without a practical approach to user experience. If the average user cannot easily fork the community, it is bound to repeat the mistakes of the Fediverse, Matrix, Secure Scuttlebutt or Bluesky.

Therefore, BudaBit uses a moderated Nostr relay as the basis of a community: One central relay that anyone can back up means: - Consistency of community data - A way for contributors to step up as community leaders - An easy way to migrate or fork the community by any member

This creates a usable group with high signal, and keeps its leaders accountable. They have less incentive to kick people out and more incentive to solve conflicts. Nevertheless, if some people want to go the other way, they can trivially do so by downloading the Nostr events and uploading them on another relay. Relays do not have critical functionality tied to them but are mere repositories of events. They matter for good UX, but cannot lock users in. This is secession made simple.

Reputation of members in BudaBit accumulates and cannot be easily erased, but the real people behind them can freely create any number of Nostr identities. An identity reboot can happen with the trade-off that it starts with a clean slate of reputation and might be less trusted initially. However, communities can quickly recover from a leaked or stolen identity in practice if some members vouch for each other or by using off-protocol methods. The absence of protocol-level key rotation is another design aspect Nostr got right: resist complexity, and let people figure out the rest.

Use platforms where it makes sense, avoid where it doesn't

BudaBit is not a drop-in replacement for GitHub, GitLab or such. However, it deeply integrates code collaboration from any of these, while making them redundant utilities for open-source projects.

Code can still be hosted on popular platforms so projects make use of the convenience they provide, while drawing a clear boundary around social features they want to keep separate. Issues, discussions and the PR workflow must be protected by Nostr events. Code, CI/CD (like GitHub actions), and file hosting (such as releases) can either remain on platforms or be gradually migrated to an even more sovereign setup, like Grasp servers with Nostr-native Git server authentication.

Freedom tech tools are getting better for heavier tasks by the day but first movers have to endure an unpolished experience while the tech is maturing. BudaBit wants to provide a straightforward complementary experience requiring minimal changes to the usual workflows but delivering maximum impact on control and peace of mind. This is laying the groundwork for further steps toward freedom later on.

Ecosystem over platform bloat

BudaBit wants to offer a good community experience with git-centric workflows but not more. We strive to build software that is extensible via the Nostr protocol, similar to how WordPress has done it with blogs in the past. With Nostr, however, we have stronger cryptographic guarantees instead of loose conventions, and a vast number of use-cases instead of an inherently limited reach (e.g. only blogs and very basic websites for WordPress).

Nostr apps find niches and interoperate while platforms bloat. GitHub users understand what I am talking about: a mishmash of features that try to do everything at once. Users cannot draw clear boundaries and extend or modify features because GitHub is not open-source software and it is not trying to adhere to open-source values. It merely wants to leech off of open-source. In contrast, BudaBit is fully open-source and embraces cypherpunk values while meeting projects where they currently are.

BudaBit uses standard Nostr events for content types and NIP34 for git-related operations. In fact, https://budabit.club is just a static website easily deployable on a cheap web server. Moreover, running or renting a Nostr relay is considered quite simple already. This means that you can launch your own BudaBit community today, and we will make that even simpler in the future. Existing communities are compatible with each other, and thanks to Nostr the data speaks for itself, so the only thing required is to keep a copy of it somewhere.

Current status and future plans

BudaBit is focusing on delivering a stable experience for basic social interactions and code collaboration: - Chat rooms - Forum-like threads - Event calendar - Direct messages - Create and fork repos using GitHub, GitLab or Gitea - Track and browse repos announced on Nostr - Issues and Comments on Nostr - A basic PR flow that handles patches posted with ngit - Share git-related data anywhere

Expect some rough edges, with quick stability improvements on the basics. The future of BudaBit communities holds even simpler hosting, easy migration, and exciting innovations only possible on Nostr: - One-click migration from popular platforms for repo metadata, issues, and discussions - One-click deployment of all important components of the community - Full Grasp compatibility - Seamless PR workflow across all hosting providers, thus making ngit optional - CI/CD as a marketplace on Nostr for sats: generate income or help your cause by running CI jobs on your machine or phone - A Nostr-wide marketplace of extensions (NIP89) for extra features in BudaBit such as community calls, streams and job listings

BudaBit is here for the adventurers to start their own colonies on the new continent of digital freedom, unlocked by Nostr and Bitcoin. Try it today in beta, or take a glance at how the magic is made! We need feedback from open-source contributors, community leaders around OSS, and everyone trying to help open-source projects succeed.