Gzuuus

Forever learning, continuously buidling⚡
cryptoanarchism student
https://nostree.me/gzuuus
#noderunner#Bitcoin | #technology | #art | #electronics

Public Key

npub1gzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gs3ea5ds

NIP-05 Address

[email protected]

Profile Code

nprofile1qqsypwwgtll74lqu4huvxzjwtjyxvrlkujt35rw8y026ke6ttesmg5gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds4n6g3w

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1gzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gs3ea5ds

Show more details

Last Notes

2025-10-15 21:32:28 UTC

- reply

PROTECT YOUR ATTENTION AT ALL COST specially for things you care about
#nevent1q…zme6

2025-10-15 14:21:49 UTC

It's incredible how now days any conversation or discussion can be interrupted by a notification. You could be having an important discussion, and then a notification rings on a phone. With a high likelihood of this happening, the conversation or discussion gets hijacked and distorted, and it just vanishes as our attention wanes and jumps between stimuli. This is destroying relationships between people, and not just between people, but also within ourselves. It's incredible that this happens so frequently. Your priorities just switch between what is happening and this random thing that makes your phone ring. To be honest, it's pathetic, and just demonstrate how hackable our brains are... I hope we realize how dangerous this is.

2025-10-13 07:57:28 UTC

GM🌞

2025-10-10 09:00:08 UTC

- reply

I did this one sometime ago, its a relay that can sign notes, the idea is that you can create "subkeys" in the relay dashboard and use them in any client connected to the relay and then get the notes signed with the main key https://github.com/gzuuus/mimoty

2025-09-28 08:00:00 UTC

- reply

The og
#nevent1q…92lu

2025-09-28 07:38:45 UTC

- reply

Cool! I'll avoid to watch the trailer and wait until the film (trailers are shitcoins)

2025-09-28 07:29:58 UTC

GM is GFY 🌞

2025-09-27 09:59:58 UTC

Just a retired in a field
https://nostr.download/7cca706a7a022ce1414d964e6c85288094231dee93886368bd4851db33acbbaa.jpg

2025-09-26 11:34:19 UTC

- reply

Today is shipping day arr

2025-09-26 07:47:03 UTC

GM 🌞
https://nostr.download/50853ef54b719afb01130b8b7055a0e8b7a7eb417da1427fc867e0c40b4bbb30.jpg

2025-09-25 21:45:39 UTC

- reply

It always does, it's a quite powerful duck👌

2025-09-25 20:53:02 UTC

- reply

🦆🍀🚀🚀

2025-09-25 08:32:08 UTC

- reply

GM 🫶

2025-09-25 07:26:03 UTC

- reply

Gm frann :)

2025-09-25 07:19:15 UTC

GM🌞

2025-09-25 07:19:01 UTC

- reply

What I've lost? 👀

2025-09-24 19:32:54 UTC

- reply

and nutoff 🤟

2025-09-24 14:25:09 UTC

- reply

Yes, I understand. I'm also not engaging in politics within the NIPs repo. The interoperability we have today is the result of blood, tears, and sweat, the hard work, dedication, and passion of developers who truly believe in what they are doing. However, this is not due to clear guidelines or good support for interoperability. The fact that Nostr is relatively easy to reverse engineer has facilitated this interoperability, but it is not because the protocol is well-specified.
I see this as a potential vector of attack that could lead to the protocol being captured. You cannot combat this if you are merely ranting and confused (which, incidentally, is the name of the Nostr Telegram groupgroup xD). The direction I'm pointing towards in the article is simply a suggestion on how we can improve this situation. We need cleaner and clearer specifications and processes. As Nostr grows, the effort required to maintain interoperability will inevitably increase.

2025-09-24 14:12:18 UTC

- reply

I was testing https://github.com/musistudio/claude-code-router, which essentially allows you to use any llm from different providers with Claude code. I've also noticed that Codex lets you define the base URL, so theoretically, you could use any other provider, although I haven't tested this yet. The key point to understand is that different llms can be used as agents within these agentic coding CLIs. Choose the one that integrates better with your IDE and experiment with different LLMs to find what works better for you

2025-09-24 13:43:36 UTC

- reply

Yay! The duck of luck and I wish you good luck and a high grade on your exam 🦆🍀

2025-09-24 13:29:07 UTC

World of sheep, government of wolves

2025-09-24 12:42:23 UTC

- reply

GM! Sleepy?

2025-09-24 07:42:17 UTC

- reply

Good mantra xD

2025-09-24 07:35:55 UTC

GM🌞

2025-09-23 14:29:06 UTC

Be consequent; you are the only one responsible for your acts and decisions, no one else. That means that in essence, you are free

2025-09-23 09:45:42 UTC

- reply

Last windows I touched as daily driver was XP

2025-09-23 08:18:11 UTC

- reply

@nprofile…jq5m

2025-09-23 07:33:30 UTC

GM🌞

2025-09-21 17:33:57 UTC

- reply

That's definitely true; you are where everything starts, but we need collaboration

2025-09-21 17:26:39 UTC

- reply

Some people are awakening. The majority is procrastinating

2025-09-21 14:36:15 UTC

- reply

Oh man it would be amazing if you could experiment and report back on the effectiveness of these defensive techniques. It could be huge in defending against new, modern threats.

2025-09-21 14:31:35 UTC

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

2025-09-21 14:18:05 UTC

La letra de esta canción... Escucha con atención
https://www.youtube.com/watch?v=mJ3_JHXEWlY

2025-09-21 14:17:09 UTC

- reply

Would be amazing if you find an effective way to stop ddos based on that

2025-09-21 14:09:41 UTC

The world is going nuts, period.

2025-09-21 10:38:15 UTC

- reply

Why does your cat look so sad?

2025-09-21 10:37:05 UTC

https://github.com/gensecaihq
AI defending against AI. We are living in the future

2025-09-21 09:08:12 UTC

GM🌞

2025-09-21 08:11:10 UTC

- reply

GM🌞

2025-09-20 10:08:35 UTC

Hahaha, man, that demo had more failures than all the soveng demos together. Epic https://www.youtube.com/watch?v=wsHt2YReQzA

2025-09-19 12:06:50 UTC

- reply

Virtually 0 bugs

2025-09-19 11:42:28 UTC

https://youtube.com/watch?v=iamEJE1cC14

2025-09-19 11:18:23 UTC

- reply

Thanks for your comment! I believe that any protocol requires a specification; otherwise, it's not a protocol, but rather a mess. You're right that what you're mentioning could happen: different specifications for the same use case competing and eventually needing to be interoperable through bridges, adapters, or translation layers. If Nostr ends up in that situation, I would consider it a failure. Interoperability is king

2025-09-19 11:13:32 UTC

- reply

I may have an idea for this 🤔

2025-09-19 11:12:51 UTC

- reply

👌

2025-09-19 11:11:32 UTC

- reply

Recommended
#nevent1q…r202

2025-09-19 10:22:39 UTC

- reply

Gm 🫶

2025-09-19 09:01:34 UTC

- reply

GM 🌞
#nevent1q…jpem

2025-09-18 21:26:06 UTC

- reply

Funchal? 👀

2025-09-18 18:44:38 UTC

Tomorrow is demo day #soveng
https://nostr.download/d57fccc4b7ced208ab060f01de6883e967f55fd571a23e76ae3e24524a4db301.jpg

2025-09-18 16:33:34 UTC

- reply

Hijacking your attention since 2005

2025-09-18 13:50:19 UTC

- reply

Gm 🌞

2025-09-18 09:51:02 UTC

- reply

Ok, seems we touched a nerve. We can agree to disagree; that’s fine. My argument in the article is that Nostr needs a better governance model to foster collaboration and provide clarity for newcomers. I mentioned Fiatjaf’s article because it’s another example showing that the community already recognizes problems with the current model.
From my point of view, Nostr needs clearer guidelines and specifications if it expects to be interoperable within a wider ecosystem. The “wild west” approach can remain for experimentation, but that’s why I mentioned the dual-layer approach used in Lightning (BOLTs and BLIPs). I think a similar approach could help people and communities feel comfortable building on Nostr and make it easier for newcomers to participate. It would also help defend and harden the protocol against political and influence attacks, something I think is quite feasible. In fact, rejecting any governance model increases the chance of capture by an organization that can exploit the general confusion and discomfort about “how the hell do I build on Nostr” without having to dig through hundred of unstructured threads, discussions, issues, and PRs to just grasp the rationale and philosophy behind the protocol.
If you read my article with fresh eyes rather than getting triggered, you’ll see that my proposals and key guidelines are intended to improve the clarity of the spec documents, restore attribution to organically create reputation, and define clear lifecycles for new proposals that expect to be interoperable. I’m not advocating for a “Nostr steering council” or anything like that. I mention these projects (peps, rfcs) because they effectively manage large ecosystems; even if Nostr isn’t that large yet, it will need some structures if we don’t want it to collapse as it grows.
Also, Conway’s Law describes a symptom of capture: complex projects tend to take the shape of the organizational structures that design them. This ties into the “embrace, extend, extinguish” methodology I mention in the article.
In short: it’s not about bureaucracy, it’s about resilience.
PS: LNURL specs are confusing too

2025-09-18 07:57:22 UTC

- reply

Haha mas o menos 😅

2025-09-18 07:36:52 UTC

- reply

GM🌞

2025-09-17 21:31:34 UTC

- reply

GN🌝

2025-09-17 21:26:23 UTC

- reply

Death by thousand cuts

2025-09-17 16:20:28 UTC

- reply

Agree. They can be different type of specifications for relays and clients

2025-09-17 16:17:37 UTC

- reply

I think you are missing the point. I don't know whether it's because you didn't fully read the article, you weren't paying attention while reading, or something triggered you. But I'm not talking about formalizing Nostr development, I'm talking about governance and a process to propose new interoperability standards. If you read carefully, you'll notice that I treat that distinction with care. No one can impose anything on Nostr, no top‑down imposition; that will never change, but it's different when we expect interoperability: that's when we need a more robust framework.
It also doesn't matter whether it's about money. Some of the projects with more robust and successful governance that I mention in the article (Py PEPs, Rust RFCs) are unrelated to money, and yet they designed a pretty good way to manage their project with thousand and developers, stake holders and participants, so I don't understand your rationale there.
Anyway, I'm just reflecting on how weak governance can be an attack vector, and how better-designed guidelines and processes can help us be more resilient in the long term.

2025-09-17 12:43:09 UTC

Almost two weeks ago I began working on this article. It grew out of conversations with several people involved in Nostr and Open source, and from the realization that a very informal specification process is indeed a vulnerability. I would love to hear your thoughts.
Thanks also to everyone who provided feedback while I was writing, and to the participants in #soveng for sharing helpful feedback and resources I didn’t know about, they made the article much stronger.
#naddr1qv…4ag2

2025-09-16 21:32:05 UTC

- reply

Bump feast

2025-09-16 18:31:28 UTC

NOSTB - Notes and other stuff transmitted by banks

2025-09-16 07:54:03 UTC

Hahaha nice way to raise awareness
https://www.gadgetreview.com/massive-attack-turns-concert-into-facial-recognition-surveillance-experiment

2025-09-16 07:47:51 UTC

- reply

True
#nevent1q…8h55

2025-09-16 07:17:35 UTC

- reply

GM 🌞

2025-09-16 07:09:41 UTC

- reply

Screens are shitcoins

2025-09-15 15:55:29 UTC

https://youtube.com/watch?v=JxfuQ8a5gwA

2025-09-15 13:15:52 UTC

- reply

Yes, basically, the local Cashu wallet can be used remotely. The wallet can run anywhere and use Nostr relays for hole punching. From it, you can designate allowed keys that have permissions to call all the methods of the wallet, while the rest of the non-allowed pubkeys can only call some public methods (make_invoice, get_info, lookup_invoice). The HTTP server is just a public service that translates between LNURL and MCP/ContextVM. So yes, you can be nomadic and run the wallet anywhere. While the wallet is running, it is reachable remotely. I think a cool use case is for spontaneous markets where all merchants can receive payments automatically and without hassle. Of course, anyone can use this to spin up a wallet very easily

2025-09-15 11:05:33 UTC

This is a diagram showing how the different parts of nutoff work together.
https://image.nostr.build/25928ecefffe5a12164c46b929b53913ddb5561c8160e204a22543d404caec3e.png
#nevent1q…qwf3

2025-09-15 07:14:07 UTC

- reply

Yes, the reason was that nostr-tools lib broke in an update.

2025-09-15 07:12:03 UTC

GM 🌞

2025-09-15 07:06:55 UTC

- reply

Gm Franny :)

2025-09-15 07:04:40 UTC

- reply

I use feeder normally

2025-09-14 20:31:14 UTC

- reply

Sent you a dm, cannot see nothing on 0x

2025-09-14 19:53:00 UTC

- reply

Ups sorry, let me install 0x and see if I can answer there 👌

2025-09-14 08:37:32 UTC

GM🌞

2025-09-13 20:07:52 UTC

- reply

Thanks for the sats 🥰
#nevent1q…dkz0

2025-09-13 19:18:51 UTC

If you zap this lightning address d30ef73ddc36ae3f4398c4972008a0862488f44303a8f305a6a1f3c68d01ece0@dvmcp.fun i'll receive some nuts, also you can visit this page to generate invoices https://dvmcp.fun/w/d30ef73ddc36ae3f4398c4972008a0862488f44303a8f305a6a1f3c68d01ece0
#nevent1q…cr3r

2025-09-13 19:08:25 UTC

Ok, here we go! A little demo on how you can use the Nutoff wallet. This is not meant to have a good UX, as it's just for educational and experimental purposes. But if you want to play with it, follow these steps:
1. Open your terminal, and navigate to a directory where you feel comfortable placing the codebase of this project. Then, run `git clone https://github.com/gzuuus/nutoff-wallet.git`
2. Navigate into the `nutoff-wallet` directory and run `bun i`
(I assume you can use other package managers, but it will definitely work with https://bun.sh )
3. Now, just run the wallet by executing `bun run mcp-server.ts`
It has some default settings, but it is highly recommended to set a private key. This way, every time you execute the wallet, it will have the same public key. Also, configure some allowed public keys; these will be able to spend from the wallet. Just put your public key. It also accepts a list of keys if you want more than one key to be able to spend from the wallet. See the `example.env` file for more details.
At this point, your wallet is running, and you should see a message like this one
https://image.nostr.build/1daad14ee3368e6f86382ece7a16a8788498ddda74872bf64628a395a85eab44.png
The last line shows the public key of your wallet. Now you can either go to https://contextvm.org/s/<your-wallet-public-key> from where you can manage the wallet and create invoices, get the balance, pay invoices, create Cashu tokens from your balance, etc. Or you can test the Nutoff LNURL proxy, which is temporarily running (it will be shut down soon) at https://dvmcp.fun (yes, I've just reused that domain for demo purposes). You will have a Lightning address automatically at `<your-wallet-public-key>@dvmcp.fun`, which you can use to start receiving payments... Magic! There is also another goodie: if you go to https://dvmcp.fun/w/<your-wallet-public-key>, it will show your LN address and a little POS to generate invoices that people can pay. This is the page of my wallet https://dvmcp.fun/w/d30ef73ddc36ae3f4398c4972008a0862488f44303a8f305a6a1f3c68d01ece0
https://image.nostr.build/c781827d7c8966448144286b60966c905143b95fe3b0800a3919351f6edf3f81.png
That's it! Now, to see the balance or pay invoices from there, you can either use your wallet remotely by going to https://contextvm.org/s/<your-wallet-public-key> or you can use the CLI interface.
Remember that the wallet has to be on to be able to receive payments, so ideally, you'll run this on a device that is always on, or that is on for some hours each day. While it is on, it can be used remotely.
This is just a proof of concept. Much better UI/UX can be done, and an interface can also be built as a static site, or even a hypernote. 👀 Imagination is the limit!
#nevent1q…h2ue

2025-09-13 18:13:33 UTC

- reply

Haha good luck... But I'll run if someone put all these concepts together

2025-09-12 22:10:11 UTC

- reply

2025-09-12 15:53:19 UTC

Today is demo day at soveng! Recklessly introducing Nutoff: a local Cashu wallet with a twist. It can be used via the command line or remotely through ContextVM. This allows users to interact with their local wallet remotely. Some methods are publicly accessible, such as 'make_invoice,' so anyone can generate invoices to pay you, while others, like 'pay_invoice,' are restricted to approved pubkeys, allowing only you or authorized users to spend from the wallet.
Nutoff also includes a web server component that translates between the local Cashu wallet and the LNURL (LUD06/LUD16) specification, enabling email-like Lightning addresses. This service runs publicly and proxies requests between Lightning wallets and the local Cashu wallet without handling funds directly. It is intended to be a public service run by a service provider, a community, or similar.
The idea that inspired this project is npub.cash, which is a great service that allows anyone to have a Cashu wallet without hassle. The difference between npub.cash and Nutoff is that npub.cash stores nuts in a database run by the service, while with Nutoff, the database runs locally. This improves the security model, but the drawback is that you need to run the wallet on one of your devices, such as a computer running Umbrel or Start9, a phone, a rpi, etc. This security model ensures that the wallet remains local, with all critical data stored on the user's device.
Key use cases include:
1. **Automatic Wallet**: Runs locally on a device, enabling payments without the need for accounts or data custody.
2. **Spontaneous POS**: Can start receiving payments immediately, ideal for merchants in flea markets.
3. **Community LNURL Server**: Provides Lightning addresses for a community, family, or friends using a custom domain.
4. **Custom Applications**: Limited only by imagination.
Nutoff offers a flexible, secure, and local solution for managing Cashu wallets with various deployment options.
Wallet: https://github.com/gzuuus/nutoff-wallet
LNURL proxy: https://github.com/gzuuus/nutoff-http
CC @nprofile…rzrk @nprofile…87e5

2025-09-12 11:44:52 UTC

https://youtube.com/watch?v=dDrizGgvP7o

2025-09-12 09:35:09 UTC

- reply

I did keynest which is a key store for nostr keys which also have derivation using bip32. But never through about using that as auth for relays, could be interesting. Maybe it could work by just giving the relay an xpub

2025-09-12 07:21:35 UTC

- reply

🚀

2025-09-11 15:24:07 UTC

- reply

LG 🧡

2025-09-11 10:46:09 UTC

https://youtube.com/watch?v=_WGPfJ2i8WU

2025-09-11 08:57:47 UTC

- reply

Yes, the important part is to realize you are not responsible about everything. You are just responsible of how you do things, nothing more

2025-09-11 08:45:12 UTC

- reply

🫂

2025-09-11 08:43:16 UTC

GM
https://arstechnica.com/tech-policy/2025/09/court-rejects-verizon-claim-that-selling-location-data-without-consent-is-legal/

2025-09-11 08:17:39 UTC

- reply

Gm 🧡

2025-09-10 08:51:34 UTC

- reply

XD gm

2025-09-09 10:04:39 UTC

- reply

I'll have it for demo fri (mvp at least) 🤙 I'll mark the date on my calendar

2025-09-09 08:30:02 UTC

- reply

(CLI cashu wallet + contextvm implementing nwc api) * lnurl address http proxy server = lnurl address and cashu wallet for everyone. Minimized trust meets ease of deployment 🤙

2025-09-09 08:19:00 UTC

- reply

Working on a similar concept, should be public on Friday 🤙 The difference in my approach is that the cloud is out of the equation, and everything remains local while reachable through nostr

2025-09-09 07:38:02 UTC

- reply

Wait for it...

2025-09-09 07:36:09 UTC

GM🌞

2025-09-09 07:30:30 UTC

- reply

Wild times ahead, be mindful of this. Attacks now are "cheaper"
https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised
#nevent1q…e7k5

2025-09-09 07:29:12 UTC

- reply

Probably is because of this https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised

2025-09-08 18:33:29 UTC

And the masks fell off