📅 Original date posted:2016-01-26
📝 Original message:On Tuesday, January 26, 2016 2:54:16 AM Toby Padilla wrote:
> Luke - As stated in the Github thread, I totally understand where you're
> coming from but the fact is people *will* encode data on the blockchain
> using worse methods. For all of the reasons that OP_RETURN was a good idea
> in the first place, it's a good idea to support it in PaymentRequests.
As I explained, none of those reasons apply to PaymentRequests.
> As for keyless - there's no way (that I know of) to construct a transaction
> with a zero value OP_RETURN in an environment without keys since the
> Payment Protocol is what defines the method for getting a transaction from
> a server to a wallet. You can make a custom transaction and execute it in
> the same application but without Payments there's no way to move
> transactions between two applications. You need to build the transaction
> where you execute it and thus need a key.
I have no idea what you are trying to say here.
Luke
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 17:48:07
in reply to nevent1q…fkr9
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nSeen on
wss://relay.noswhere.comPublished at
2023-06-07 17:48:07Event JSON
{
"id": "dc0502945e08f71f08be6a95c6709777affbce6829339aac3fb0d4cec60e3f22",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686160087,
"kind": 1,
"tags": [
[
"e",
"368032d333e01794ac3e7b97c278de084cce6e6228857d943836fb1a934a5739",
"",
"root"
],
[
"e",
"1eac8c31107d51b3dffc1ffa9538e893b7bbdab6f44efa82b08b15332cebd452",
"",
"reply"
],
[
"p",
"d94a4049e1eafdb70a0dc089351c47ae335f75b3408012d8495d51889ad9a292"
]
],
"content": "📅 Original date posted:2016-01-26\n📝 Original message:On Tuesday, January 26, 2016 2:54:16 AM Toby Padilla wrote:\n\u003e Luke - As stated in the Github thread, I totally understand where you're\n\u003e coming from but the fact is people *will* encode data on the blockchain\n\u003e using worse methods. For all of the reasons that OP_RETURN was a good idea\n\u003e in the first place, it's a good idea to support it in PaymentRequests.\n\nAs I explained, none of those reasons apply to PaymentRequests.\n\n\u003e As for keyless - there's no way (that I know of) to construct a transaction\n\u003e with a zero value OP_RETURN in an environment without keys since the\n\u003e Payment Protocol is what defines the method for getting a transaction from\n\u003e a server to a wallet. You can make a custom transaction and execute it in\n\u003e the same application but without Payments there's no way to move\n\u003e transactions between two applications. You need to build the transaction\n\u003e where you execute it and thus need a key.\n\nI have no idea what you are trying to say here.\n\nLuke",
"sig": "cd557a0ed79409e6456aa4dbdd425ab1bece9b9b4887a4959f8454b637f187eb537a5478de367731ab6e6f1035b717c055bab8e4777cd74e622a30eac9d9a80d"
}