Nostr notes by Technical Debt

Realized that a few years ago, still haven’t found “my own ...

2026-10-19T18:57:00Z

In reply to nevent1q…jxnn
_________________________

Realized that a few years ago, still haven’t found “my own game” yet

At least in bitcoin you can move your funds before it is too ...

2026-10-19T17:36:18Z

In reply to nevent1q…z850
_________________________

At least in bitcoin you can move your funds before it is too late, what are we going to do when the nsecs we have been raw dogging into random apps leak?

I hope they aren’t lactose intolerant. #nevent1q…egf6

2026-10-19T13:43:09Z

I hope they aren’t lactose intolerant.

quoting
nevent1q…egf6
Now all I can think about is emailing cheese to someone’s butt hole
nevent1q…5ac9

Nostr only here

2026-10-19T13:37:06Z

In reply to nevent1q…2leg
_________________________

Nostr only here

You are preaching to the choir. But poor people don’t care ...

2026-10-18T13:21:48Z

In reply to nevent1q…4qs7
_________________________

You are preaching to the choir.

But poor people don’t care about being tracked, since they have bigger problems to be worried about.

@npub1utx…50e8 you can’t just say “no relays accepted the ...

2026-10-17T23:17:40Z

utxo the webmaster 🧑‍💻🍁 (npub1utx…50e8) you can’t just say “no relays accepted the post” in a toast message and proceed to send the note to /dev/null when it fails to post.

I have a dumber idea: make it possible to vote people out of ...

2026-10-17T16:22:01Z

In reply to nevent1q…jgqm
_________________________

I have a dumber idea: make it possible to vote people out of office at any time for any reason.

I don’t Nostr Vault there though

2026-10-17T15:37:04Z

In reply to nevent1q…ztqg
_________________________

I don’t Nostr Vault there though

#nevent1q…dfek

2026-10-17T15:27:42Z

In reply to nevent1q…z5xj
_________________________

quoting nevent1q…dfek
I find it ironic to read that using the censorship-resistant protocol 🌚

#devstr

At some point it was expected to see nsfw here: the protocol specs even mention nsfw/content-warning tags as examples. Yet due to repetitive irresponsible Blossom servers use, it seems like nobody's currently willing to maintain them, specifically for nsfw. Or due to related political age verification cringe, for example: this may affect hosting providers / domain registrars at some point, suddenly requiring KYC from blossom admins as a result, if not worse. DCMA takedown letters are a risk as well. Or it's due to whatever other moral reasons too, I dunno.

I guess some of us believe that we shouldn't focus on this content right now, that this stuff should go last. Soft erotic nsfw possibly acceptable to many here, though. To me personally, if whatever legal nsfw content is properly distinguishable with the nsfw tag—this still should be okay. Whoever who specifically produces original legal content and publishes their nostr events with the tag could run a blossom server for themselves and for likely minded people; nobody can technically disallow that here. Some small fee from producers will also make it reasonable to maintain the server.

> dudes with no tact sending DMs

DMs probably not worth reading here right now for this purpose. I've seen pronouns/gender spec proposals, and I think it's useful here: an nsfw-oriented client could have ignored all DMs from those who didn't set their pronouns or have an irrelevant one. As well as disallow sending any DMs until the pronoun is not yet set. As well as adding the proper nsfw/content-warning tag on every event (both public and the DMs even) and ignoring all non-nsfw events (which will be simultaneously an incentive to not publish events without the appropriate tag at all). WoT and whatever would help too but they are ironically almost empty of those who'd want to send such DMs (which is not necessary a bad thing).

If we stop fighting this stuff and transform it properly, those who don't want nsfw content will see it less often as a result. I think it's a win-win.

What do you mean?

2026-10-17T14:06:09Z

In reply to nevent1q…9sj7
_________________________

What do you mean?

Something like this? https://basicswapdex.com/

2026-10-17T13:35:00Z

In reply to nevent1q…qljc
_________________________

Something like this? https://basicswapdex.com/

The problem with software loicenses is that they presume the ...

2026-10-17T12:15:24Z

In reply to nevent1q…tjw8
_________________________

The problem with software loicenses is that they presume the existence of IP (Imaginary Property).

Nostr event nevent1qqs883l53xhx7ktyfd55pz2ag90hmc9kxmdzdrjcu8e96v932w2k8wczyz465zw6k87rll7pgz0ak2938qev6sp3wpxymases5jl5l4yv6ldyyzyggt

2026-10-17T12:11:20Z

quoting
nevent1q…t035
ANOTHER DM APP FOR NOSTR 🚀 GM

I think keychat uses a different standard as well

2026-10-16T16:31:40Z

In reply to nevent1q…g2vk
_________________________

I think keychat uses a different standard as well

Seven ate nine 😭

2026-10-16T16:25:55Z

In reply to nevent1q…djvy
_________________________

Seven ate nine 😭

Nostr thread #nevent1q…8c64

2026-10-16T15:48:18Z

In reply to nevent1q…deuy
_________________________

Nostr thread

quoting nevent1q…8c64
Hiring collaborators to write some Nostr-based anticensorship software. Budget is small and not lucrative. This is not a startup and it is not going to turn a profit, but you will get massive dividends in lulz and the kingdom of heaven will open its gates to you. Still, you'll get paid.

I am not sure we need to write new software as much as we need to ...

2026-10-16T15:46:17Z

In reply to nevent1q…tqs4
_________________________

I am not sure we need to write new software as much as we need to glue together existing pieces into some kind of standardized stack.

Moaning

2026-10-16T13:15:01Z

In reply to nevent1q…cmfv
_________________________

Moaning

talvez isso te interesse https://github.com/p-e-w/heretic

2026-10-16T13:08:39Z

In reply to nevent1q…y47g
_________________________

talvez isso te interesse https://github.com/p-e-w/heretic

There’s a reason electric motors have been used in the ...

2026-10-16T13:03:50Z

In reply to nevent1q…tdp8
_________________________

There’s a reason electric motors have been used in the industrial sector since… basically ever since they were invented.

Sovereign naming systems. ...

2026-10-16T12:57:24Z

In reply to nevent1q…78qd
_________________________

Sovereign naming systems.

https://git.nostrdev.com/freakoverse/DNN/src/branch/main

https://spacesprotocol.org/

Why they matter https://buffrr.dev/blog/are-we-self-sovereign-pki-yet/

Isn’t that the dog abuser?

2026-10-15T23:31:12Z

In reply to nevent1q…r5yl
_________________________

Isn’t that the dog abuser?

You guys really use smoke alarms in homes? I thought it was a ...

2026-10-15T23:21:19Z

In reply to nevent1q…wrfl
_________________________

You guys really use smoke alarms in homes? I thought it was a movie thing…

Reject ICANN’s DNS, embrace freakoverse/DNN or Spaces Protocol ...

2026-10-15T18:45:24Z

In reply to nevent1q…ps0u
_________________________

Reject ICANN’s DNS, embrace freakoverse/DNN or Spaces Protocol (the jury is still out on which one gains more traction) ☺️

I didn’t know they made wire nuts that big…

2026-10-15T16:42:46Z

In reply to nevent1q…gces
_________________________

I didn’t know they made wire nuts that big…

Como assim

2026-10-15T16:31:23Z

In reply to nevent1q…wnwt
_________________________

Como assim

This is not using the chain as a database, it has around the same ...

2026-10-15T13:39:29Z

In reply to nevent1q…nvk0
_________________________

This is not using the chain as a database, it has around the same footprint as OTS, which no sane person would classify as bloat. Only the proof of your root is commited to the chain, and that can be merged with thousands of other proofs into the same 32byte payload, again very similar to OTS.

Your records are distributed through certrelays (which work much like nostr relays), NOT through the blockchain.

DNN, Spaces Protocol…

2026-10-15T12:44:02Z

In reply to nevent1q…82lk
_________________________

DNN, Spaces Protocol…

I found out about nostr when I asked ShartGPT for ZeroNet ...

2026-10-15T03:57:22Z

In reply to nevent1q…mkgr
_________________________

I found out about nostr when I asked ShartGPT for ZeroNet alternatives.

I don’t see it being a problem by itself, the payload is ...

2026-10-15T03:31:58Z

In reply to nevent1q…kp0e
_________________________

I don’t see it being a problem by itself, the payload is smaller than an average transaction (if I understood things correctly).

Unless you mean that would increase the precedent for getting more things on chain in general, which yeah, that could be a problem.

Another con I see with DNN is that you are forced to append some ...

2026-10-15T01:58:42Z

In reply to nevent1q…kuqs
_________________________

Another con I see with DNN is that you are forced to append some “gibberish” to what ought be human names.

But on the burning of bitcoin and chain data, that is only true for the creation of root namespaces (which are working kind of like TLDs here), everything else is handled offchain.

On a surface level it is “just” another decentralized naming ...

2026-10-15T01:07:49Z

In reply to nevent1q…893n
_________________________

On a surface level it is “just” another decentralized naming registry, but the way they’ve achieved it is the interesting part for me https://buffrr.dev/blog/are-we-self-sovereign-pki-yet/

Interesting, how does that compare to spaces protocol?

2026-10-14T21:19:57Z

In reply to nevent1q…5j4p
_________________________

Interesting, how does that compare to spaces protocol?

https://youtube.com/shorts/nlfCGqnN01k

2026-10-14T19:06:43Z

https://youtube.com/shorts/nlfCGqnN01k

Bem vinda

2026-10-14T18:36:02Z

In reply to nevent1q…3r7j
_________________________

Bem vinda

Inkan.cc nostr search engine is possibly one of the most goated ...

2026-10-14T16:46:32Z

Inkan.cc nostr search engine is possibly one of the most goated nostr things I have ever experienced. #grownostr

I think someone might actually be working on something like that ...

2026-10-14T14:25:27Z

In reply to nevent1q…8cr6
_________________________

I think someone might actually be working on something like that (zeronet for nostr) already, but I can’t remember who.

Maybe it was one of the FIPS guys, judging by the podcasts.

Are you on web, android or iOS? Inb4: no client does blossom ...

2026-10-14T14:17:34Z

In reply to nevent1q…3z2m
_________________________

Are you on web, android or iOS?

Inb4: no client does blossom resolution and the primary link is just loading intermittently

And then what would be the following steps? Or do we expect them ...

2026-10-14T14:15:26Z

In reply to nevent1q…0k63
_________________________

And then what would be the following steps? Or do we expect them to figure out the rest on their own?

I have a suspicion some people would refuse even if the solution ...

2026-10-14T14:05:35Z

In reply to nevent1q…xnx3
_________________________

I have a suspicion some people would refuse even if the solution was 100% bitcoin based (through bitcoin script, bitvm or whatever).

But this leaves us to the sad conclusion that nostr identities will forever remain disposable, nsec leaks will make the headlines and burn everyone out of nostr eventually.

We can’t keep producing marketing material about how sovereign a nostr identity is when it lacks most of the properties of a decent PKI.

ShartGPT seemed to be drinking too much of Ethereum’s kool aid ...

2026-10-14T13:47:43Z

In reply to nevent1q…j68c
_________________________

ShartGPT seemed to be drinking too much of Ethereum’s kool aid at first until I called it on its BS. I guess there is a lot of “finality” glazing in the dataset.

Still, Timestamp linking in particular seems to be of the biggest interest:

“The key insight is that Rootstock can use information published in Bitcoin’s independently maintained blockchain to constrain attacks against Rootstock itself.”

And it works without disrupting uptime like Armadillo.

In fact it is Ethereum who has its history tainted by chain reorgs. And finality is nothing more than a RPC tag on a PoS system that, under certain circumstances may lead to accidental hardforks and not knowing which chain to trust from a certain point onwards. That is a bigger problem than plain old DoS.

Another thing to consider is that Rootstock is the oldest (Jan 2018) bitcoin sidechain, which also makes it older than ethereum (!!!) given the PoS migration happened in 2022.

So yeah, liquid is newer (October 2018) and relied on a federation based peg in (while rootstock had permissionless pegins from the start), so the fact that rootstock has no recorded attack attempts (nor incidents like ethereum) seems to be more because of good engineering than not being a big enough target.

The identity of Ethereum validators isn’t public either. For ...

2026-10-14T12:35:04Z

In reply to nevent1q…v0ar
_________________________

The identity of Ethereum validators isn’t public either. For all I know a state could already have the majority of votes/validators, distributed in sock puppets which could be coordinated to make an attack at any given time. And that attack could be anything from rejecting certain transactions to actually splitting the network in two and then the “community” tries to force their opinion on what is ethereum or what is ethereum classic 2. If you had done revocations or delegations in the meantime, good luck hoping the community would pick the chain with your operations in. Compare that with a chain which always has a confirmed history but maybe under certain conditions could become read-only for a while. Sure it would suck but there would be no ambiguity to be solved subjectively, which sounds like a better property for an identity system.

This might sound unlikely but so does converting around more than 45% of bitcoin’s hash rate into bad actors. Even if you think they have individually low interest in the sidechain, that is still a huge amount of hash you would need.

Another point is that the surface area of complexity of a PoS system is bigger than PoW, and Ethereum is already tainted by consensus bugs and accidental forks.

As for the peg outs, there are working to phase out the federation model and make it so the chain does the peg outs, just like it handles the peg ins without touching a federation already. They are blocked on the bitcoin (bitvm2/opcodes) side of things, really.

The web just sucks man. ZeroNet made it look easy back in the ...

2026-10-14T06:25:12Z

In reply to nevent1q…y4uu
_________________________

The web just sucks man.

ZeroNet made it look easy back in the day, but then it runs as a daemon on your machine handling the p2p stuff in the background, but worked with any browser.

Brave has native support for IPFS but IPFS is slow as balls.

Only other option I can think of right now is:
- do server side rendering of the home page (client updates the dom afterwards)
- since the server rendered that page before it should be able to fech the first 30 seconds of each video and cache that
- do some HLS wizardry to switch the streams

Actually… I guess I am reinventing the library you mentioned.

Maybe we should just reinvent zeronet with nostr and nsites and whatever more, that way one daemon can serve as a local relay for caching/redistributing the nsites you visit and handle the p2p shit.

LTE is not the only possible transport. 5G has some low power IoT ...

2026-10-14T05:54:23Z

In reply to nevent1q…jm2q
_________________________

LTE is not the only possible transport.
5G has some low power IoT mode and actually, why restrict ourselves to mobile networks?

You could just broadcast a Bluetooth beacon intended to be transported by devices on the find my network, which means basically any iPhone or android around can do the internet hop for you.

The NAT issues only apply to people behind CGNATs which also ...

2026-10-14T05:48:48Z

In reply to nevent1q…wqfc
_________________________

The NAT issues only apply to people behind CGNATs which also don’t have IPv6… which should be precisely nobody, unless of course some ISPs are violating some rules there, which could get them fined etc.

But you can simulate a CGNAT at home, assuming you have IPv4 connectivity, just connect a second router onto your main router and then tada, you have double NAT, which is basically what CGNAT is. If you want more fun chain a third router and then you effectively have a double nat behind a cgnat, which now that I think of it shouldn’t be too uncommon either, given the amount of poorly set up “wifi range extenders” out in the blue and/or people manually disabling ipv6 or whatever.

Yeah people didn’t seem to catch on weight differences from ...

2026-10-14T04:58:59Z

In reply to nevent1q…tml7
_________________________

Yeah people didn’t seem to catch on weight differences from some videos I saw, some had a huge ass battery inside.

Still, some Samsung TV controllers claim to harvest power from thin air (actually induced voltage from radio waves or whatever), that could be one way of powering as well. The attacker certainly can wait for that kind of system to slowly charge a capacitor.

I am rather surprised at how these devices seem to have a number of exposed pads, if you can’t design an obstructed silicon like Apple at the very least give the whole thing a resin bath or something.

Pretty sure it could be worked around with a joule thief, a ...

2026-10-14T04:01:32Z

In reply to nevent1q…vrl9
_________________________

Pretty sure it could be worked around with a joule thief, a battery… but yeah, better than nothing I guess.

Why bother with starlink? Just set a local mesh and keep away ...

2026-10-14T03:21:21Z

In reply to nevent1q…eu9h
_________________________

Why bother with starlink? Just set a local mesh and keep away from the internet at large…

Tor is a CIA honeypot.

2026-10-14T03:19:06Z

In reply to nevent1q…e5k5
_________________________

Tor is a CIA honeypot.

This is uuuuge #nevent1q…3npv

2026-10-14T02:35:46Z

This is uuuuge

quoting
nevent1q…3npv
I'm going to use a post by npub1g55mzg9z4mejau0tajkc9ajw29cqe2n9qm5ugz4maknelpzuzttqtnxdg2 as a great example of how I've just integrated the amazing nostr wiki tool in to Plume.

An interesting post is written. Thinks I, to myself, I wonder what a pinhole camera is? So I press the W button below the note, the text comes up, I select the word I'm interested in, and search the wiki, which returns the result and I gets to learn a thing.

Laeserin (npub1m4n…c2jl) npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 npub1q6ya7kz84rfnw6yjmg5kyttuplwpauv43a9ug3cajztx4g0v48eqhtt3sh thankyou!! You guys did amazing work! God I hope this note renders properly!

I honestly don’t know how to onboard people anymore… half the ...

2026-10-14T02:33:05Z

In reply to nevent1q…gmtt
_________________________

I honestly don’t know how to onboard people anymore… half the wallets look like ass, the other half behave like ass and the third half (off by one errors are hard) looks and behaves like ass.

And then there’s the question of which poison to recommend. Spark? Cashu? A whole ass node full of complexity which still needs purchasing liquidity from a third party?

Ignore lightning entirely and tell them to run a plain and boring bitcoin wallet like bluewallet?

So many questions…

Also, did the join button detect the browser signer and skipped ...

2026-10-14T02:06:44Z

In reply to nevent1q…ldtg
_________________________

Also, did the join button detect the browser signer and skipped the explanation about nostr and how to login in a popup or is it missing that altogether

Why does it say “Connect to relays to discover games” right ...

2026-10-14T02:04:39Z

In reply to nevent1q…tsey
_________________________

Why does it say “Connect to relays to discover games” right in the front page?

We shouldn’t be forcing jargon like that, especially so early.

I think every nostr user would implode if they had to be forced ...

2026-10-14T01:59:10Z

In reply to nevent1q…v24x
_________________________

I think every nostr user would implode if they had to be forced into using a single client for a week.

The humble client devs seeing their appstore age rating rise to ...

2026-10-14T01:47:47Z

The humble client devs seeing their appstore age rating rise to 18+: :Sadge:

quoting
nevent1q…qy72
New site update just dropped and a dedicated relay!

Https://pornstr.net
wss://relay.pornstr.net

Honestly I wouldn’t take blossom seriously for any long form ...

2026-10-14T01:39:10Z

In reply to nevent1q…tjwc
_________________________

Honestly I wouldn’t take blossom seriously for any long form video usecase, most clients don’t even seem to be doing blossom resolutions… treat it as if it was a mere a centralized http server.

Your best bet seems to be webtorrents indeed.

FIPS is good as is, but if you want to explore similar networks ...

2026-10-14T01:26:36Z

In reply to nevent1q…jhdh
_________________________

FIPS is good as is, but if you want to explore similar networks with an already existing user base, check cjdns and Yggdrasil.

Also see my reply

quoting nevent1q…g39v
They should be able to scale better than DHT based meshes, or at least that is what led one of the co-creators of CJDNS into creating Yggdrasil.

Basically the problem was, since cjdns is source routed and relies on a DHT, the routing table would eventually grow to the point that nodes wouldn’t be able to route packets anymore (at least without asking for a bigger/“routing node” for a route), while Yggdrasil (and our nostr friend fips (npub1y0g…00ly)) elect a node as the network root and then assign dynamic coordinates based on your position relative to said root, and then nodes try to find the best next hop based on local information (and a worst case scenario route is always guaranteed).

I may have gotten a thing or two wrong so might want to check out https://yggdrasil-network.github.io/

I have a growing suspicion that IPFS isn’t fundamentally wrong, it just has/had severe implementation issues, to the point that I guess some vibecoder could get it working better than whoever is at protocol labs, but they have brand recognition so good luck to whoever attempts taking them down.

Nostr event nevent1qqsvg9cdfjkjg449t5rdg8527lawquzc5q7rtgxfldrc9j2j9wtn8aczyz465zw6k87rll7pgz0ak2938qev6sp3wpxymases5jl5l4yv6ldy9spjz9

2026-10-14T00:56:33Z

quoting
nevent1q…0nnc
I don't think the Monerobros even care about scarcity or market cap, they just care about some medium of exchange they can transact in that's "private" and that's the value driver?

It actually means that their blockchain isn’t held hostage by a ...

2026-10-14T00:53:13Z

In reply to nevent1q…z33p
_________________________

It actually means that their blockchain isn’t held hostage by a handful of miners and we should congratulate them on that.

Why would a State or central bank try to develop a cpu based asic when they can just delist monero from every exchange on earth and use the surveillance apparatus they already have to keep an eye on who might be exchanging bitcoin for monero? Or setup honeypots or literally just plain brute force? That is what they always do.

And I’m pretty sure ASIC developers wouldn’t be sitting on the opportunity of printing literal cash if they thought it was possible to do so.

This is goated.

2026-10-14T00:34:53Z

In reply to nevent1q…7qcw
_________________________

This is goated.

After a session of AI psychosis I feel like I’m more on side of ...

2026-10-13T20:15:35Z

In reply to nevent1q…n54j
_________________________

After a session of AI psychosis I feel like I’m more on side of Rootsocks than before.

Ethereum finality is only relevant in the context of a PoS chain, Rootstock being PoW means you can just count confirmations instead.

As for reorgs, Rootstock has multiple preventive measures (Armadillo, Timestamp linking with Bitcoin’s main chain, transparent double spending trails etc), mostly trading availability for consistency (it stops validating blocks when an attack is detected).

Basically, the worst case scenario for ethereum is solved through “social recovery”, meaning the community has to pick a chain to call ethereum arbitrarily (this already happened in the past due to consensus bugs).

Now Rootstock, even if its defenses fail, worst thing that could happen is what, a depeg? Sure, that would suck for them but for inkan there wouldn’t be the subjective problem of choosing which delegation history is canonical. The consensus rules of PoW take care of that.

I do that sometimes but I feel like it could get annoying rather ...

2026-10-13T17:37:13Z

In reply to nevent1q…9hfj
_________________________

I do that sometimes but I feel like it could get annoying rather quickly. Or at least very disjointed, reports could get forgotten and I wouldn’t if and when they do get fixed.

I’m used to following issues on GitHub that are old enough to spell the abc and count to one hundred 😂

Thanks, but I should consider creating proper bug reports instead ...

2026-10-13T17:26:53Z

In reply to nevent1q…vpp7
_________________________

Thanks, but I should consider creating proper bug reports instead of just bitching to the wind.

I just didn’t want to dox myself opening issues on GitHub… let’s hope more nostr devs get banned from there so they move their issue tracking into nostr :EZ: :EZ:

Nostur is not loading that image for me. So far only ditto and ...

2026-10-13T17:17:26Z

In reply to nevent1q…5dd7
_________________________

Nostur is not loading that image for me. So far only ditto and yakihonne did the trick for me, not even nostrich, which posted the event with the fallabck url and everything, was able to load the image after I closed and reopened it.

I think some people will just outright refuse anything that ...

2026-10-13T17:15:03Z

In reply to nevent1q…u0gp
_________________________

I think some people will just outright refuse anything that doesn’t resolve 100% within the broken relay ecosystem, which I’m convinced is impossible. So… 🤷‍♂️

There’s a gap between socializing and fucking.

2026-10-13T17:09:24Z

In reply to nevent1q…wx8v
_________________________

There’s a gap between socializing and fucking.

Yes, Rootstock is 100% EVM compatible. Some arguments for that: - ...

2026-10-13T17:07:28Z

In reply to nevent1q…9203
_________________________

Yes, Rootstock is 100% EVM compatible. Some arguments for that:
- trusting the PoW of basically one network: since rootstock is merge mined with bitcoin and OTS already depends on bitcoin
- payment of delegation fees in a currency closer to being money/more holders/etc; getting some btc into rootstock is a trustless operation (and going back could be made to not require a federation if only a certain op code would be added into bitcoin or whatever, that’s besides the point)

But on a surface level a technical argument I can think for bitcoin script (which works against both ethereum and rootstock) is that you are already using one blockchain for OTS, using a second blockchain is added complexity/a second single point of failure/whatever.

Wen iOS

2026-10-13T11:37:58Z

In reply to nevent1q…u45j
_________________________

Wen iOS

Weird, YakiHonne worked for me. That and ditto. The rest of the ...

2026-10-13T11:31:12Z

In reply to nevent1q…awwg
_________________________

Weird, YakiHonne worked for me. That and ditto. The rest of the list… yeah, nothing.

If you are really curious you can view the note json and copy the primal blossom fallback url and paste in a browser. Then you can call yourself human blossom resolution!

Imagine trying to find women in a sausage protocol.

2026-10-13T10:58:33Z

In reply to nevent1q…8xe4
_________________________

Imagine trying to find women in a sausage protocol.

If your client can’t load this image, it’s not doing blossom ...

2026-10-13T10:54:30Z

If your client can’t load this image, it’s not doing blossom resolutions… in fact it is not even reading the fallback field from the note json.

quoting
nevent1q…5e36
For the curious about my word selection

🫪

2026-10-13T01:15:23Z

In reply to nevent1q…g0n5
_________________________

🫪

For the curious about my word selection ...

2026-10-13T00:44:53Z

In reply to nevent1q…55m2
_________________________

For the curious about my word selection

FIPS is more similar to cjdns’ younger cousin, Yggdrasil. It ...

2026-10-13T00:25:05Z

In reply to nevent1q…c7ee
_________________________

FIPS is more similar to cjdns’ younger cousin, Yggdrasil.

It should be possible to bridge all three, but I haven’t seen anyone trying it yet.

Since they don’t conflict with each other people just prefer to run them on dual stack I guess.

Finally being too poor to afford a hardware wallet paid off. A ...

2026-10-12T23:50:09Z

In reply to nevent1q…djrp
_________________________

Finally being too poor to afford a hardware wallet paid off.

A used android phone sells for peanuts where I live, guess I shouldn’t have been worried about not being able to buy one of the fancy hardware wallets.

Good, now do @npub1y0g…00ly :EZ:

2026-10-12T21:25:28Z

In reply to nevent1q…l94c
_________________________

Good, now do fips (npub1y0g…00ly) :EZ:

Do you think the smart contract could be ported to bitcoin ...

2026-10-12T20:52:12Z

In reply to nevent1q…py0s
_________________________

Do you think the smart contract could be ported to bitcoin script?

But do you think it would be better received or not?

2026-10-12T19:11:18Z

In reply to nevent1q…pq9a
_________________________

But do you think it would be better received or not?

You don’t even need to speculate about the existence of higher ...

2026-10-12T19:05:05Z

In reply to nevent1q…x23s
_________________________

You don’t even need to speculate about the existence of higher beings for this.

Our inherent inability to perfectly perceive the world around us is not proof that there aren’t universal truths.

Staying open to questioning perceived truths is what pushes us towards the real deal, not outright denying them.

Would it make any difference had he deployed the smart contract ...

2026-10-12T18:52:53Z

In reply to nevent1q…cnhy
_________________________

Would it make any difference had he deployed the smart contract on bitcoin rootstock instead of Ethereum?

If you apply that assertion into itself the conclusion is that ...

2026-10-12T18:42:51Z

In reply to nevent1q…hmc3
_________________________

If you apply that assertion into itself the conclusion is that there can be things that are objectively true or false.

Relativism is one hell of a drug.

Yeah there is a smart contract because OTS + nostr alone would ...

2026-10-12T18:30:45Z

In reply to nevent1q…ezlp
_________________________

Yeah there is a smart contract because OTS + nostr alone would leave the system vulnerable to some attack scenarios. I won’t pretend to understand why that is the case but nothing seems to prevent us from deploying the contract on Rootstock instead.

quoting
naddr1qq…u70r

NIP Proposal

draft optional

This NIP specifies online identities whose private key can be created in cold storage and stay there permanently. The key never has to touch an internet-connected device, and does not have to be kept close at hand. The identity can nonetheless be used easily for everyday online authentication, such as posting, replying, messaging, or signing in to services.

1. How it works

The identity-securing key never signs Nostr events itself. It delegates signing authority to delegatee keys, which handle the everyday signing on its behalf. If a delegatee key is lost or stolen, it is replaced, and the identity is untouched.

2. Delegations between keys

Delegations are time-indexed two-place relations. Between any two key pairs, at any moment, the first either delegates signing authority to the second or it does not. When it does, the second key is authorized to sign on the first's behalf. When it does not, the second has no such authority.

Delegations are either direct or indirect. A direct delegation arises when one key has expressly declared that it delegates signing authority to another. An indirect delegation arises because the relation is transitively closed: if X delegates to Y and Y delegates to Z, then X indirectly delegates to Z. This is what lets an identity be built as a chain (master → intermediate → signer), so that events signed by the bottom key are attributed all the way up to the master, while the master, having signed the top link once, retires to cold storage.

3. How a direct delegation is created

A direct delegation from key pair X to key pair Y is created when both key pairs sign a Declaration of Delegation of Signing Authority, by which X declares that it delegates signing authority to Y and Y declares that it accepts. The signed declaration is then recorded on-chain (the reference implementation uses Ethereum). The delegation begins at the time of the block in which the declaration was recorded, and remains in effect until it is revoked.

One special case: this holds only if neither X nor Y has previously permanently invalidated itself (§5). If either has, no delegation is created, even though the declaration sits on-chain.

As part of the declaration, X and Y also specify whether X can revoke the delegation unilaterally or whether Y's consent is required. The default is unilateral revocation by X, and it is the right default for most users: if Y's key is ever lost, X can still revoke it alone. Were Y's consent required, a lost Y could never be revoked, because Y would no longer be available to sign.

4. How a direct delegation is terminated

A direct delegation from X to Y is terminated when X signs a Declaration of Revocation of Signing Authority and records it on-chain, with Y's signature too if the original delegation required it. The delegation terminates at the time of the block in which the revocation was recorded. Everything Y signed while the delegation was in effect stays attributed to X; nothing it signs afterward does. A stolen signer therefore damages only the window between key compromise and revocation, and that window is the user's to close.

When a delegation and a revocation between the same X and Y land in the same block, the revocation is by convention treated as occurring first and the delegation thereafter. The convention is a tiebreaker for cases that block timestamps cannot order.

5. Permanent key invalidation

The third declaration is the Declaration of Permanent Invalidation of a Key Pair, signed by a key pair against itself, declaring that from then on it can no longer participate in any direct delegation, as delegator or delegatee. Once recorded on-chain, it takes effect at the time of its block. From that point, all existing direct delegations involving the key are terminated, and no new one involving it can come into existence, even if a declaration naming it is later recorded.

Its main use is invalidating a compromised master key. Such a key has no delegator above it, so ordinary revocation is unavailable; permanent invalidation lets its owner withdraw it from the system entirely.

6. Delegation timelines

A client can read the three kinds of declaration from the chain and, for any pubkey and any past moment up to the present, compute the direct delegations that pubkey was involved in at that moment. The indirect ones follow by transitive closure. So for any pubkey a client can compile a complete timeline of every direct and indirect delegation it has ever been involved in, and trace each back to the declaration that established it. Because the rules are fixed and the data is public, every client computes the same timeline, and no server has to be trusted to report it.

7. Bitcoin timestamping of events

Attribution needs an objective, auditable rule for when the signing of each event is deemed to have occurred. A self-declared created_at proves nothing on its own.

Events are anchored to Bitcoin using OpenTimestamps (OTS). An OTS proof for an event establishes that the event and its signature existed by the time of a specific Bitcoin block. An event's created_at is then treated as its objective signing time when a proof shows the event and its signature existed shortly after that time. The length of the "shortly after" window is configurable; the reference implementation defaults to four hours. Events without such a proof are treated as if they carried no valid signature at all: they are not displayed, and are attributed to no one.

A proof over the event id alone would show only that the event's contents existed by the attested block, not that anyone had yet signed them. Binding the signature into the proof as well shows that the signature itself existed by then, which is what an objective signing time requires. These proofs are published as kind 31045 events (§12).

8. Attribution of events

We now know, for any past time T and any two keys X and Y, whether X delegated (directly or indirectly) to Y at T; and for any event Y signed with both a valid signature and a valid OTS anchor, we have an objective signing time. Together these give a well-defined attribution rule:

An event E is attributed to a key X if and only if some key Y validly signed E at a time T and, as of T, X delegated signing authority to Y.

So a text note signed by a delegatee Y during a valid delegation period from X appears on X's timeline and is displayed there under X's profile, as if posted by X, even though X's own key never signed it.

9. Two profiles, one identity

You log in with your signer key and sign events with it, exactly as in any other Nostr client. Those events appear on the signer's own profile, and in addition on the profile of each of its delegators, up to your top-level identity.

You set the signer's profile by publishing a kind-0 event as usual. Separately, a signer can also set a profile for each of its current delegators, so that a top-level identity can present a face to the world without signing any event itself. This delegator-profile mechanism is kind 31065 (§12).

Your identity's profile is what you present to the world. Others should follow and interact with the identity, not with the signer beneath it. The signer is ephemeral and expected to be replaced; the identity is permanent, and is the thing followers should attach to.

10. Disavowal

When making a delegation declaration, the delegator may declare an avowal start time and an avowal end time. When making a revocation declaration, the revoker may declare a disavowal start time and a disavowal end time. A start time of zero is interpreted as the time at which the declaration was recorded on-chain; an end time of zero means unbounded.

For keys X and Y, take the latest delegation or revocation declaration between them recorded before any permanent invalidation of either (§5). If it is a delegation declaration, X avows Y's actions at exactly the times T inside its avowal window; if a revocation declaration, at exactly the times T outside its disavowal window; provided, in both cases, that X directly delegated to Y at T. Y's actions at T are the events Y validly signed with objective signing time T (§7).

Avowal composes along delegation paths: X currently avows S's actions at T if the relevant declaration between X and S avows them directly, or if, for some key Y, X avows Y's actions at T, X avows Y's actions at the present moment, and Y currently avows S's actions at T.

Clients can filter events whose signing the identity currently disavows out of the identity's timeline, or display them with a disavowal badge.

11. Re-ratification

A disavowed window covers everything the disavowed key signed within it, including events whose signing was caused by the identity's legitimate owner. The identity can in that situation make a kind 31066 re-ratification declaration as described in §12.3 below, specifying the events it re-ratifies in the e tags of that declaration. If the declaration is valid and effective, a client treats these events as re-ratified, until a disavowal recorded after the declaration's anchoring block prevails over it (§12.3) or a later declaration governs in its place.

12. Event kinds

This NIP defines three addressable event kinds (kinds 30000 to 39999 in NIP-01, where the latest event for a given (pubkey, kind, d-tag) replaces any earlier one).

Kind Name d tag Signed by

31045 Bitcoin timestamp id of the referenced event any party

31065 Attributed profile the delegator's pubkey a delegatee

31066 Re-ratification the re-ratifying pubkey an avowed key

12.1 Kind 31045: Bitcoin timestamp

A 31045 event carries an OpenTimestamps proof for another event (§7). It is addressable by the referenced event's id, so a consumer finds the proof for an event E by querying kind 31045 with #d = [E.id], whoever published it. Any valid proof for E is as good as any other, because the proof rests on Bitcoin and not on its publisher.

Tag Required Meaning

d yes Id of the referenced event. The addressable key.

s yes Signature of the referenced event. With d, binds the proof to a signed event, not just an id.

p no Author pubkey of the referenced event.

b no Bitcoin block height of the attestation, or not_yet_available while pending.

t no Bitcoin block time (unix seconds), or not_yet_available while pending.

c no created_at of the referenced event, when known.

alt no NIP-31 summary, e.g. Complete Bitcoin Timestamp.

content is the base64-encoded OpenTimestamps (.ots) proof. Its leaf must commit to sha256(referenced_id || referenced_signature), the concatenation of the referenced event's 32-byte id and 64-byte signature. A consumer should verify the proof against its own view of the Bitcoin chain rather than rely on a relay having accepted it.

Only d and s, together with a verifiable content proof, are required to verify a timestamp. Every single-letter tag (d, p, s, b, t, c) is relay-indexed, so it can also serve as a query key, for example finding proofs by referenced author (#p) or by anchoring block (#b). b and t additionally duplicate what the proof itself attests; alt is not indexed and serves only as a NIP-31 display label.
{
  "kind": 31045,
  "tags": [
    ["d", "<referenced-event-id>"],
    ["p", "<referenced-event-author>"],
    ["s", "<referenced-event-signature>"],
    ["b", "<bitcoin-block-height>"],
    ["t", "<bitcoin-block-time>"],
    ["alt", "Complete Bitcoin Timestamp"],
    ["c", "<referenced-event-created-at>"]
  ],
  "content": "<base64 .ots proof committing to sha256(id||sig)>"
}
12.2 Kind 31065: Attributed profile

A 31065 event is a profile for one key, published by another: how an identity that never signs anything nonetheless presents a face to the world (§9). Its d tag is the delegator's pubkey, the identity the profile describes, while the event is signed by a delegatee authorized to sign for it. The defining property is that event.pubkey, the signer, is not the subject d. A consumer must confirm, against the delegation timeline of §6, that the signer was a current delegatee of the subject before honoring the profile; one signed by a non-delegatee is ignored.

Tag Required Meaning

d yes The subject: the delegator's pubkey.

alt yes The exact string Attributed profile.

content is a JSON object carrying the subject's presentation. Its kind-0-style fields (name, display_name, about, picture, banner, website, nip05, lud16) mean what they mean in NIP-01 and NIP-05. It may also carry the subject's follow list, mute list, and a map giving relay lists for the members of the identity's delegation network (the keys tied to it by delegation), so a client can present and route for the identity without a further fetch.
{
  "kind": 31065,
  "pubkey": "<delegatee-that-signs>",
  "tags": [
    ["d", "<delegator-pubkey-the-profile-is-for>"],
    ["alt", "Attributed profile"]
  ],
  "content": "{\"name\":\"…\",\"display_name\":\"…\",\"about\":\"…\",\"website\":\"…\",\"nip05\":\"…\",\"picture\":\"…\",\"relay_lists_by_pubkey\":{\"<pubkey>\":{\"readWriteRelays\":[[\"r\",\"<relay-url>\",\"<scope>\"]],\"favoriteRelays\":[\"<relay-url>\"],\"relaySets\":[{\"id\":\"…\",\"name\":\"…\",\"relayUrls\":[\"<relay-url>\"]}]}},\"publicly_muted_pubkey_hex_ids\":[\"<muted-pubkey>\"],\"current_snapshot_of_dir_indir_followed_pubkey\":[[\"p\",\"<followed-pubkey>\"]]}"
}
Because 31065 is addressable, the current profile for an identity is simply the latest one whose d is that identity, signed by a key that is currently its delegatee. When the signer is rotated, the new signer republishes, and the identity's face carries across the change unbroken.

12.3 Kind 31066: Re-ratification declaration

A 31066 event can be used by key A to re-ratify an event signed by key B with objective signing time T (§7), where A currently disavows actions taken by B at T (§10). The d tag contains the re-ratifying pubkey and each e tag is the id of a re-ratified event. The re-ratification is valid only if the 31066 event is signed by a key whose actions the re-ratifying key currently avows (which includes the re-ratifying key itself), and only if no e tag contains the declaration's own event id. The 31066 event must be submitted for Bitcoin timestamping and is effective starting from the time of the block in which its proof is anchored. If there are multiple valid and effective 31066 events with the same re-ratifying pubkey in their d tag, the one with the latest created_at governs. A re-ratification overrides only disavowals recorded on-chain before the time of its anchoring block; a disavowal recorded after that time prevails over the re-ratification.

Tag Required Meaning

d yes The re-ratifying pubkey.

e yes, repeated Id of a re-ratified event, one tag per id.

alt yes Re-ratification declaration
{
  "kind": 31066,
  "pubkey": "<signing-key>",
  "tags": [
    ["d", "<re-ratifying-pubkey>"],
    ["e", "<re-ratified-event-id>"],
    ["e", "<re-ratified-event-id>"],
    ["alt", "Re-ratification declaration"]
  ],
  "content": ""
}
13. Reference implementation

Inkan (https://www.inkan.cc) implements this specification as a working Nostr client and a cooperating relay at wss://relay.inkan.cc. Delegation, revocation, permanent invalidation, avowal, and disavowal are recorded by an Ethereum contract deployed at 0x385C0A272b1f44687cb360557b25827bD7CdB7eb, which is the normative reference for the exact on-chain declaration encoding. A separate, network-disconnected "Management Utility" generates keys and signs declarations on an air-gapped machine, so a master key can be created and used to bootstrap an identity without ever touching a networked host.

Kind	Name	`d` tag	Signed by
`31045`	Bitcoin timestamp	id of the referenced event	any party
`31065`	Attributed profile	the delegator's pubkey	a delegatee
`31066`	Re-ratification	the re-ratifying pubkey	an avowed key

Tag	Required	Meaning
`d`	yes	Id of the referenced event. The addressable key.
`s`	yes	Signature of the referenced event. With `d`, binds the proof to a signed event, not just an id.
`p`	no	Author pubkey of the referenced event.
`b`	no	Bitcoin block height of the attestation, or `not_yet_available` while pending.
`t`	no	Bitcoin block time (unix seconds), or `not_yet_available` while pending.
`c`	no	`created_at` of the referenced event, when known.
`alt`	no	NIP-31 summary, e.g. `Complete Bitcoin Timestamp`.

Tag	Required	Meaning
`d`	yes	The subject: the delegator's pubkey.
`alt`	yes	The exact string `Attributed profile`.

Tag	Required	Meaning
`d`	yes	The re-ratifying pubkey.
`e`	yes, repeated	Id of a re-ratified event, one tag per id.
`alt`	yes	`Re-ratification declaration`

That explains a lot. #nevent1q…9jy4 #nevent1q…m4qw

2026-10-12T17:53:06Z

That explains a lot.

quoting nevent1q…9jy4

Money printer goes brr.

nostr:nevent1qqs8wx2rxcg0wnsqtjzmrrlffdukmsk8yt9x66jx0saekrky5j4nztqzyzq9kd8hpzphm7e70uzczkk9wczkgc5ttr26pn5rnn9mdmekyravxqcyqqqqqqgpy3mhxue69uhhqatzd35kxtnrwfhhxarj9e3k7mf0vfjkzcm0dckh2mtzwfss8qm4qw

Yes, at https://www.inkan.cc

2026-10-12T17:48:58Z

In reply to nevent1q…pnzj
_________________________

Yes, at https://www.inkan.cc

Laughing on the outside, but screaming internally because the ...

2026-10-12T17:47:14Z

Laughing on the outside, but screaming internally because the only country in the world capable of exporting its inflation won’t stop playing third world games, so everyone will get third world prizes.

quoting
nevent1q…09e7
Money printer goes brr.

Gimme gimme!

2026-10-12T17:36:04Z

In reply to nevent1q…8xas
_________________________

Gimme gimme!

It depends on your level of paranoia, nothing in that proposal ...

2026-10-12T17:34:13Z

In reply to nevent1q…vee2
_________________________

It depends on your level of paranoia, nothing in that proposal prevents you from making your existing npub do the delegation, but like come on that would be a one time effort for priceless peace of mind.

I personally have rawdogged my nsec enough that I would prefer to go through that effort when the time comes.

Have you guys figured out the not-so-secret sauce that makes ...

2026-10-12T17:19:09Z

In reply to nevent1q…93za
_________________________

Have you guys figured out the not-so-secret sauce that makes Clave (npub1cla…539g) receive silent push instantaneously and replicated into Blitz?

Because right now, most of the wallet requests coming from Nostur (npub1n0s…k6h0) timeout for me.

Dude I am Brazilian, my race is yes.

2026-10-12T17:12:25Z

In reply to nevent1q…3ega
_________________________

Dude I am Brazilian, my race is yes.

That was so deep you may find oil

2026-10-12T17:08:46Z

In reply to nevent1q…zvpl
_________________________

That was so deep you may find oil

It is optional, but like why wouldn’t you? You can make your ...

2026-10-12T17:03:29Z

In reply to nevent1q…ltk2
_________________________

It is optional, but like why wouldn’t you? You can make your new key bless the existing npub, so that your existing posts aren’t lost in the transition, if I understood correctly.

Is it that bad in the big US of A?

2026-10-12T16:58:04Z

In reply to nevent1q…lg04
_________________________

Is it that bad in the big US of A?

He’s getting paid for that????

2026-10-12T16:52:15Z

In reply to nevent1q…a2q4
_________________________

He’s getting paid for that????

I don’t know if it was made to save money, I think the ...

2026-10-12T16:50:23Z

In reply to nevent1q…rvc4
_________________________

I don’t know if it was made to save money, I think the reasoning would be that nobody eats whole foods anymore and just associate the fake smell with the fruit… and then someone did a market research and found out enough psychos like that fake smell.

Or maybe we are just trying to read retards doing retarded things.

If I had to guess that would be the smell emitting from whatever ...

2026-10-12T16:42:01Z

In reply to nevent1q…scy3
_________________________

If I had to guess that would be the smell emitting from whatever chemicals they use to make artificial coconut flavoring.

@npub1fdt…uwwr have you seen this?

2026-10-12T16:32:15Z

In reply to nevent1q…h5sf
_________________________

verita84 (npub1fdt…uwwr) have you seen this?

My only and barely relevant complaint is the use of etherum ...

2026-10-12T16:15:24Z

In reply to nevent1q…kw83
_________________________

My only and barely relevant complaint is the use of etherum instead of rootstock, which I believe would make it easier to get bitcooners on board.

I see where you are coming from and that may be true for some of ...

2026-10-12T16:01:24Z

In reply to nevent1q…h934
_________________________

I see where you are coming from and that may be true for some of these projects, like Yggdrasil really started as a research thing.

However I don’t think that applies to CJDNS and FIPS.

Caleb James DeLisle (npub1mh5…233h) , the creator of CJDNS, the oldest of this category of self arranging, encrypted, ipv6-compatible mesh networks (or darknets or whatever people like to call them), created pkt.cash with a novel “bandwidth pow” to, among other things, fund the project in a way that the equipment you buy to mine later becomes useful to sustain the network.

FIPS is the other way around, people at toll gate hit some scaling issues trying to bend the traditional network stack into incentivized mesh networks and so FIPS was born.

And there’s also Althea doing moves since 2018.

Now, I’m not so sure these projects are in the exact same position as nostr. Incentivized meshnets can lure anyone in with the idea of reselling idle internet links, which basically acts as the gateway drug. That is value delivered in the short term and dare I say it is easier to flash some random wifi router than it is to figure out how and why to nostr.

Meanwhile, when nostr (as a twitter replacement) got its big push, the fediverse/bluesky bridges weren’t up yet so people got burned with the lack of content and whatever other problems of early technology.

I’m pretty sure things would’ve been different if bridges were a day one priority, see how Matrix did an embrace, extend and extinguish on IRC.

The package management side of flatpak is atrocious compared to ...

2026-10-12T04:39:38Z

In reply to nevent1q…djpt
_________________________

The package management side of flatpak is atrocious compared to something like nix or guix

Flatpak is barely a sandbox. Things might improve with flatpak 2 ...

2026-10-12T04:25:29Z

In reply to nevent1q…xmaj
_________________________

Flatpak is barely a sandbox. Things might improve with flatpak 2 but eh