From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 37283C000A for ; Sat, 27 Nov 2021 13:42:43 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 0D1B540352 for ; Sat, 27 Nov 2021 13:42:43 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: 0.601 X-Spam-Level: X-Spam-Status: No, score=0.601 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp4.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=tutanota.de Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FOnj1CB-nsxJ for ; Sat, 27 Nov 2021 13:42:42 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162]) by smtp4.osuosl.org (Postfix) with ESMTPS id DB70B40350 for ; Sat, 27 Nov 2021 13:42:41 +0000 (UTC) Received: from w3.tutanota.de (unknown [192.168.1.164]) by w1.tutanota.de (Postfix) with ESMTP id 8821CFBB3C2; Sat, 27 Nov 2021 13:42:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1638020558; s=s1; d=tutanota.de; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender; bh=xwwlGK3XgXF0aXApGkrn229BIfdou27Sg2xKkRMSOEQ=; b=SjrXBbYP+xjpqtZk1SSy1pa98yuOBEExEyWVqzLH8Xc3rTZsihnS3sfEM8gFIWPi 1v8e+1qJgeliGJkF6em3N8k+CrVUFayp+WOCjgCxQ+tbr8+YRNNKIZNFj3tuYmbsc2q Gr9YGk4rbbWbxpxil9TkBQva8yFuGDQObJfs4pSMGZF3qgH6dacmUv2tcsVGEnpzVlP 968/E/iciQ3tyao2q7lrFKCFBs2JLlkvU4gs3JKhGeIGdkoo+1VzWaHlXGq2yaUf3iz kGVg9ZNnYnprnadakuC2IG4+tWrWdkEj0eE0QMJ1t3y3T6skXW7oX15ruySJl1JmJmg nJy9eLid6A== Date: Sat, 27 Nov 2021 14:42:38 +0100 (CET) From: Prayank To: ali@notatether.com Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_92765_1100432481.1638020558538" X-Mailman-Approved-At: Sat, 27 Nov 2021 16:58:17 +0000 Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] Trying to patch Core ZMQ "rawtx" topic to only publish unconfirmed transactions: How? X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2021 13:42:43 -0000 ------=_Part_92765_1100432481.1638020558538 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi Ali, Not sure if this is exactly what you are looking for but maybe trying to solve this I might also learn few things: Save zmqpubsequence=tcp://127.0.0.1:28332 in bitcoin.conf Run bitcoind Run this python script: https://pastebin.com/raw/tNp2x5y3 You will see results like this: https://i.imgur.com/xKzFJbl.png https://i.imgur.com/gpsTTHZ.png A - Accepted, C- Connect (block) and R- Removal in the above screenshots If you are looking for unconfirmed transactions printed in sequence I think this should help. Since transactions can be printed twice (accept,remove) in this case as well, python script can be modified to manage this IMO. Other alternatives can be debug=mempool and reading debug.log for changes without polling. -- Prayank A3B1 E430 2298 178F ------=_Part_92765_1100432481.1638020558538 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Ali,

Not sur= e if this is exactly what you are looking for but maybe trying to solve thi= s I might also learn few things:

Save zmqpubsequence=3Dtcp://127.0.0.1:28332 in bitcoin.conf

Run bitcoind
=

Run this python script: https= ://pastebin.com/raw/tNp2x5y3

You will see results like this:
https= ://i.imgur.com/xKzFJbl.png
https://i.imgur.com/g= psTTHZ.png

A - Accep= ted, C- Connect (block) and R- Removal in the above screenshots

If you are looking for unconfir= med transactions printed in sequence I think this should help. Since transa= ctions can be printed twice (accept,remove) in this case as well, python sc= ript can be modified to manage this IMO.

Other alternatives can be debug=3Dmempool and reading = debug.log for changes without polling.

--
Prayank

A= 3B1 E430 2298 178F
------=_Part_92765_1100432481.1638020558538--