Considering (partial?) removal of OpenAlias support. Comment here if you use it.

[SomberNight]

With recent refactoring of invoices/payment requests, OpenAlias support is now partially broken.
Looking up an OpenAlias (name -> addr) works, however

• signing a payment request with an openalias is broken
  

  electrum/electrum/wallet.py

  Line 1772 in eb39aa1

  def sign_payment_request(self, key, alias, alias_addr, password): # FIXME this is broken

• trying to pay a bip21 URI with embedded openalias name and signature is broken
  

  electrum/electrum/util.py

  Line 854 in eb39aa1

  s = pr.serialize_request(out).SerializeToString()

  
  

  electrum/electrum/paymentrequest.py

  Line 449 in eb39aa1

  def serialize_request(req): # FIXME this is broken

I am wondering whether this functionality is worth restoring/fixing.
We could remove the broken functionality;
or maybe we could strip OpenAlias support completely.

Do people actually use OpenAlias?
Do you use OpenAlias? What do you use it for?

If you want the project to keep supporting OpenAlias, please comment here.

[fluffypony]

I know of a fair number of people that use OpenAlias within Electrum, and we're actually busy with an OpenAlias v2 spec. There's also some activity around OpenAlias with Lightning, so I'd definitely push for it to continue.

A bip21 URI with OA embedded could get confusing, as the OA record itself could include an amount, so I'd veer away from that particular edge-case - unless we start to see adoption by payment processors that dictates revisiting this.

[relativisticelectron]

Is this not a huge privacy leak (without paynyms) and should not be used?

[fluffypony]

@relativisticelectron yes, but that doesn't mean it's not useful. OpenAlias is a very broad standard, and works with Monero (for instance) where privacy isn't an issue. It already allows you to specify a Lightning invoice (via oa1:lightning), which may be somewhat useless given the nature of DNS, but there will be long-lived LN payment mechanisms in future that OA will support.

[ysangkok]

@fluffypony keysend is already supported in LND and c-lightning: https://lightning.readthedocs.io/lightning-keysend.7.html

[fluffypony]

@ysangkok awesome that's great news!

[JeremyRand]

Namecoin is interested in OpenAlias (specifically using .bit domains for OpenAlias records), so we'd definitely vote for keeping the OpenAlias support present. Definitely would be useful to fix the privacy leaks associated with address reuse though.

[losnappas]

Who is this built for? Is there even a UI for registering an alias? I think it's junk, have not seen anybody use it.

[fluffypony]

@losnappas when you say stuff like "is there a UI for registering an alias" you demonstrate that you have no clue what you're talking about, didn't bother reading up on it, and are merely giving your uninformed opinion for some narcissistic reason. Feel free to come back to this conversation when you've actually done a smattering of research.

[losnappas]

Whoa there.

I was just giving the 2 cents of the average user. "for some narcissistic reason"? Calm down.

[fluffypony]

I was just giving the 2 cents of the average user. "for some narcissistic reason"? Calm down.

If that was the case you would have just said "I don't personally know anyone using it". Comments like "it's junk" have no place here.

[losnappas]

Right, I thought that that was more of a funny thing to say, but I guess people will read it with another tone in mind.

My apologies

[dunnock]

This really helps to send coins to people I personally know, instead of keeping hexadecimal addresses at hand for copy pasting. Please don't remove.

[delta1]

Another vote to please keep OpenAlias support, I use it regularly and I'm certain many more people (that may never see this issue do as well).

[stringhandler]

I'll like the project to keep supporting OpenAlias

[artk42]

Is there any further activity re OA v2 spec? The site looks doomed..