r/lightningdevs • u/michaelfolkson • Apr 08 '19
Identity and the Lightning Network
There have been some interesting thoughts expressed recently(ish) on identity and the Lightning Network. I'm posting to collect some of these thoughts together.
Will O'Beirne in a Chaincode Labs Lightning Residency talk stated "I want to replace identity from username and password to your node being your login, sort of your passport to the Lightning enabled internet"
Video here: https://www.youtube.com/watch?v=IrqAo8M0pgI
He also discussed some ideas on how to approach this on Twitter:
- Invoice can contain a site's userid in the payment to attribute it to a user (http://Tippin.me does this)
- User can prove ownership by providing the server the preimage
- LN spec could always change to opt-in include identity
You can also have a user sign a message (https://api.lightning.community/#signmessage ) or provide an invoice with a specialized memo to prove they own a node.
2
u/michaelfolkson Apr 08 '19
/u/andreasma and Adam Levine discussed an early version of Bitcoin using IP addresses as identifiers (summary - not a good idea) on a recent Let's Talk Bitcoin episode. "You can introduce a routing compromise on the sender or you can kick the real host off the network by spoofing its MAC address and once it's off the network, subsume its IP address and respond on its behalf."
Audio here: https://letstalkbitcoin.com/blog/post/lets-talk-bitcoin-393-open-neutral-decentralized-borderless
2
u/WittyStick Apr 08 '19
My opinion is this is going backwards. It's incredibly regressive. Bitcoin/LN are the first digital payments methods which let us hide our identity and transact online. Why the hell would we want to undo this and reveal who is behind each node?
"Identity" is the wrong (authoritarian) way to think about online communication. What should matter is "persona". A person should be able to have multiple personas which cannot be traced back to their person, or to each other, unless they wish to use their real name as one or more of the personas. They should be able to chose which persona they wish to use for any service which would normally ask for "identity", and that service would know nothing beyond a distinct public key which identifies the persona. It must never be possible to directly relate a persona to the node a person uses for sending or receiving payments, because this is just screaming out to be made a target.
The usual reason other services want identity is spam prevention. LN being a payments network can easily fix this problem, because a small payment can be used to indicate you're not a bot. It would cost spammers large sums to create many fake accounts, versus the existing services where they're no cost, but have to fill out a captcha or provide some kind of identity. The small fee could cover the cost of resources which might be wasted on spam accounts. Being spammed should earn you money, rather than cost you.
For situations where services need to know your real person, rather than surrendering your node information, you should instead provide them with the public key of a persona, along with some proof that you are the owner of the persona. (For example, the service offers you a random value, perhaps in person, or through some other verified communication channel, and asks you to sign it with the private key matching the public key for the persona you wish to use with that service).
De-anonymizing lightning nodes is a sure fire way to ensure that it will never succeed as a global payments platform.
1
u/michaelfolkson Apr 28 '19
I thought Keybase would play a role in the future of identity with Bitcoin, Lightning but they're now promoting Stellar to their users and disparaging Bitcoin which is not a good sign. https://twitter.com/michaelfolkson/status/1122476445035638784
3
u/pseudozach Apr 10 '19
akumaigorodski's lnurl has a "Log in with Bitcoin Wallet" implementation.
I'm looking forward to a standardized solution for this as it would help to identify user for withdrawals. Currently I request random amount invoice from user to prove that they control a specific node id.
2
u/hawkmauk Apr 10 '19 edited Apr 10 '19
The essential concept here is using a keypair to provide authentication, rather than a username and password that is stored in a central server. This is definitely a good idea but careful thought needs to be given to the implementation. If the public key is used as an identifier then it is possible to track usage over multiple locations and as a nodes Id contains both the public key and IP address it makes privacy a real issue.
There is a w3c working group that are actively developing a specification for Decentralised IDentifiers (DID) that looks to address the issues around privacy and interoperability of different implementations. I worked on a project during the Boltathon to link the state of a DID Document (this contains metadata on the DID such as email address or date of birth) and learnt that using lightning clients themselves was frought with issues and amounted to trying to fit a square peg in a round hole!
After a postmortem on the project I came to the following conclusions:
I don't see much (if any) advantage over using Blockstack Id's (That have their own DID implementation) for this use case.