SSH succeeded because it removed bureaucracy: users not developers know who they trust, with what, and why: https://tools.ietf.org/html/draft-iab-protocol-success-04#appendix-A.3 …
-
the current payment protocol use x509, typically with the same host key as the SSL site running a million lines of web framework.
-
-
@NickSzabo4 indeed! my assertion is trust anchor needs to be sender verifiable & exercisable without online interaction with recipient code. -
@adam3us Even better: let users handle Bitcoin addresses however they want to handle Bitcoin addresses. They know, the rest of us don't. -
@NickSzabo4 well. i think its clear users & developers have spoken: they want a reusable bitcoin address. problem is that breaks fungibility -
so I think solution is find a safely reusable addr as trust anchor & then get out of user & developers way, let them do what they find best.
-
about server for x509 signed one-use addr; challenging for users to run and x509 is complex & vulnerable to hacker & insider impersonation.
-
dont want diginotar (hacked CA) nor insiders (rogue state owned/coerced CAs) to be a TTP inside trust-anchor interpretation. thats crazy.
-
once a key is accepted it can be (somewhat) safely reused via BIP 32 HD wallets. trust-anchor is a privacy preserving introducer problem.
-
secure trust-anchor easy for full nodes: stealth address (encrypt to recipient) & have them trial-decrypt all tx. hard part is SPV compat.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.