Gzuuus

Forever learning, continuously buidling⚡
cryptoanarchism student
chat: https://cordn.net/p/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

2026-08-15 09:58:03 GMT

https://blossom.primal.net/43d094f885b0fbfcbbd39249feed5a4800a36657542c6a2fb40fccf2d774d56e.jpg

2026-08-14 11:04:20 GMT

Grose, probably face wash / normalization move 🤢🤮
#nevent1q…2nry

2026-08-14 07:41:34 GMT

https://blossom.primal.net/bcfa376439b8c35ac152b13592ef05a2a594c428eb20791353dfcf4f82839797.jpg

2026-08-13 08:30:36 GMT

https://blossom.primal.net/fbdb8b3232a4a7e2564b482f464f4dc87e0272e9760488be189e37ecd6d93377.jpg

2026-08-12 23:27:02 GMT

- reply

Given that you are questioning it, and therefore adding a new dimension I would say it is 5d

2026-08-12 09:38:58 GMT

https://blossom.primal.net/99b12d3725f55ed62ebb9a6e7c1453ffd8c4b7c92be8f77f819972449f18a9aa.jpg

2026-08-11 07:51:33 GMT

- reply

Maybe @npub1t6m…qycp si?

2026-08-10 09:25:08 GMT

- reply

Hahaha no never heard about him, is good?

2026-08-10 07:47:24 GMT

- reply

Thanks guys for having me, was fun :)

2026-08-07 08:26:00 GMT

GM 🌞
https://blossom.primal.net/9654ce6d21b3ab03577cf413053a004423be903c99ffe2180adddfc96031edf0.jpg

2026-08-06 11:19:27 GMT

- reply

I don't think so hahaha

2026-08-06 10:59:57 GMT

- reply

Exactly, But GFY != GFY

2026-08-06 09:11:45 GMT

- reply

GM it is :)

2026-08-06 09:07:55 GMT

https://blossom.primal.net/0555a3959c526d770239a23cf2a83d72bd23240b38efed72ef4cb3746f0c4afb.jpg

2026-08-06 09:04:07 GMT

- reply

Out of context?

2026-08-05 09:00:21 GMT

https://blossom.primal.net/9d99658189d0e6530e6fe5a6990492e56862e706bd3162af2abd815239cf75e9.jpg

2026-08-04 21:46:38 GMT

Masterpiece
https://www.youtube.com/watch?v=QOrrNM4md8c

2026-08-04 14:25:04 GMT

- reply

With love

2026-08-04 09:07:27 GMT

- reply

Me too, then I discovered orca and so far enjoying it, it fills some gaps herdr had from my pov

2026-08-04 07:35:09 GMT

- reply

Hahaha tbh I'll probably give you more headaches

2026-08-03 21:58:28 GMT

- reply

The good life 🫂

2026-08-03 16:41:42 GMT

- reply

That's a great question! Would love to know as well

2026-08-03 09:17:13 GMT

- reply

Damn nippies 💪💪

2026-08-03 08:51:38 GMT

- reply

Cannot zap you :./

2026-08-03 06:35:53 GMT

- reply

Also if you wanna test cordn.net/p/gzuuus

2026-08-03 06:35:29 GMT

- reply

cordn.net it basically is mls over nostr but using a coordinator. I cover it up here #naddr1qv…7qdm

2026-08-03 06:30:39 GMT

GM🏄

2026-08-03 06:15:44 GMT

- reply

GM🫶

2026-08-02 11:18:34 GMT

- reply

you're sharp my friend hahaha

2026-08-02 10:29:51 GMT

I'll get indigestion from so much popcorn 🍿

2026-08-01 12:42:18 GMT

- reply

https://coldcard-hack.up.railway.app/

2026-08-01 12:41:33 GMT

- reply

Ooof 🥲

2026-08-01 11:26:31 GMT

- reply

Classic

2026-08-01 10:30:04 GMT

- reply

A well, physical access to the device... You can't really do nothing in that situation

2026-08-01 09:42:44 GMT

- reply

Trezor? Why?

2026-08-01 09:33:39 GMT

- reply

GM sk8r

2026-07-31 14:46:57 GMT

- reply

The point I wanted to make is that the "rush effect" would help attackers prioritize targets by just watching the mempool. And yea, I passes my text through an llm. Just deleted, I will rewrite it later, did it in a rush

2026-07-31 14:38:55 GMT

So is the mempool full of weak ass addresses yet? Probably it's about to be.
Everyone yelling "move your funds NOW" isn't wrong. This is a live attack and sitting still isn't safer. But here's the catch nobody's mentioning: even if your wallet has poor entropy, it is indistinguishable from any other wallet. The moment everyone rushes at once, the mempool fills with exactly the weak entropy addresses attackers are hunting. Your unconfirmed sweep tx just sits there publicly, basically flagged "fleeing Coldcard user" waiting on a block.
The ugly part is that while it sits there, if your sending key is weak, whoever crack it before the tx confirms can fire a higher fee tx that redirects your funds somewhere else. Full-RBF means bigger fee wins, and for the mk3 weak wallets that crack fits confortably inside the time a block confirm.
So yeah, move, but pay the fee (fast confirm = short window) specially if your address is one of the weakest ones.

2026-07-31 13:16:11 GMT

- reply

It was at some point

2026-07-31 12:51:06 GMT

Another great (yet painful) lesson about why open source is important, and why having as many eyes as possible, especially in security sensitive projects, is crucial.

2026-07-31 07:31:22 GMT

GM what a fuckity fuck oopsie woopsie 👀

2026-07-30 08:52:44 GMT

https://blossom.primal.net/4c11c4c4ba5cc95f071f3cd0a6a896f15897c6d3b7f07e972fc9920c00222924.jpg
#nevent1q…3ace

2026-07-29 08:01:00 GMT

- reply

Well, anything that's not nip01 could be considered "special" so relays need to support extra features like count, search, etc. So yes, I would say vertical

2026-07-29 06:30:11 GMT

GM🖖

2026-07-28 10:58:26 GMT

My god... And they complain about destillation from other companies... They are evil
#nevent1q…r7jj

2026-07-28 08:55:49 GMT

- reply

Yea, please do, would love to hear your thoughts. And yea, I agree with your point of view, dumb relays are general purpose indexes if you want to see it in that way, it works

2026-07-28 08:52:13 GMT

Why such a long face?
https://blossom.primal.net/99249fd6c445aa96f6c15c01c3b1f6cb91d3a2bbaa3e78e1974c2e13bfd76d11.jpg

2026-07-28 06:56:53 GMT

GM🌞

2026-07-27 19:02:56 GMT

TLDR of the TLDR: Notes and other stuff TRANSMITTED by relays. Assume storage, have fun 🫂
#nevent1q…hz4f

2026-07-27 17:31:28 GMT

https://music.youtube.com/watch?v=selAvZE6lp4

2026-07-27 14:39:02 GMT

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

2026-07-27 12:42:08 GMT

- reply

Yea that's interesting indeed we are thinking about how to do the same in cordn. So far that's one of the options, and the other is to share group state for the epochs you want new users to have access to, so they could naturally just catch-up from them and decrypt by themselves. I think this scales better since it avoids redundancy. But still exploring different solutions. In any case, why is this incompatible with the cordn client? I should be able to join your group even if I don't have access to the previous map data right? Are you using your own cordn coordinator?

2026-07-27 12:37:57 GMT

https://music.youtube.com/watch?v=sFUGvdxuQGQ

2026-07-27 12:23:07 GMT

Great post, and it gives me the groundwork to write about something I’ve been thinking about for a while now. I’ve discussed it with different people, the latest being @npub1wf4…dgh9 . This is about relay specialization versus a dumb relays topology. There’s a lot to unpack here, but I’ll try to keep it concise and dynamic.
Also tl;dr at the end of the note ;)
One of the first things that caught my attention early on when I discovered Nostr was that relays were dumb and clients were smart. All relays could be used homogeneously and interchangeably. The more relays, the better, right? The bigger and more distributed the network, the harder it is to shut it down or prevent someone from using it. In other words, in this topology, decentralization and censorship resistance scale horizontally. And this is true, I really believe it. But as Nostr evolved, more use cases emerged, new attacks appeared (spam, etc.), and Nostr started to need more specialized relays, hardened specs, rules, and so on. This shifts the balance between dumb relays and smart clients, and in my view, it’s a logical evolution.
A one-size-fits-all solution is difficult, if not impossible, to achieve. We’re seeing this tension now with the buzz (I used this world deliberately 🐝) around chats, groups, and so on. NIP-29 is a clear example, it acknowledges this tension from the start and accepts it to make things work. From my perspective, this is the right approach, and I completely agree with @npub1t6j…ksrw :
"The point of Nostr was never to get rid of servers; the point of Nostr is to be free again to leverage them for what they are good for. "Platforms" conflated purposes, also taking responsibility for identity and by extension the social graph, resulting in the capture of the user."
#nevent1q…hthu
Accepting this limitation of "dumb" relays means accepting that not every use case will fit into general purpose infrastructure. Expecting any use case to work reliably, beautifully, and without issues in such a setup is a stretch. Specific use cases with constraints or requirements need specialized services that can support them.
On the other hand, the problem with specialized relays is that they scale vertically, unlike general purpose ones. This means each specialized kind of relay becomes its own decentralization and censorship resistance vector. This does create some tension with Nostr’s original promise, but in my view, it’s a fair and honest one. Specialized relays make sense, and we shouldn’t feel aversion towards them.
Beyond this, there’s a third path I’ve been exploring with @npub1dvm…3jdm , moving the "smart" logic to a separate service that runs alongside relays and just uses them as a bus. This way, complex or specialized logic can be offloaded from relays, which can remain as dumb and homogeneous as possible. Before CVM, DVMs already offered this characteristic, it’s just RPC over Nostr. From my perspective, this approach strikes a great balance. As I mentioned earlier, if relays are standard and not specialized, they remain homogeneous, decentralization and censorship resistance scale horizontally, and the network becomes more resilient and harder to shut down. CVM also doesn’t impose storage pressure on relays, making relays cheaper and more sustainable to run. A clear example of this is Cordn coordinators, an specialized service that handle ordering so the MLS encryption state machine can work without issues. They interface through relays and store encrypted blobs, but nothing is stored in the relays themselves. Any relay accepts their traffic, and it works well.
Another nice feature of offloading logic from relays and running it in a separate service is that the bus doesn’t know what’s running, and the logic service doesn’t have network visibility. This creates a nice balance that benefits privacy and deniability. To wrap up this section, another interesting advantage is that running CVM servers is easier than running a relay. Relays need to be exposed, requiring network configurations and touching parts of the internet’s permission backbone (DNS). Of course, you can run a relay on Tor, but a CVM server doesn’t need any configuration, you just run it, and it’s accessible. You can even run it from your laptop in a coffee shop.
TL;DR: Dumb relays are great for decentralization and censorship resistance but fall short for use cases with specific requirements. Specialized relays are necessary and make sense for supporting those use cases, but decentralization scales vertically. CVM is a third path that leverages a network of dumb relays while offloading logic from them.
#nevent1q…27qe

2026-07-27 10:29:21 GMT

- reply

Well, I’m still trying to wrap my head around the protocol, and my analysis also points to a relay specialization for running Concord groups. Concord introduces special features, such as the gift‑wrap inversion and edge cases like deletion, that cannot be solved in any way by real relays aside of your other points from your article. Alex left me a note saying "deletion by all" can be seen as a feature, not a bug. I think it is a huge source of instability/edge cases, especially in large, public groups where not everyone is trusted and can easily disrupt the group’s health.
As you noted, rate‑limiting and relays potentially dropping events can be harmful to Concord’s control plane. In a world with a diversity of relay implementations and cofigs, each with different settings for rate limiting, spam prevention, and so on, this could become very unreliable, assuming relays will behave homogeneously is too happy path protocol design. Put aside from the ability of relay operators to calculate heuristics over the stream provenance and users.
So, yea, I would say that Concord works over any relay for its fundamental operation, but it is probably not reliable in the long term because of all the possible relay quirks, weirdness, and edge cases that could exist. NIP‑17 is more straightforward yet still considered unreliable by many developers, so Concord could be even less reliable. Let’s see how it evolves

2026-07-27 08:26:07 GMT

- reply

https://blossom.primal.net/420e9c6891aa97522500900fd064b170b5d2b7b51b7a206f5bdbaebf362ade89.jpg

2026-07-27 08:22:56 GMT

I'm looking for ~/

2026-07-27 07:43:45 GMT

GM🌞

2026-07-26 12:42:44 GMT

- reply

How did you achieved that? To provide historical messages to new joiners?

2026-07-26 11:08:59 GMT

- reply

🤝

2026-07-26 11:04:01 GMT

- reply

Do you have a cordn group for this? 👀

2026-07-26 11:02:21 GMT

Just wow 👀🔥
#nevent1q…4wla

2026-07-26 10:51:43 GMT

- reply

Also the deletion issue, in a normal relay anyone could delete anything because everyone share the same stream key, therefore deletion requests are valid. Maybe not important in a "trusted" environment, but critical flag in a public o big group

2026-07-26 10:37:17 GMT

- reply

Oh man 🫂

2026-07-26 10:24:51 GMT

- reply

This is really cool, congrats! 👏👏👏
But so far, Concord needs special relays, right? Or would it work fine with any existing relay?
I wrote this note the other day but never got a response. Maybe you can clear my doubts
#nevent1q…twku

2026-07-26 09:33:04 GMT

GM 🌞

2026-07-25 09:15:07 GMT

https://music.youtube.com/watch?v=-y37njM09uc

2026-07-24 20:40:41 GMT

- reply

Aaah looking forward to be there 🔥

2026-07-24 20:32:04 GMT

- reply

That's the point of the article, and why cordn is designed as it is designed

2026-07-24 18:45:43 GMT

- reply

You can use nostr.at for example: https://nostr.at/naddr1qvzqqqr4gupzqs9eep0ll6hurjkl3sc2fewgses07mjfwxsdcu3at2m8fd0xrdz3qy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjd9kx7tnwdaehgunfvyhxzurs9uqrzurjd9mxzar9943k7mtdw4hxjcmpw35k7mnn94hhvetj94c82cnvd93j66twveexzum5wf6kxar4wfjsc27qdm

2026-07-24 18:40:45 GMT

https://music.youtube.com/watch?v=-DenZhMCbC4

2026-07-24 17:22:14 GMT

This is great! Look at this flashy url https://cordn.net/p/gzuuus Just ping me there if you want to chat. If you want one like these answer in the comments of the release note 👌
#nevent1q…v8en

2026-07-24 12:40:33 GMT

- reply

This guy should listen to john vervaeke

2026-07-24 08:14:03 GMT

- reply

🧡

2026-07-24 08:08:34 GMT

- reply

U terrorist xD

2026-07-24 06:48:30 GMT

GM🖖

2026-07-23 17:45:17 GMT

Got it!
https://blossom.primal.net/f8b8c02af881e6c47ef7fdfa4ba20fd0337d0cfe0be590dcb55018e4d8b33c10.jpg
#nevent1q…c5hy

2026-07-22 21:19:12 GMT

- reply

I'm just at second episode, let's see

2026-07-22 20:58:37 GMT

Watching silo 👀

2026-07-22 19:04:47 GMT

https://music.youtube.com/watch?v=bysSGMYjM9k

2026-07-22 18:13:05 GMT

- reply

For real

2026-07-22 18:12:26 GMT

- reply

For real

2026-07-22 18:09:44 GMT

- reply

I love pi an all its digits

2026-07-22 16:38:35 GMT

- reply

2026-07-21 16:14:59 GMT

- reply

Yea, sure that's the same critique I had for nip-70 (protected events) since the beginning, but from my perspective, the key here is that if an implementation doesn't follow the spec is a bad implementation, and then we can discuss about sibyl attacks, but that's a different conversation.

2026-07-21 16:07:11 GMT

- reply

A protocol defines a contract that all implementations must follow.
If an implementation deviates from that, it is either a non‑compliant (bad) implementation or an entirely different protocol.
The “discretionary” aspect refers to enforcement: no external authority automatically guarantees compliance, so violations may go unchecked. When non‑compliance occurs, interoperability breaks

2026-07-21 15:48:28 GMT

- reply

It's just what the spec says, its not trust, just compliance with the protocol. An implementation doing something different is just not implementing the protocol

2026-07-21 15:46:53 GMT

- reply

Tl;dr: Protocols that claim to be “decentralized” because they are “just Nostr,” but if you look closely, they require specialized software (special relays) to run. Tbh I’m not opposed to needing special software to run your use case, specially if there is a good reason, although they reject anyone who goes straight in that direction.

2026-07-21 08:46:22 GMT

I expected a quality discussion, or at least some correction if I was wrong, but instead I got silence… It was a bit boring, and concerning, not gonna lie.
#nevent1q…pkxx

2026-07-20 18:32:16 GMT

https://music.youtube.com/watch?v=A0rknJFLOwc

2026-07-20 13:39:29 GMT

https://music.youtube.com/watch?v=vBeE3zRsOMg

2026-07-20 13:38:57 GMT

- reply

A server anyways ¯\_(ツ)_/¯

2026-07-20 13:37:38 GMT

- reply

Indeed... I can make it for my self 🔥

2026-07-20 13:37:12 GMT

- reply

👀👀
https://blossom.primal.net/1f308f8878c4e6dd12743e31e2f1c455a351a534f1d58f7db0c255631dc2be72.mp4

2026-07-20 13:34:09 GMT

- reply

Yea right? Mental karate

2026-07-20 13:32:40 GMT

- reply

https://blossom.primal.net/9438ac8ab00a252794cfb4ae0f3d7758fb82cd8bc80a1143076b044accbbcf03.mp4

2026-07-20 13:19:12 GMT

A little secret
#nevent1q…xyug

2026-07-20 13:14:53 GMT

- reply

Hahaha yea, sure, but that will potentially interfere with other standards, so it is a specialized relays, which essentially is a server with an specific function

2026-07-20 08:51:50 GMT

- reply

#nevent1q…hgkt

2026-07-20 08:51:28 GMT

- reply

Well, kindly pushing back on the "just like regular nostr" part. I've been reading through the spec and the Armada codebase, and that part doesn't really hold up. Concord relays need a specific configuration, as far as I can tell.
Concord reverses nip 59. A normal gift wrap has a random one-time author and the real recipient in the p-tag. Concord flips it: the author is a the stream key, and the p-tag is a random ephemeral key. Members read by the author, not by the p-tag. So it breaks on any relay doing the nip 59 "correct" thing, because nip 59 says relays SHOULD only serve kind 1059 to the marked recipient, and here nobody is the marked recipient. The spec admits it outright: "Communities must choose relays accordingly."
Also, if someone uses relays that prune or just nuke their db, that breaks the whole authority layer (roles, bans, channels all ride on 1059), and deletion gets messy because every wrap is authored by the same shared stream key that every member holds: on generic relays that honor author-based deletion, anyone can delete any message, or all of them, just by sending deletion requests, which from my POV is a huge hole.
In practice Armada runs on two default relays configured in the same way