📅 Original date posted:2014-02-12
📝 Original message:Sending this again and truncating since apparently the message body was too
long.
Thanks for humoring my questions!
>I think reporting such errors to the wallet would make complete sense.
However i am not clear why we would a separate url for that?
Hmm, thinking about this more, adding a simple status_code in
PaymentRequest would be a much easier way to achieve this. However,
continuing to think about this even more, maybe the simple memo field along
with an empty set of outputs is enough already.
In bitcoinj, right now the code will throw a
PaymentRequestException.InvalidOutputs exception if the set of outputs is
empty with a message of "No Outputs". Because of that, there isn't a good
way to tell the difference between a payment request that had no outputs
and a payment request that had some invalid output(s).
*Question to everyone:*
How does bitcoin-qt handle a PaymentRequest with no outputs?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140211/e0972311/attachment.html>;
Kevin Greene [ARCHIVE] /
npub1l3…hwq5p
2023-06-07 15:13:08
in reply to nevent1q…8a8l
Author Public Key
npub1l3sj8amnurgf3cu3p2hhcaham90khafc4vgsmymqdnn0k3kanulsghwq5pPublished at
2023-06-07 15:13:08Event JSON
{
"id": "aea2aabf8b96721cfbbce8fff2aed4761ee7cbd885c234616cc17bd884a10f72",
"pubkey": "fc6123f773e0d098e3910aaf7c76fdd95f6bf538ab110d93606ce6fb46dd9f3f",
"created_at": 1686150788,
"kind": 1,
"tags": [
[
"e",
"8d7858f1d9ce21a632344a1294f3710b1744f78d70beac66f50b5fdde038ce90",
"",
"root"
],
[
"e",
"cb2629cad0934e8d1ba874ff163d4b1af0b32b113bc372fc000fa108776b3f0b",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2014-02-12\n📝 Original message:Sending this again and truncating since apparently the message body was too\nlong.\n\nThanks for humoring my questions!\n\n\u003eI think reporting such errors to the wallet would make complete sense.\nHowever i am not clear why we would a separate url for that?\n\nHmm, thinking about this more, adding a simple status_code in\nPaymentRequest would be a much easier way to achieve this. However,\ncontinuing to think about this even more, maybe the simple memo field along\nwith an empty set of outputs is enough already.\n\nIn bitcoinj, right now the code will throw a\nPaymentRequestException.InvalidOutputs exception if the set of outputs is\nempty with a message of \"No Outputs\". Because of that, there isn't a good\nway to tell the difference between a payment request that had no outputs\nand a payment request that had some invalid output(s).\n\n*Question to everyone:*\nHow does bitcoin-qt handle a PaymentRequest with no outputs?\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140211/e0972311/attachment.html\u003e",
"sig": "02b75e52bf365d95e0b04e853af8f2fe1babc024f128bb7e7f4042d800aed3bd16a7f414f4d574071f6442378567e6885de9d0c74300f12204a18b2f6edca145"
}