Hi,
[I sent this email 2 days ago prior my registration to the mailing list; please
forgive me if this is a duplicate]
I would like to propose an extension to the Payment Protocol (bip-0070) to
address the case of recurring payments in Bitcoin -- new bip or modification of
bip-0070.
There has
From what I have seen so far, there seems to be an agreement that this is a
nice feature to add. We are pretty new to that community and so we don't know
exactly what the process is, and in particular how we reach consensus via
email. I am certainly open to follow 'the way' if there is one, but
to define the payment schedule
> Do you allow pre-submission of time locked transactions or not?
> I think as you prototype these things will become clearer. You could try
> prototyping either in Bitcoin Core (C++) or bitcoinj (java, look at the
> PaymentSession class).
>
>
>
d transactions or not?
>> I think as you prototype these things will become clearer. You could try
>> prototyping either in Bitcoin Core (C++) or bitcoinj (java, look at the
>> PaymentSession class).
>>
>>
>>
>> On Wed, Jan 29, 2014 at 3:47 AM, Stephane
to add it
later this week. Think of your Netflix subscriptions, this is never ending
(evergreen) until you decide to terminate it or Netflix does it (abuse, bills
not paid,...)
Thanks for taking a look!
>
> On Sat, Feb 8, 2014 at 6:48 PM, Stephane Brossier
> wrote:
> Mike, Gavin,
Kevin,
We did a second iteration on the prototype to implement subscription
cancellation and upgrade/downgrade. We checked in both the bitcoinj and php
server to be able to test it.
We also worked on our side of the merchant implementation (Kill Bill) to feel
confident that the protocol will su
have more important matters to solve these days with
the recent malleability issue, but i want to make it clear that we are waiting
for feedbacks to make additional progress.
Thanks!
S.
On Feb 14, 2014, at 12:28 PM, Stephane Brossier wrote:
> Kevin,
>
> We did a second iteration
Hi Mike, Jeremy, Drak,
Before going through your questions, I would like to bring some clarity on a
few key elements in that protocol. There are really two aspects to it:
The contract negotiation; when the user first subscribes, it is prompted by a
contract that will define the payment bounds as
8 matches
Mail list logo
