From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 0F44792 for ; Wed, 22 Jun 2016 15:31:08 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-yw0-f181.google.com (mail-yw0-f181.google.com [209.85.161.181]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id EF9521BD for ; Wed, 22 Jun 2016 15:31:06 +0000 (UTC) Received: by mail-yw0-f181.google.com with SMTP id l125so45238351ywb.2 for ; Wed, 22 Jun 2016 08:31:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=qUOdIV/z2+EQwjNfEB9sz9NT30lAd/CfRjWh+LPb8Lc=; b=Fta9HOpD42OGNQlJyEb62pssd+xbKig1SexZ35BdR1ABUMNGoTt21i052yt6D69ULT RKKZXwZXgDATFGj+Ri1rWqvGpN3KJDtDhEZNY0b1xi992sOCpNcmjDZMr/S8Cs3oWtZ0 shDpfoB55+HHKtHytu9B9V8OZ/4eGhmL/sKAkEMpLRqSgD9p8WOygC6onGaZnbQcS9gU FYPV8lqY0PluvwVBWQ6NYZcNjPYPM9DfRV31k8TsSjS0iQI13NQZP2g768/RNW5lBMhi 6JVyAiIiW/NFqCpecngBRXzNDhoYC4SR8+cl266RYmvrF99xKGcB4Ft32O2Upv4ewXlE +IAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=qUOdIV/z2+EQwjNfEB9sz9NT30lAd/CfRjWh+LPb8Lc=; b=KlszB6XTv/7IPi/3oyTGPf6OXJfqTJt8bc3U3fpcmG9FH6G0Vzs/kksK4D9j3jNJ7M Je/05oBKKQOGrJSTtmJofUrr/vjJsm+Hb6mqv9/jopxJgK7DxG8z+7zd6ltiF0rq5W70 ZNvYMbriLB5o9sJ8dsAK3mfWkrltJ2hrY/st1P4/6EBK+Y8xHCGWX15bTb23m0lBSlRv fXHLi5Qs1QYbXOY+l9v1fmEluaWyv98JiEnRUsAM3OTD4zmApY36o505zakiUnA+cg5t vMpmh9KeeHwJDxmFgr1bfDkQCZ86YGU96sNY1a/D10VVjsbB35WSxGTldQj3p/mSXz0g 7Dig== X-Gm-Message-State: ALyK8tJ2oHH66ZjOmwZb4qDpcB1TWWjhUZw72fZYJkqPv2b/SIGuxqABmsyDI+7vZWPNf5Lr5Isl+Dbl1MjloA== X-Received: by 10.37.15.10 with SMTP id 10mr14636491ybp.51.1466609465994; Wed, 22 Jun 2016 08:31:05 -0700 (PDT) MIME-Version: 1.0 Sender: earonesty@gmail.com Received: by 10.37.72.68 with HTTP; Wed, 22 Jun 2016 08:30:55 -0700 (PDT) In-Reply-To: <576AAAC4.1020304@AndySchroder.com> References: <576A44F1.9050108@electrum.org> <576AAAC4.1020304@AndySchroder.com> From: Erik Aronesty Date: Wed, 22 Jun 2016 11:30:55 -0400 X-Google-Sender-Auth: 6emYMivF0CxAZ80lAJHaIaex5IU Message-ID: To: Andy Schroder Content-Type: multipart/alternative; boundary=001a1138f4743eb93a0535dfa051 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Wed, 22 Jun 2016 19:33:55 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Even more proposed BIP extensions to BIP 0070 X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2016 15:31:08 -0000 --001a1138f4743eb93a0535dfa051 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Again, my comments above about issues with using bitcoin: URI for everything. Also, why do you want to bloat the blockchain with unnecessary refund transaction data? I don't, sorry - I was just kind of thinking out loud and explaining what happens when you stuff that into a URL. My conclusion at the bottom of that post was to keep BIP 75 the same, don't change a bit, and stick any subscription information (future payment schedule) in the PaymentACK. Then the wallet then re-initiates an invoice (unattended or attended.. up to the user), after the subscription interval is passed. Subscriptions are pretty important for Bitcoin to be used as a real payment system. =E2=80=8B --001a1138f4743eb93a0535dfa051 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
> Again, my comments above about issues with = using bitcoin: URI for everything. Also, why do you want to bloat the blockchain with unnecessary refund transaction data?

I don't, sorry -= =C2=A0 I was just kind of thinking out loud and explaining what happens whe= n you stuff that into a URL.=C2=A0=C2=A0

My conclusion at the botto= m of that post was to keep BIP 75 the same, don't change a bit, and sti= ck any subscription information (future payment schedule) in the PaymentACK= .=C2=A0=C2=A0 Then the wallet then re-initiates an invoice (unattended or a= ttended.. up to the user), after the subscription interval is passed.=C2=A0= Subscriptions are pretty important for Bitcoin to be used as a real paymen= t system.=C2=A0=C2=A0


=E2=80=8B
--001a1138f4743eb93a0535dfa051--