đź“… Original date posted:2019-03-06
đź“ť Original message:The reject message is helpful for figuring out why a tx was rejected.
It’s not useful for determining success, yes. Particularly when doing
segwit / newer types of tx’s as there’s always one or more pesky nodes who
still don’t support it and send a reject message for perfectly good tx’s.
But after a delay where you haven’t seen your tx propagated on the network,
it’s useful to know *why* it failed.
What would be nice is actually expanding this error message. Currently with
RBF tx’s “fee too small” is sent for both original transactions as well as
replacement transactions. So a bug accidentally sending spent txos
(currently in mempool) says “fee too small” instead of something more
appropriate like “fee too small to supersede existing unconfirmed
transaction.”
On Tue, Mar 5, 2019 at 7:26 PM Marco Falke via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> Bitcoin Core may send "reject" messages as response to "tx", "block" or
> "version" messages from a network peer when the message could not be
> accepted.
>
> This feature is toggled by the `-enablebip61` command line option and has
> been
> disabled by default since Bitcoin Core version 0.18.0 (not yet released as
> of
> time of writing). Nodes on the network can not generally be trusted to send
> valid ("reject") messages, so this should only ever be used when connected
> to a
> trusted node. At this time, I am not aware of any software that requires
> this
> feature, and I would like to remove if from Bitcoin Core to make the
> codebase
> slimmer, easier to understand and maintain. Let us know if your application
> relies on this feature and you can not use any of the recommended
> alternatives:
>
> * Testing or debugging of implementations of the Bitcoin P2P network
> protocol
> should be done by inspecting the log messages that are produced by a
> recent
> version of Bitcoin Core. Bitcoin Core logs debug messages
> (`-debug=<category>`) to a stream (`-printtoconsole`) or to a file
> (`-debuglogfile=<debug.log>`).
>
> * Testing the validity of a block can be achieved by specific RPCs:
> - `submitblock`
> - `getblocktemplate` with `'mode'` set to `'proposal'` for blocks with
> potentially invalid POW
>
> * Testing the validity of a transaction can be achieved by specific RPCs:
> - `sendrawtransaction`
> - `testmempoolaccept`
>
> * Wallets should not use the absence of "reject" messages to indicate a
> transaction has propagated the network, nor should wallets use "reject"
> messages to set transaction fees. Wallets should rather use fee
> estimation
> to determine transaction fees and set replace-by-fee if desired. Thus,
> they
> could wait until the transaction has confirmed (taking into account the
> fee
> target they set (compare the RPC `estimatesmartfee`)) or listen for the
> transaction announcement by other network peers to check for propagation.
>
> I propose to remove "reject" messages from Bitcoin Core 0.19.0 unless
> there are
> valid concerns about its removal.
>
> Marco
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20190305/bf105368/attachment.html>;
Dustin Dettmer [ARCHIVE] /
npub1x5…kqsqu
2023-06-07 18:16:35
in reply to nevent1q…vjex
Author Public Key
npub1x54n25utwk7dzwzvk2v0aknptez5gxdwcyrxx2wgc0lnhgvwu72qmkqsquPublished at
2023-06-07 18:16:35Event JSON
{
"id": "63e3ae9fb6515463ee1b3c2ad381af9547ec8d8d66e65a6b5cfd27bc87395698",
"pubkey": "352b35538b75bcd1384cb298feda615e454419aec1066329c8c3ff3ba18ee794",
"created_at": 1686161795,
"kind": 1,
"tags": [
[
"e",
"d23d84909ded4e86934b4199a32650fb490f51617593613544f6edda083d91e3",
"",
"root"
],
[
"e",
"9e7d5b971c93a5f11c9f7ccdcc71a6054811f82b9bbc3c746ce148f1b25c96fa",
"",
"reply"
],
[
"p",
"04038841fa1dffefb87710e6ca5bcef647155d764360a6d1e77ab28e7646a869"
]
],
"content": "📅 Original date posted:2019-03-06\n📝 Original message:The reject message is helpful for figuring out why a tx was rejected.\n\nIt’s not useful for determining success, yes. Particularly when doing\nsegwit / newer types of tx’s as there’s always one or more pesky nodes who\nstill don’t support it and send a reject message for perfectly good tx’s.\n\nBut after a delay where you haven’t seen your tx propagated on the network,\nit’s useful to know *why* it failed.\n\nWhat would be nice is actually expanding this error message. Currently with\nRBF tx’s “fee too small” is sent for both original transactions as well as\nreplacement transactions. So a bug accidentally sending spent txos\n(currently in mempool) says “fee too small” instead of something more\nappropriate like “fee too small to supersede existing unconfirmed\ntransaction.”\n\nOn Tue, Mar 5, 2019 at 7:26 PM Marco Falke via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Bitcoin Core may send \"reject\" messages as response to \"tx\", \"block\" or\n\u003e \"version\" messages from a network peer when the message could not be\n\u003e accepted.\n\u003e\n\u003e This feature is toggled by the `-enablebip61` command line option and has\n\u003e been\n\u003e disabled by default since Bitcoin Core version 0.18.0 (not yet released as\n\u003e of\n\u003e time of writing). Nodes on the network can not generally be trusted to send\n\u003e valid (\"reject\") messages, so this should only ever be used when connected\n\u003e to a\n\u003e trusted node. At this time, I am not aware of any software that requires\n\u003e this\n\u003e feature, and I would like to remove if from Bitcoin Core to make the\n\u003e codebase\n\u003e slimmer, easier to understand and maintain. Let us know if your application\n\u003e relies on this feature and you can not use any of the recommended\n\u003e alternatives:\n\u003e\n\u003e * Testing or debugging of implementations of the Bitcoin P2P network\n\u003e protocol\n\u003e should be done by inspecting the log messages that are produced by a\n\u003e recent\n\u003e version of Bitcoin Core. Bitcoin Core logs debug messages\n\u003e (`-debug=\u003ccategory\u003e`) to a stream (`-printtoconsole`) or to a file\n\u003e (`-debuglogfile=\u003cdebug.log\u003e`).\n\u003e\n\u003e * Testing the validity of a block can be achieved by specific RPCs:\n\u003e - `submitblock`\n\u003e - `getblocktemplate` with `'mode'` set to `'proposal'` for blocks with\n\u003e potentially invalid POW\n\u003e\n\u003e * Testing the validity of a transaction can be achieved by specific RPCs:\n\u003e - `sendrawtransaction`\n\u003e - `testmempoolaccept`\n\u003e\n\u003e * Wallets should not use the absence of \"reject\" messages to indicate a\n\u003e transaction has propagated the network, nor should wallets use \"reject\"\n\u003e messages to set transaction fees. Wallets should rather use fee\n\u003e estimation\n\u003e to determine transaction fees and set replace-by-fee if desired. Thus,\n\u003e they\n\u003e could wait until the transaction has confirmed (taking into account the\n\u003e fee\n\u003e target they set (compare the RPC `estimatesmartfee`)) or listen for the\n\u003e transaction announcement by other network peers to check for propagation.\n\u003e\n\u003e I propose to remove \"reject\" messages from Bitcoin Core 0.19.0 unless\n\u003e there are\n\u003e valid concerns about its removal.\n\u003e\n\u003e Marco\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20190305/bf105368/attachment.html\u003e",
"sig": "a529fb82825f929f04c5c110c361434e9dd60c640912e74f94df4b496d1509e9ef22370febf3ae1f9e9645a3c54cad5bf1fa6c4060b13514704e668cd78ae695"
}