<oembed><type>rich</type><version>1.0</version><author_name>npub1pynqzktaxz4ffsv8w0ju86anmqmfjau252vwd43nmw0qdk3xrmtskld7pp</author_name><author_url>https://nostr.ae/npub1pynqzktaxz4ffsv8w0ju86anmqmfjau252vwd43nmw0qdk3xrmtskld7pp</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-01-15&#xA;📝 Original message:One variation of this, &#34;recycled address&#34;, might avert misconceptions that&#xA;the &#34;re-use&#34; is exclusive to one&#39;s own identity.&#xA;&#xA;&#xA;Eric Martindale, relentless maker.&#xA;http://www.ericmartindale.com&#xA;+1 (919) 374-2020 | *BitMessage: *BM-2cWCmYBpV64FRSJpHHKWi1Cfc9W52jydwe&#xA;*Note:* Beginning December 11th, 2013, I will only be intermittently&#xA;available via email, SMS, and BitMessage.  As a courtesy, please leave a&#xA;detailed message so that I can respond in kind.  Thanks!&#xA;&#xA;&#xA;On Wed, Jan 15, 2014 at 7:05 PM, Jeremy Spilman &lt;jeremy at taplink.co&gt; wrote:&#xA;&#xA;&gt;  Might I propose &#34;reusable address&#34;.&#xA;&gt;&#xA;&gt; I think that describes it best to any non-programmer, and even more so&#xA;&gt; encourages wallets to present options as &#39;one time use&#39; vs &#39;reusable&#39;.&#xA;&gt;&#xA;&gt; It definitely packs a marketing punch which could help drive adoption. The&#xA;&gt; feature is only useful if/when broadly adopted.&#xA;&gt;&#xA;&gt; I think it meets all the criteria required:&#xA;&gt;&#xA;&gt;   - Communication between parties is a single message from the payee,&#xA;&gt; which may be public&#xA;&gt;   - Multiple payments to the same address are not publicly linkable on the&#xA;&gt; blockchain&#xA;&gt;   - The payee has explicitly designated they expect to receive more than&#xA;&gt; one payment at that address&#xA;&gt;   - Payer can publicly prove they made a payment to the reusable address&#xA;&gt; by revealing a secret&#xA;&gt;&#xA;&gt; I have high hopes for this feature. The war *against* address reuse may&#xA;&gt; soon be a distant memory.&#xA;&gt;&#xA;&gt; On Wed, 15 Jan 2014 12:44:17 -0800, Jeff Garzik &lt;jgarzik at bitpay.com&gt;&#xA;&gt; wrote:&#xA;&gt;&#xA;&gt; &#34;static address&#34; seems like a reasonable attempt at describing intended&#xA;&gt; use/direction.&#xA;&gt;&#xA;&gt; On Wed, Jan 15, 2014 at 3:38 PM, Gregory Maxwell &lt;gmaxwell at gmail.com&gt;wrote:&#xA;&gt;&#xA;&gt;&gt; On Wed, Jan 15, 2014 at 12:22 PM, Ben Davenport &lt;bendavenport at gmail.com&gt;&#xA;&gt;&gt; wrote:&#xA;&gt;&gt; &gt; But may I suggest we consider changing the name &#34;stealth address&#34; to&#xA;&gt;&gt; &gt; something more neutral?&#xA;&gt;&gt;&#xA;&gt;&gt; ACK.  Regardless of the &#39;political&#39; overtones, I think stealth is a&#xA;&gt;&gt; little cringe-worthy.&#xA;&gt;&gt;&#xA;&gt;&gt; &#34;Private address&#34; would be fine if not for confusion with private-keys.&#xA;&gt;&gt;&#xA;&gt;&gt; &#34;Static address&#34; is perhaps the best in my view. (also helps improve&#xA;&gt;&gt;  awareness that normal addresses are intended to be more one-use-ness)&#xA;&gt;&#xA;&gt;&#xA;&gt;&#xA;&gt; ------------------------------------------------------------------------------&#xA;&gt; CenturyLink Cloud: The Leader in Enterprise Cloud Services.&#xA;&gt; Learn Why More Businesses Are Choosing CenturyLink Cloud For&#xA;&gt; Critical Workloads, Development Environments &amp; Everything In Between.&#xA;&gt; Get a Quote or Start a Free Trial Today.&#xA;&gt;&#xA;&gt; http://pubads.g.doubleclick.net/gampad/clk?id=119420431&amp;iu=/4140/ostg.clktrk&#xA;&gt; _______________________________________________&#xA;&gt; Bitcoin-development mailing list&#xA;&gt; Bitcoin-development at lists.sourceforge.net&#xA;&gt; https://lists.sourceforge.net/lists/listinfo/bitcoin-development&#xA;&gt;&#xA;&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140115/dad871e2/attachment.html&gt;</html></oembed>