GM

Bitcoin eCash Cashu Satellite Tollgate wen fren? x3

When trying to understand new systems, I like to try to place them on that triangle to reason about the tradeoffs...

Aah, so the name is human readable, but the TLD is a large random string - ie. the entropy that makes it secure. That makes sense. Does this mean I need to check the large random string like checking an npub to make sure I'm being redirected to the right IP address?

Aah, so the name is human readable, but the TLD is a large random string - ie. the entropy that makes it secure. That makes sense. Does this mean I need to check the large random string like checking an npub to make sure I'm being redirected to the right IP address?

A pleasure =3

To further elaborate on what I meant by "no name scarcity", let's look at Space to help deliver what I mean.

You have name.space on the Spaces protocol, where "name" is unique and "space" is the protocol TLD (like .com) let's say.

On DNN, we have name.nABCeAbsurd, where the unique part of this is the TLD/ID (in this example, it's nABCeAbsurd, which is what I got when I did a bitcoin self-transfer. Another's might be nJHDcAbility, for example, or nMDKa12Zoo many years later), and "name" can be whatever you want, even if it's the same as someone else. The unique part is the TLD/ID, not the name.

It seems like the similarity between Spaces and DNN ends at 'both use bitcoin' (more specifically, both use bitcoin txid, but even there it differs).

Based on my understanding, at least on a surface level, Spaces has scarce names, must go through a bidding process to get a new name, and that process results in burning bitcoin (at scale, this isn't healthy for bitcoin in my opinion), and said process might result in requiring the user to pay (burn) a high number to get a single desired name/id/domain.

##Spaces:

Pros:

-uses bitcoin

-name transfer

-decentralized website

-equal to dns human readability

Cons:

-burning bitcoin

-relies on 'op_return' (putting spam in bitcoin, and spam here means anything that is not transaction data)

-similar bad ux as dns in terms of acquiring a name (or worse? requires consensus permission? i might be wrong on that 'requires consensus permission' bit)

-potentially very expensive

-scarce names (might not be a pro depending on who you ask, but for the end average user, and for scalability, it's a con)

-(not technical con:) brand tied (.spaces, .bitcoin)

Neutral:

-Can be updated to do what DNN is doing to circumvent IANA/IPs

##On DNN's side:

Pros:

-uses bitcoin

-decentralized websites (infinite)

-cheap

-doesn't burn bitcoin (but circulates it in a neutral sense)

-doesn't put any data on bitcoin (zero / no spam) / no reliance on 'op_return' or anything else, just the txid self-transfer

-no permission

-easy UX (self transfer btc, one click publishing of nostr events (4 button clicks at the moment, but will make it a one-click process soon), and done. Two actions. Well, three assuming you don't have funds on your bitcoin derived nostr address)

-no name scarcity (have whatever name you want, the ID/TLD part is a 'you get what you get')

-Brand-agnostic ('nabceabsurd' is just a simple structure)

Neutral:

-human-readable and memorable, but not as equal to the level of dns.

Cons:

-no transfer (though in most cases, 99%, there isn't a need to do it)

---

Aside from that, I think I'd have a much easier time with adoption, and faster, from developer adoption on nostr and on bitcoin (it's infra is bitcoin+nostr, and bitcoin and nostr sides are merging more and more over time, as well as how easy it is/would-be to implement dnn support on existing nostr signers apps or extensions), to user adoption through short to long term strategies. There's also an assumption of Tollgate's future potential growth/success that utilizes nostr, so DNN's growth path is intertwined with Tollgate as well.

---

So far, I see Spaces as a market of names to have fun in (and with usefulness in terms of identification and/or rendering sites), but not as the non-hostile slow/invisible infrastructure takeover of ICANN-DNS&IANA which DNN is going for. Though that's my opinion so far from what I looked into, and of course you're asking me who is the person behind DNN in this 'DNN vs Spaces' comparison x3 but who knows, maybe Space will be the dominant network in the future (hopefully no though, not out of malice but out of those cons i mentioned) and DNN won't be, which is fine, but I'd want to continue developing and pushing DNN to be that 'new internet' (hopefully along with Tollgate, it's awesome =3) as I took decisions for it to be simple, easy, infinitely scalable within bounds, cheap, not worry about names, and bring in a host of secondary benefit solutions.

Each new DNN ID is generated based on when their policy valid Bitcoin transaction is created, and its order position in the block.

A policy valid Bitcoin transaction is one where it's a self-transfer and the transaction fee is set at a minimum of 5 vBytes.

For example, I did that for myself using my Bitcoin derived address from my nostr address (this is also an important point) and got the numbers n4.8 and b922664.8 (n as in nostr/DNN, b as in bitcoin).

The first number in each is the entry of where the transaction took place, and the second number is its position within them, in the context of policy validity (self transfer, minimum fee, order based on amount).

From that it's already unique and will always be so.

From there, the encoder transforms that number based ID to a human-readable and memorable one. That n4.8 turned into nABCeAbsurd.

n = DNN/nostr prefix

abc = batch of blocks of an upper limit if 15,600 policy valid transactions per block

e = block position within a batch

(future numbers) = cycle of 78,000 blocks

absurd = bip39 mapping to the policy valid transaction position within a block ordered by highest paying fee rate

<3_letter_batch><1_letter_block>

So, with that number based ID and its encoder results, IDs will always be unique (and all are already created technically, just born yet. This is infinitely scalable, where I simulated results from 10k and a 100k years later and it still gave human-readable and memorable IDs). No collision.

So the IDs exist, and you get what you get in the end based on timing and fee rate. I'd imagine most people won't try to time to acquire a ID as other people would bump them up or down in position, they'll just do a self transfer and they get what they get. My name is still freakoverse, but my ID is nABCeAbsurd, and my I can have whatever website name, and however many, under that ID/TLD.

Regarding SEC, I'd love to (wanted to go there for a while), but most likely I'm unable to (though there would be someone there where he might do what he did last time, which is do a quick stream to everyone there of projects from people that aren't there).

Interesting. How do you ensure that other people can't claim the same name you already claimed? Ie. how do you ensure you have a global state?

Have you considered coming to SEC-07?

I'd love one to prune branches on some gum trees

It's at a point now where it's almost impossible for me to use the "regular" internet. I can't access half the sites. The reason? I care about my digital hygiene and thus use a VPN. Sometimes switching to a different VPN or switching the country of the VPN works; other times it does not. Oh well, I guess I'm not going to watch that video, or read that article, or look at that picture. Whatever.

In addition to that, if I'm not blocked completely, I have to prove that I'm human every step of the way. Captchas, re-captchas, Cloudflare checkboxes, the whole shebang. I am human. I promise. And I am very annoyed. Outright angry, even. I doubt that any robot will ever be as annoyed as I am right now about the current state of the internet.

What annoys me most, actually, is that all these measures don't really work. There's bots everywhere. Robots get access to the stuff anyway, using farms of humans, just like in the good old days of WoW gold farming. The centralized "safety" nets of Cloudflare et al brought down large swaths of the internet multiple times in the last couple of weeks alone, and as things centralize more and more these outages will happen more and more.

I'm very close to breaking up with the legacy internet. I'm human, I can cryptographically prove that I'm human, and I have sats to spend. But the legacy internet doesn't care about that. It cares about farming me and my data, while annoying me to no end. I've been nostr only for a while now, but that was only on the "social media" side. 2026 might be the year where I go nostr-only for everything, or to phrase it slightly differently: permissionless for everything.

No more "are you human?"

No more "I'm sorry, Dave. I'm afraid I can't do that."

No more cookie banners, paywalls, and AI slop.

No more being treated like a child.

Even if it means that I'll have to self-host everything.

Even if it means that I'll have to build & maintain stuff myself.

Even if it means that it's a lot of work and pain.

Nothing worth having ever comes easy.

But the easy stuff is not worth having in the first place.

Here's to the year to come, and the new corner of the internet, build on cryptography and webs-of-trust. Real value. Real connections. Real humans.

Here's to nostr.

BTC question... does anyone have any idea or an example of :

what data a BTC node sends to the network when a block is found ?

I want to test and see if i can setup the BitSatRelay to route any node traffic to the BTC network. I can download my database/blocks/node sync via nostr:npub1jg552aulj07skd6e7y2hu0vl5g8nl5jvfw8jhn6jpjk0vjd0waksvl6n8n satellite download service and i can relay data out from my nostr:npub14uee3fwxjwq7m25gsyqguv2t6v8ft69jax4lvs3skfpa8u7thdsqpu7gam .. as i cant have a "open" outgoing connection being in "off grid mode" I need to send a burst of data out as and when node says block found - on order to propagate it. ( ok wishful thinking to find a block but none the less i want to built the tech to exist as my fall back SHTF) Any tips or insight is welcome

BTC question... does anyone have any idea or an example of :

what data a BTC node sends to the network when a block is found ?

I want to test and see if i can setup the BitSatRelay to route any node traffic to the BTC network. I can download my database/blocks/node sync via nostr:npub1jg552aulj07skd6e7y2hu0vl5g8nl5jvfw8jhn6jpjk0vjd0waksvl6n8n satellite download service and i can relay data out from my nostr:npub14uee3fwxjwq7m25gsyqguv2t6v8ft69jax4lvs3skfpa8u7thdsqpu7gam .. as i cant have a "open" outgoing connection being in "off grid mode" I need to send a burst of data out as and when node says block found - on order to propagate it. ( ok wishful thinking to find a block but none the less i want to built the tech to exist as my fall back SHTF) Any tips or insight is welcome

I think I've found the problem with what I propose at the top of this thread.

Alice can spend the same secret after sending it to Carol, by blinding the same secret in the conventional way and then spending it before Carol attempts to spend it

So that's why we need to stick with the two stages, both with P2PK

(I must admit I'm not sure I understand your response)