Skip to content

txs being requested when they are already in the blockchain #4797

@rebroad

Description

@rebroad

An example transaction is "6603c701696be7d3ca6b540816627b4e3358d17cb92cc54466da6afb87b9615a".

At 2014-08-30 17:04:46, it's accepted into my node's mempool:-
2014-08-30 17:04:46 AcceptToMemoryPool: peer=26 /Satoshi:0.8.6/ : accepted 6603c701696be7d3ca6b540816627b4e3358d17cb92cc54466da6afb87b9615a (poolsz 486)

At 2014-08-30 17:08:25, the block containing this tx is received:-
2014-08-30 17:08:25 UpdateTip: new best=000000000000000007c2b4a744a51454c7809cf695fc33b2ee7153ff1d15cd2a height=318283 log2_work=80.436706 tx=45651627 date=2014-08-30 17:08:08 progress=0.999999

At 2014-08-30 17:18:44, it's seen on the network again, and requested (dispite being in the blockchain), and identified as an orphan:-
2014-08-30 17:18:44 stored orphan tx 6603c701696be7d3ca6b540816627b4e3358d17cb92cc54466da6afb87b9615a (mapsz 1169)

At 2014-08-30 17:49:18, it's still being requested by other nodes, but "notfound", because it's presumeably fallen out of the orphan tx pool:-
2014-08-30 17:49:18 notfound tx 6603c701696be7d3ca6b540816627b4e3358d17cb92cc54466da6afb87b9615a to peer=176

Over an hour later, it's still being requested by up-to-date nodes:-
2014-08-30 18:16:56 notfound tx 6603c701696be7d3ca6b540816627b4e3358d17cb92cc54466da6afb87b9615a to peer=56 (/Satoshi:0.9.1/: version 70002)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions