📅 Original date posted:2012-04-12
📝 Original message:On Thu, Apr 12, 2012 at 3:19 PM, Alan Reiner <etotheipi at gmail.com> wrote:
> My one big concern about this that users find a way to exploit this behavior
> for themselves. If it's too easy for users to create tx they know will get
> stuck and expire, it's no different than letting them cancel their zero-conf
> transactions. i.e. I pay 0.5 BTC in a store for a candy bar, so I send it
> using a combination of inputs and fees that I know will lead to it being
> stuck and expire.
>
> On the other hand, if such conditions are deterministic enough, it could be
> detected by the recipient and flagged.
>
> It's not a huge deal, but it's something to consider.
Do you have a -specific- concern that you feel may be exploited?
Expiration already occurs at random, as nodes shut down and restart,
log on and log off the network.
--
Jeff Garzik
exMULTI, Inc.
jgarzik at exmulti.com
Jeff Garzik [ARCHIVE] /
npub1kf…f3f58
2023-06-07 10:04:03
in reply to nevent1q…6nvy
Author Public Key
npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58Published at
2023-06-07 10:04:03Event JSON
{
"id": "f6d4d0a4fcb61cb037dfacea90cc95eb8189fca113886f338c1e90fecfab949e",
"pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11",
"created_at": 1686132243,
"kind": 1,
"tags": [
[
"e",
"5f0cc6578a9ca4b7b0857c070ede1826db3227f161e70524c04566da5c5a56a8",
"",
"root"
],
[
"e",
"45b46176888b4578195fac33f72f7af44bfc550e7394a28b4af0f2588f128b08",
"",
"reply"
],
[
"p",
"86f42bcb76a431c128b596c36714ae73a42cae48706a9e5513d716043447f5ec"
]
],
"content": "📅 Original date posted:2012-04-12\n📝 Original message:On Thu, Apr 12, 2012 at 3:19 PM, Alan Reiner \u003cetotheipi at gmail.com\u003e wrote:\n\u003e My one big concern about this that users find a way to exploit this behavior\n\u003e for themselves. If it's too easy for users to create tx they know will get\n\u003e stuck and expire, it's no different than letting them cancel their zero-conf\n\u003e transactions. i.e. I pay 0.5 BTC in a store for a candy bar, so I send it\n\u003e using a combination of inputs and fees that I know will lead to it being\n\u003e stuck and expire.\n\u003e\n\u003e On the other hand, if such conditions are deterministic enough, it could be\n\u003e detected by the recipient and flagged.\n\u003e\n\u003e It's not a huge deal, but it's something to consider.\n\nDo you have a -specific- concern that you feel may be exploited?\n\nExpiration already occurs at random, as nodes shut down and restart,\nlog on and log off the network.\n\n-- \nJeff Garzik\nexMULTI, Inc.\njgarzik at exmulti.com",
"sig": "2b1f837cbedc670ef97cdf381b5b507ccbfe9f49cbb5316eb420597aa9cacff53452c97cc08af830b5d95a36bad0ab08d7342971e0278fa227098a79b0e7330d"
}