<oembed><type>rich</type><version>1.0</version><author_name>npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7</author_name><author_url>https://nostr.ae/npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-02-26&#xA;📝 Original message:On 02/24/2015 11:41 AM, Mike Hearn wrote:&#xA;&gt;     Does this not also require the BT publication of the script for a P2SH&#xA;&gt;     address?&#xA;&gt; &#xA;&gt; &#xA;&gt; You mean if the URI you&#39;re serving is like this?&#xA;&gt; &#xA;&gt;    bitcoin:3aBcD........?bt=....&#xA;&gt; &#xA;&gt; Yes it would. I guess then, the server would indicate both the script,&#xA;&gt; and the key within that script that it wanted to use. A bit more complex&#xA;&gt; but would still work to save URI space.&#xA;&#xA;What if the script doesn&#39;t use any key at all?&#xA;&#xA;Somehow this &#34;re-using&#34; the fallback address idea feels less and less&#xA;appealing to me. I think we should add our own parameter and let go of&#xA;fallback addresses as soon as possible. If will waste space during the&#xA;transition period, but after that it should make no difference any more.</html></oembed>