You can create a bitcoin transaction, have it as a txhex, and see if it’s in any mempool via the p2p layer, so it’s the collective of all mempools I am referring to

Reply to this note

Please Login to reply.

Discussion

The idea of “the collective of all mempools” is not a defined entity and can't be queried or observed in its entirety.

There is no way to know whether a transaction is in any mempool, because you can’t reach or query every node in practice or in principle.

You can walk the network graph and talk to any node in the p2p network graph with ports open and check to see if they have a tx in their mempool.

Something is telling me you’re playing pedantic word games to avoid the point, which is it’s absolutely possible to show someone a tx which has been filtered, because it would be a transaction not in any block, nor none of the reachable networks mempool.

Here - let me even help you out - you can create a 0 fee tx, and that would be a “filtered” transaction. It takes a few minutes to do it on a core node in the console.

I mean; I did say call me crazy from the start and I’m not ignoring the point: the point still stands.

Miners would not include a 0 fee transaction unless there are other incentives. Just like some nodes would opt not to relay a transaction with arbitrary data less there is policy alignment.

Therefore I cannot “link” a transaction that has been filtered because it cannot be verified on chain (which would disprove its filtered nature) and I cannot “link” a transaction that has been opted not to be relayed around the network because it would be unable to query it.

A filtered or non-relayed transaction cannot be linked, verified, or queried because it exists outside the bounds of both blockchain inclusion and mempool propagation.

But maybe I’m just crazy. I’m still learning.

The linking of a TX is a TX Hex, you can load it into your node, sparrow wallet, and other bitcoin software.

Correct miners would not include a 0 fee TX short of exogenous incentives. Your opinion on how the network topology works for nodes is a non sequitor.

Here, this is a txhex I just spun up on my node:

0200000001e58689052bfbff3af1cd60c65d82e0d17b0a60c235817ba50e1a71b4111940410300000000fdffffff010000000000000000c06a4cbd4865726520697320616e206578616d706c6520666f7220612066696c7465726564207472616e73616374696f6e20666f72204c6f67656e206f6e204e6f7374722e20596f752063616e206c6f6164207468697320696e20796f7572206e6f6465207573696e6720746865206465636f64657261777461726e73616374696f6e20636f6d6d616e6420696e2074686520426974636f696e204e6f6465205250432c206f72206c6f6164696e6720696e2073706172726f772077616c6c657400000000

TXID: d3002dbfb6317ebc98107a305e3855969c8049da2384e3e4d8b9d3bb8c7ba9be

Use either sparrow wallet to load it yourself, OR your own bitcoin node using decoderawtransaction.

Whoops, forgot to sign it. Here is the full txhex, also used the wrong vout for the utxo:

TXID: eaece0c1768247d3b8718ed0cab59752d149884d859aef9998d5bbf7648258b2

02000000000101e58689052bfbff3af1cd60c65d82e0d17b0a60c235817ba50e1a71b4111940410400000000fdffffff010000000000000000c06a4cbd4865726520697320616e206578616d706c6520666f7220612066696c7465726564207472616e73616374696f6e20666f72204c6f67656e206f6e204e6f7374722e20596f752063616e206c6f6164207468697320696e20796f7572206e6f6465207573696e6720746865206465636f64657261777461726e73616374696f6e20636f6d6d616e6420696e2074686520426974636f696e204e6f6465205250432c206f72206c6f6164696e6720696e2073706172726f772077616c6c6574014017702a23c38ecba6b854e00f34ad9c717b49fac9bbdf8f9eb3c7246258b03faeb2f2f90d3668204042ecbf8b32ebdd09de22e0b3e0fa4fe5f9580c6ecb9ac2c900000000

Here is another one (can't spend with both, it'd be a double spend):

TXID: 78996a0c15aa1b01574b99b0899829211d4ea3fad7c29cac0572eef7f1a6018d

02000000000101e58689052bfbff3af1cd60c65d82e0d17b0a60c235817ba50e1a71b4111940410400000000fdffffff0100170000000000002251208f200657b2853dfc759fb2aab5d6cda2e0227ce83041aa37d36b3345ace800ca0140fecfa6b2fb5d91c99d52cc122655bd0cdbc4426bf772098a12a7babbbb6691307cb7ab686fa0c999911ba53f629abd36db0770c80ebae5c7e2a58668544de2e900000000

Transaction, linked: