I will push another build to TestFlight with a few fixes in a week or two
Honor is dead, but I’ll see what I can do. 
For some reason, I spent an entire evening working on #WheelOfTime generative AI portraits 
Always a good day when you make it into the nostr report nostr:note1awt3qv6c99su6mkgwx62dj80tervfc2elwcrqrfuww45gczvhwkq8kg6lq
How does one activate this?
“The Golden Crane flies for Tarmon Gai’don”
Basically. There’s only room for about 200-300 total ASPs if all of the blocks were taken up entirely with ark transactions.
#[0] #subscribe
No. Every five seconds an ASP does a coin join round that results on a transaction on the Bitcoin blockchain.
I don’t think footprint is a huge problem with this protocol. On Nomen output is 41 bytes in total. That means if every single person on earth registered one, it would only add 370 GB to the blockchain. It’s not like you need a lot of these names, or need to make frequent transactions on chain. Of course, that isn’t possible, anyway. Long before that happened, a name will be too expensive to register on chain for almost anyone, and they will move to sidechains (I talk about this at the end of the post).
It is simpler which is a big win, but the main reason what you said wouldn’t work is because someone could claim a zillion names at no cost and never publish a nostr event to prove it. Then when someone decided to claim a name that the spammer had claimed (he could fit a million in the OTS transaction if he wanted), he could just reveal his first “claim” and rugpull the whole protocol.
In Nomen, there is a 5 byte fingerprint in the metadata. The fingerprint is the first five bytes of the HASH-160 of the name. It’s right there, in the open, on the blockchain. You can tell if anyone has claimed a name you want without publishing a Nostr event just by scanning the blockchain for your fingerprint. No chance of getting rug pulled by a sneaky squatter.
I think I just maybe understood what you mean. Yes, I am aware of opentimestamps. What makes it a non-starter is that it is compresses infinite documents into a single hash (as I understand it). This is not desirable because then someone could claim many names at no cost. Which is probably closer to what you meant, I am guessing? If so, yes, that is why I chose the method I did
It did a number on me 😭
It’s not just to reduce spam, though that helps. Bitcoin provides absolute ordering. Outputs inside transactions inside blocks, all in exact sequence. This allows indexers to verify who claimed a name. POW doesn’t provide any kind of ordering guarantee
I wanted to share a little bit about Nomen, a new protocol that establishes rules for creating globally unique, human readable identifiers, similar to domain names but without a central planner like ICANN.
- How does it work?
Nomen uses the ordering guarantees of the Bitcoin blockchain as the arbitration method for opposing claims on names. In other words: first come, first serve. Nostr acts as the data layer of the protocol. Records and other data-heavy operations happen as Nostr events on public relays. Indexers, which are the name servers of the protocol, link on-chain claims to related Nostr events in order to piece together a full picture of the Nomen name set.
For a more complete view of the protocol, check out the specification on GitHub. It’s very simple: https://github.com/ursuscamp/nomen/blob/master/docs/SPEC.md
- What’s in a name?
A name is “complete”, so to speak, when there is a claim published on chain with a corresponding Nostr event that contains the records for that name. The on-chain claim is merely an OP_RETURN output, which contains a few bytes of metadata and a 20-byte hash of the ownership information (Hash-160 of NAME + PUBLIC KEY). A corresponding Nostr record event must be published that is signed by the owner of the name, containing a tag with the name that was claimed and a record set. Using the name and the public key, the indexer can recompute the hash and validate that this event is published by the true owner of the name. The record event is a replaceable event, so every time you want to update your record set, you just publish a new record event to replace the old.
The record set is a just a set of key/values that represent the pieces of identity you want published. Some examples are “WEB” for your website, “TWITTER” for your twitter handle, “NPUB” for your Nostr pub, etc.
- The Explorer
The Nomen Explorer (https://nomenexplorer.com) is the first public indexer. Not only does it allow you to explore the existing names out there already, but it has tools to claim a name for yourself and to update your records.
Claiming a name through the Explorer is a trustless process. All you need to do is create an unsigned Bitcoin transaction paid back to yourself (or whoever you want) and copy it to your clipboard. Then click “New Name” in the Explorer, and paste your PSBT into the box. Enter your name and pub key, then submit. The Explorer will add an extra output to the PSBT which is a 0 sat OP_RETURN, and spit the new PSBT back out to you. Load that PSBT into your Bitcoin wallet. You can examine it to make sure the Explorer isn’t doing any funny business (it’s not, I promise!), then sign it and broadcast. The indexer will pick it up after 3 confirmations.
Then you click “Update Records” and publish a new record set. Sign the event with your Nostr extension (Alby, nos2x, Nostore, etc), and you’re good to go. Within a few minutes, the explorer should pick it up and display it in the list.
- Consensus
You might have noticed that, since the claim is published in an OP_RETURN, that means that the miners and validators don’t enforce consensus like they do with Bitcoin script. In Nomen, the indexers are the arbitrators of consensus. This is a looser social consensus mechanism, similar to something like you might find with Ordinal Theory. This has advantages, as you will see.
- Squashing Squatters
Any name system needs to have a way of dealing with squatters. That way may be absolute central control, or letting them run rampant, or somewhere in between. The softer consensus of Nomen provides a potential solution to this problem.
One possible protocol upgrade is a standard for something like a decentralized spam/blacklist for squatters. Indexers could choose to subscribe to streams of Nostr events from trusted parties that handle spammers and squatters. Any name claim on such a spam list would be ignored by an indexer, and the next claim taken as the correct one.
In reality, just the existence of such lists should deter most squatters, since they would need to waste real Bitcoin in mining fees just to try something easily thwarted by indexers.
- Scaling and the Future
The ability to scale these names is important. Every name requires an output on-chain. This isn’t a massive concern (yet) because most people won’t ever need but one or a few of these names. But, still, how far can we scale this?
One example of low hanging fruit is to allow name owners to create sub-names by publishing sub-name Nostr events. These could be useful for families, or for businesses to offer names to their customers. For instance, Bob Smith might register the name “smith” and create a sub-name for each of his children: alice.smith, andy.smith, etc.
Another exciting possibility is to expand the protocol to sidechains, using custom naming schemes. If “smith” is registered on the Bitcoin blockchain, someone else may claim “smith.lqd” on the Liquid sidechain.
The combination of non-sovereign sub-names and sovereign top-level names on sidechains means that this one protocol could potentially scale to the entire world with ease.
If I understand the protocol, the ASP does an on-chain transaction for every round. So I guess 5 seconds is fast enough for a payment to be quick on mobile, but slow enough to allow “plenty” of ASPs to operate. Every bit of time you shave is less blockspace available for ASPs.
Hello fren 🐸 
Which one of you did this 😂 