<oembed><type>rich</type><version>1.0</version><author_name>npub12hzwfhx9ptjf2f0va8qllc0h4tcvz5aaefvlvn9uq8z2ssrq027qtvtmxa</author_name><author_url>https://nostr.ae/npub12hzwfhx9ptjf2f0va8qllc0h4tcvz5aaefvlvn9uq8z2ssrq027qtvtmxa</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-03-06&#xA;📝 Original message:On Thu, Mar 6, 2014 at 11:07 AM, Mike Hearn &lt;mike at plan99.net&gt; wrote:&#xA;&#xA;&gt; if some sort of Stealth address or HD wallet root was the identity gaining&#xA;&gt;&gt; the reputation, then address re-use wouldn&#39;t have to be mandatory.&#xA;&gt;&gt;&#xA;&gt; The identity would be the X.520 name in the signing cert that signed the&#xA;&gt; payment request. It doesn&#39;t have to be a difficult to obtain cert. It could&#xA;&gt; even be self signed for this use case, but then you lose the security&#xA;&gt; benefits and a key rotation would delete your reputation, so in practice I&#xA;&gt; think most people would want the reputation to accrue to the name itself.&#xA;&gt;&#xA;&#xA;That makes sense, to have self-signed certificates as a basic start, but&#xA;then is it possible to have a Bitcoin user (address) add reputation/sign&#xA;such a certificate, rather than having a central signing authority? If&#xA;there was a way for a Bitcoin user to provide feedback on a payment (ECDSA&#xA;signature from one of the addresses involved in the payment, signing an&#xA;identifier of the payment and a feedback score) such that any user can add&#xA;to the reputation with just the Bitcoin infrastructure, without having to&#xA;learn X.500 certificate signing on top of EC signatures? If there was a&#xA;standard structure for a message to be EC-signed with your Bitcoin client,&#xA;and then a distributed store of those signed messages, could that form a&#xA;reputation score?&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140306/3f35eb4a/attachment.html&gt;</html></oembed>