📅 Original date posted:2018-04-11
📝 Original message:Clarification on one part below:
On Wed, Apr 11, 2018 at 2:21 PM, Karl-Johan Alm
<karljohan-alm at garage.co.jp> wrote:
> On Wed, Apr 11, 2018 at 5:29 AM, Maksim Solovjov via bitcoin-dev
> <bitcoin-dev at lists.linuxfoundation.org> wrote:
>> 1. What does it mean for a transaction ( with 0 confirmations ) to be
>> trusted or not?
>
> It is trusted if (1) it is final (i.e. it can't be replaced), (2) it
> is not in a block that was reorged out (negative confirmation count),
> (3) the 'spend zero conf change' option is set, (4) it is in the
> mempool, and (5) all inputs are from us.
"can't be replaced" here means it cannot be replaced through
conventional means. It is always possible to replace a transaction
that has not yet been confirmed, e.g. by asking a miner to mine a
conflicting transaction directly.
Karl-Johan Alm [ARCHIVE] /
npub17c…qmtzy
2023-06-07 18:11:36
in reply to nevent1q…c73e
Author Public Key
npub17cwk7hm623dm5npjzu8cvv994h43k2keanegs8w78xyvlez8hqqsqqmtzyPublished at
2023-06-07 18:11:36Event JSON
{
"id": "52626c0a5555b44a746353a7edacbc4b47a7d1159f019bbb0f8b9ed690e455c8",
"pubkey": "f61d6f5f7a545bba4c32170f8630a5adeb1b2ad9ecf2881dde3988cfe447b801",
"created_at": 1686161496,
"kind": 1,
"tags": [
[
"e",
"982a0c82bfb8d6491e92dfa42dfd12e7a2df5bc1554108026ba2680500a8b0bc",
"",
"root"
],
[
"e",
"341d9959ee6d926f99bae15cd278aa3fec3af4956501b0794daecc7fe0ae6a71",
"",
"reply"
],
[
"p",
"f61d6f5f7a545bba4c32170f8630a5adeb1b2ad9ecf2881dde3988cfe447b801"
]
],
"content": "📅 Original date posted:2018-04-11\n📝 Original message:Clarification on one part below:\n\nOn Wed, Apr 11, 2018 at 2:21 PM, Karl-Johan Alm\n\u003ckarljohan-alm at garage.co.jp\u003e wrote:\n\u003e On Wed, Apr 11, 2018 at 5:29 AM, Maksim Solovjov via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e 1. What does it mean for a transaction ( with 0 confirmations ) to be\n\u003e\u003e trusted or not?\n\u003e\n\u003e It is trusted if (1) it is final (i.e. it can't be replaced), (2) it\n\u003e is not in a block that was reorged out (negative confirmation count),\n\u003e (3) the 'spend zero conf change' option is set, (4) it is in the\n\u003e mempool, and (5) all inputs are from us.\n\n\"can't be replaced\" here means it cannot be replaced through\nconventional means. It is always possible to replace a transaction\nthat has not yet been confirmed, e.g. by asking a miner to mine a\nconflicting transaction directly.",
"sig": "ba47d59f9c7d765947a8ec59c9c40cde25f40e97735095bfb73f197f85057490081c3fc7a252eceb5d73990ae96b782d8799a73b74fe14981670c15249ec4aa3"
}