📅 Original date posted:2016-03-03
📝 Original message:Hi
> My guess is the user was using a client that does not adjust TX fee, and
> needed to manually set it in order to get the TX in the block sooner,
> and meant 15 mBTC or something.
>
> I suggest that either :
>
> A) TX fee may not be larger than sum of outputs
> B) TX fee per byte may not be larger than 4X largest fee per byte in
> previous block
I don't think a such "feature" or lets say protection should be part of
the consensus layer.
Such checks should be done by the tx creation clients (wallets) – or –
nodes could have an option to not accept transaction with insane fees
into their mempool (policy).
</jonas>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160303/a0e73400/attachment-0001.sig>;
Jonas Schnelli [ARCHIVE] /
npub1nf…3dtxs
2023-06-07 17:49:40
in reply to nevent1q…r3dn
Author Public Key
npub1nfrrurat393mqymf3s26pujyn5vujlem3pzcukr5p9d4qpklngxq43dtxsPublished at
2023-06-07 17:49:40Event JSON
{
"id": "83dd3d53a7bc549f317c014a2ebf232c48a63f95fcc3b338db3ed43f6b6218d0",
"pubkey": "9a463e0fab8963b013698c15a0f2449d19c97f3b88458e5874095b5006df9a0c",
"created_at": 1686160180,
"kind": 1,
"tags": [
[
"e",
"a7cc26178fb7f18a507ac22e6b721acf88f6e1f9d32f90a76a43a728f3b1a249",
"",
"root"
],
[
"e",
"636cb8fd4cab64020f3040ac3723d6213b0adf2b6f3165d0681adb30057cbd93",
"",
"reply"
],
[
"p",
"a384795310cea1937dda4d01ee8f14ca734b9a7ab60c62114a5656706e15e47f"
]
],
"content": "📅 Original date posted:2016-03-03\n📝 Original message:Hi\n\n\u003e My guess is the user was using a client that does not adjust TX fee, and\n\u003e needed to manually set it in order to get the TX in the block sooner,\n\u003e and meant 15 mBTC or something.\n\u003e \n\u003e I suggest that either :\n\u003e \n\u003e A) TX fee may not be larger than sum of outputs\n\u003e B) TX fee per byte may not be larger than 4X largest fee per byte in\n\u003e previous block\n\nI don't think a such \"feature\" or lets say protection should be part of\nthe consensus layer.\n\nSuch checks should be done by the tx creation clients (wallets) – or –\nnodes could have an option to not accept transaction with insane fees\ninto their mempool (policy).\n\n\u003c/jonas\u003e\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 819 bytes\nDesc: OpenPGP digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160303/a0e73400/attachment-0001.sig\u003e",
"sig": "204707e207b7b2661e2077d8c71c519aa59c11615d302128b6d0cbe3159125082525b28e3d6043ca64ca2f6eca2c3be514764234e0606d5809d101d7f05cd54f"
}