Luke Dashjr [ARCHIVE] on Nostr: 📅 Original date posted:2016-01-26 📝 Original message:On Tuesday, January 26, ...
📅 Original date posted:2016-01-26
📝 Original message:On Tuesday, January 26, 2016 3:01:13 AM Toby Padilla wrote:
> > As I explained, none of those reasons apply to PaymentRequests.
>
> As they exist today PaymentRequests allow for essentially the same types of
> transactions as non-PaymentRequest based transactions with the limitation
> that OP_RETURN values must be greater. In that sense they're basically a
> pre-OP_RETURN environment. OP_RETURN serves a purpose and it can't be used
> with PaymentRequest transactions.
OP_RETURN can be used, but you need to burn coins. I don't see any benefit to
changing that. It is better that coins are burned.
> > I have no idea what you are trying to say here.
>
> I think if you think through how you would create an OP_RETURN transaction
> today without this BIP you'll see you need a key at some point if you want
> a zero value.
You *always* need a key, to redeem inputs... regardless of values.
Luke
📝 Original message:On Tuesday, January 26, 2016 3:01:13 AM Toby Padilla wrote:
> > As I explained, none of those reasons apply to PaymentRequests.
>
> As they exist today PaymentRequests allow for essentially the same types of
> transactions as non-PaymentRequest based transactions with the limitation
> that OP_RETURN values must be greater. In that sense they're basically a
> pre-OP_RETURN environment. OP_RETURN serves a purpose and it can't be used
> with PaymentRequest transactions.
OP_RETURN can be used, but you need to burn coins. I don't see any benefit to
changing that. It is better that coins are burned.
> > I have no idea what you are trying to say here.
>
> I think if you think through how you would create an OP_RETURN transaction
> today without this BIP you'll see you need a key at some point if you want
> a zero value.
You *always* need a key, to redeem inputs... regardless of values.
Luke