there is such things as non-network identities using the user@location format, but anyway, the thing is that there is no consensus mechanism for tying names to nostr:npubs anyway... this would actually be a sane use of op_return then you could have the "location" being some code meaning "bitcoin blockchain" i'd sure be fine with spending a transaction to anchor my npub onchain to a name, just needs a scheme for superseding identifiers